Hi Peter and Jens

I've checked the byte order using Chads Trabant msview routine and:
1. msd files from GeoDas are big endian
2. msd file from newest version of SEISEI, resulting of merging GeoDAS msd files are little endian i.e. SEISEI change byte order 3. msd files from new version of WAVETOOL are little endian, WAVETOOL change byte order too

GeoDAS software cannot read little endian files making error i.e. GeoDAS have an endian problem. Seisan mulplt have no endian problem i.e. display both big and little endian.

I've used msrepack to change byte order from little to big endian, how Peter has suggested, and the files are read correctly by GeoDAS. This solves my problem.
I only ask why SEISEI and WAVETOOL change byte order?

Thank you very much for your suggestions, discussion and help.

Grazyna




----- Original Message ----- From: "Voss, Peter" <[email protected]>
To: "'Jens Havskov'" <[email protected]>
Cc: <[email protected]>
Sent: Sunday, October 13, 2013 9:27 PM
Subject: SV: [seisan] SEISEI from Seisan V.10


Hi Jens and Grazyna,
Yes, Chads routines have no endian problem (and I did a lot of testing).
I suggest that Grazyna use msrepack to check if it is the GeoDAS software that has a endian problem.
iSalud!
Peter

-----Oprindelig meddelelse-----
Fra: Jens Havskov [mailto:[email protected]] På vegne af Jens Havskov
Sendt: 13. oktober 2013 18:57
Til: Voss, Peter
Cc: [email protected]
Emne: Re: [seisan] SEISEI from Seisan V.10

peter

we are using chads routines to read mseed, i suppose that he takes care of the endian problem ? in any case if thsi is the problem we should contact chad and find out.

jens

On Thu, 10 Oct 2013, Voss, Peter wrote:

Hi Grazyna,
The msi program will tell you if your mseed files are little/big endian. See example below.

Download msi here: https://seiscode.iris.washington.edu/projects/msi

To change byte order of a mseed file use the msrepack:
msrepack -b 1 -o data.out data.in

to get msrepack download msmod here:
https://seiscode.iris.washington.edu/projects/msmod
and look under msmod/libmseed/example/

Good luck
Peter

EXAMPLE:
msi -p /seedlink/archive/2013/DK/9593/HHZ.D/DK.9593..HHZ.D.2013.280 |
more DK_9593__HHZ, 000025, D
            start time: 2013,280,00:00:00.370000
     number of samples: 3063
    sample rate factor: 100  (100 samples per second) sample rate
multiplier: 1
  number of blockettes: 2
       time correction: 0
           data offset: 64
first blockette offset: 48
        BLOCKETTE 1000: (Data Only SEED)
             next blockette: 56
                   encoding: STEIM 2 Compression (val:11)
                 byte order: Big endian (val:1)
              record length: 4096 (val:12)
        BLOCKETTE 1001: (Data Extension)
             next blockette: 0
             timing quality: 0%
               micro second: 0
                frame count: 63


-----Oprindelig meddelelse-----
Fra: [email protected] [mailto:[email protected]] På
vegne af [email protected]
Sendt: 10. oktober 2013 11:13
Til: [email protected]; [email protected]
Emne: Re: [seisan] SEISEI from Seisan V.10

Hello again,

Done a lot of testing and I'm pretty sure the mseed files (output from SEISEI or WAVETOOL) will not open because of the little endian byte order.
Is it possible to change byte order to big endian?

Thank you in advance
Grazyna Holeczek



Od: [email protected]
Do: [email protected];
Wys?ane: 13:09 Poniedzia?ek 2013-10-07
Temat: [seisan] SEISEI from Seisan V.10

Dear Seisan Experts

GeoDAS cannot open files created with the new version of SEISEI, option merge, output format mseed. A comment appear, for example "last sample of the frame is -2187 instead of -1588 expected". There was no ploblem with the files created with the older version of SEISEI.
The only difference i have noticed is byte order: the new files are
little endian, the old was big endian (the input files for the SEISEI
commad are big endian)

Is byte order a reason?
Is there any reason the new version of SEISEI create little endian?

Regards
Grazyna Holeczek

_______________________________________________
seisan mailing list
[email protected]
http://mailman.uib.no/listinfo/seisan





_______________________________________________
seisan mailing list
[email protected]
http://mailman.uib.no/listinfo/seisan
_______________________________________________
seisan mailing list
[email protected]
http://mailman.uib.no/listinfo/seisan



_______________________________________________
seisan mailing list
[email protected]
http://mailman.uib.no/listinfo/seisan

Reply via email to