Thread: sac header enumerated values

Started: 2010-09-28 23:27:59
Last activity: 2010-09-29 00:57:03
Topics: SAC Help
Philip Crotwell
2010-09-28 23:27:59
Hi

I have a java based seismic file reading package called seisFile that
handles SAC files amongst others
(http://www.seis.sc.edu/seisFile.html).

As part of that I have all the "enumerated header field values" as
constants (ie static final fields). At the time I created this, they
were all unique. I was looking at the sac docs today and noticed that
there have been new values added (51-86). I was going to add them, but
they are no longer unique. For example there are 2 IO "enumerated
headers", 11 and 82.

Is there a reason that these names were not kept unique?

http://www.iris.edu/software/sac/manual/file_format.html

thanks
Philip

  • Chad Trabant
    2010-09-28 20:46:11

    Hi Philip,

    I suspect there is a documentation error, maybe just the transcription to the HTML page. The values on that page don't quite match the enumerated values in the SacHeader.h that ships with 101.4 source code, the deviation starts . The defined value for 82 is "INU" (Nuclear cavity collapse), there is another IO-like value for "IO_" at number 84, there is also an "IOOTHER" at 44, at least that one matches the header. Somewhere around number 60 they deviate, looks like IPDEQ (59) and IPDEW (60) were included at some point in one list and not the other.

    Chad


    On Sep 28, 2010, at 1:27 PM, Philip Crotwell wrote:

    Hi

    I have a java based seismic file reading package called seisFile that
    handles SAC files amongst others
    (http://www.seis.sc.edu/seisFile.html).

    As part of that I have all the "enumerated header field values" as
    constants (ie static final fields). At the time I created this, they
    were all unique. I was looking at the sac docs today and noticed that
    there have been new values added (51-86). I was going to add them, but
    they are no longer unique. For example there are 2 IO "enumerated
    headers", 11 and 82.

    Is there a reason that these names were not kept unique?

    http://www.iris.edu/software/sac/manual/file_format.html

    thanks
    Philip
    _______________________________________________
    sac-help mailing list
    sac-help<at>iris.washington.edu
    http://www.iris.washington.edu/mailman/listinfo/sac-help



    • Philip Crotwell
      2010-09-29 00:57:03
      OK, so I will assume utils/sac.h from the 101.4 tarball should be
      considered definitive?

      I have to say "IO_" is a pretty dumb name for a constant, but I am
      going to make a real effort to use
      IODOR = 97 /* Odors */
      as soon as I get a chance!
      :)

      Philip


      On Tue, Sep 28, 2010 at 4:46 PM, Chad Trabant <chad<at>iris.washington.edu> wrote:

      Hi Philip,

      I suspect there is a documentation error, maybe just the transcription to the HTML page.  The values on that page don't quite match the enumerated values in the SacHeader.h that ships with 101.4 source code, the deviation starts .  The defined value for 82 is "INU" (Nuclear cavity collapse), there is another IO-like value for "IO_" at number 84, there is also an "IOOTHER" at 44, at least that one matches the header.  Somewhere around number 60 they deviate, looks like IPDEQ (59) and IPDEW (60) were included at some point in one list and not the other.

      Chad


      On Sep 28, 2010, at 1:27 PM, Philip Crotwell wrote:

      Hi

      I have a java based seismic file reading package called seisFile that
      handles SAC files amongst others
      (http://www.seis.sc.edu/seisFile.html).

      As part of that I have all the "enumerated header field values" as
      constants (ie static final fields). At the time I created this, they
      were all unique. I was looking at the sac docs today and noticed that
      there have been new values added (51-86). I was going to add them, but
      they are no longer unique. For example there are 2 IO "enumerated
      headers", 11 and 82.

      Is there a reason that these names were not kept unique?

      http://www.iris.edu/software/sac/manual/file_format.html

      thanks
      Philip
      _______________________________________________
      sac-help mailing list
      sac-help<at>iris.washington.edu
      http://www.iris.washington.edu/mailman/listinfo/sac-help




22:04:37 v.01697673