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

Reply via email to