In "Preferences" set file format to "Sac Little Endian" , importing little endian sac file will report error message and vice versa . So there must be a little bug in UI. Of course, "Automatic recognition" works.
Setting "Time reference" to "No common time reference(leave T0 as is)" never produce correct time reference where the hour:minute:second is correct, but not for moth/day/year.
Sac import bugs
1) What is the error message displayed when you load SAC files?
When trying to load a big endian SAC file with little endian forced, you can get this message in the log window:
Loading SAC : Geopsy can only open SAC files with version 6
Actual version is 100663296. It may lead to instabilities.
Loading SAC : This SAC file does not contains time series evenly spaced
### Error while loading file /home/mwathele/M2/signals/ABC/SIGNALS/001A_01988_02002.3.sac
2) The error for the date might comes from the way dates are written in Europe (day/month/year) and US (month/day/year). Do you get the correct T0 and Time Reference when loading through automatic recognition and any other option for time reference in preferences?
It may help me if you can send me a sample file either to my email address or to ftp://ftp.geopsy.org (if file is too large).
When trying to load a big endian SAC file with little endian forced, you can get this message in the log window:
Loading SAC : Geopsy can only open SAC files with version 6
Actual version is 100663296. It may lead to instabilities.
Loading SAC : This SAC file does not contains time series evenly spaced
### Error while loading file /home/mwathele/M2/signals/ABC/SIGNALS/001A_01988_02002.3.sac
2) The error for the date might comes from the way dates are written in Europe (day/month/year) and US (month/day/year). Do you get the correct T0 and Time Reference when loading through automatic recognition and any other option for time reference in preferences?
It may help me if you can send me a sample file either to my email address or to ftp://ftp.geopsy.org (if file is too large).
Mixing up between Little and Big endian for SAC files is now fixed (for next release). In fact, it was linked to the Preference and Load format dialog boxes and other file format may be affected (SEGY,...). Because "Automatic recognition" does a good job in general, I never test these two other ways for specifying file format. Thanks for your report.
Thanks again for your report for the date problem with SAC. The Julian days read from the file header were never included in the reference date.
These two bugs will be included in next release.
Thanks again for your report for the date problem with SAC. The Julian days read from the file header were never included in the reference date.
These two bugs will be included in next release.