[SAC-HELP] Error messages from getfhv etc

[Brian Savage]

Neil,

I agree with you, but accessing an undefined header value is (and has been) defined as an error (warning more recently).

There is a function call to turn off all errors (or warnings), but it will also disable any errors that you may want to see.
- sac_warning_off()
- sac_warning_stdout()
- sac_warning_stderr()
- sac_error_off()
- sac_error_stdout()
- sac_error_stderr()

Do you see another way to avoid these pesky error messages ? 
Should we defining these as "Warnings" ? or
Turn off the messaging completely for undefined values in the get* functions ? 
I am asking because I am curious how the community would like to see this handled, as I have been asked this before.

I think a recent version (circa 2011) has undefined values throws Warnings, not errors.

Brian Savage
savage at uri.edu

On Feb 25, 2014, at 11:21 AM, Neil Selby wrote:

> The sac_i/o functions getfhv, getihv etc print error messages to standard output if the related header variable is not defined, e.g.:
> 
> ERROR 1336: Undefined header field value. DEPMIN
> 
> this seems an undesirable behaviour to me, since the functions already return an error value that the programmer can handle in their own way.
> 
> Is this the designed behaviour or is it something peculiar about my set-up that can be changed?
> 
> 
> many thanks,
> 
> Neil
> _______________________________________________
> sac-help mailing list
> sac-help at iris.washington.edu
> http://www.iris.washington.edu/mailman/listinfo/sac-help