Grazyna
In the last couple of version of seisan we have used the offical chad
trabat routines to read and write mseed so it is not impossible that byte
order has changed. seisan has always been checking the byte order before
reading files so it should not be a probelm in seisan and i assume chads
routiens do the same. so it seems that the problem is that geisig does not
check byte order.
jens
On Mon, 7 Oct 2013, [email protected] wrote:
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