geopsy.org

Hi Marc,
I found that Geopsy v. 3.3.0. and later releases do not read log files created with previous releases (H/V tool) and give error messages like this
Loading C: /Lavori/2020/Cortina_RioGatto/N_2864.saf ...
Unrecognized component name for SAF format: "v"
Unrecognized component name for SAF format: "ew"
*********** File N_2864.saf ***********
Add signal id 1 to component Vertical of station RioGatto_2864 at 0.00 0.00 0.00
Add signal id 2 to component North of station RioGatto_2864 at 0.00 0.00 0.00
Add signal id 3 to component East of station RioGatto_2864 at 0.00 0.00 0.00
expected a number between 0000 and 9999: 'SIGN'
error parsing time 'CyyyyMMddhhmmssz'
^
expected a number between 0000 and 9999: 'FILE'
error parsing time 'CyyyyMMddhhmmssz'
^
Adding windows: error reading line 'SIGNAL FILE NAME = ### temporary signal ###'
------------------------------------------------------------------------------------

The log file is the following (I can't attach it):

### Parameters ###
SIGNAL FILE NAME=### temporary signal ###
FROM TIME TYPE=Signal
TO TIME TYPE=Signal
USE FIRST PICK ONLY=n
WINDOW LENGTH TYPE=Exactly
WINDOW MIN LENGTH=40
WINDOW MAX LENGTH=40
BAD SAMPLE TOLERANCE=0
BAD SAMPLE GAP=0
WINDOW OVERLAP=5
BAD SAMPLE THRESHOLD TYPE=NoSampleThreshold
BAD SAMPLE THRESHOLD=100
ANTI-TRIGGERING ON RAW SIGNAL (y/n)=y
USED RAW COMPONENTS=y, y, y
RAW STA (s)=1
RAW LTA (s)=30
RAW MIN SLTA=0.2
RAW MAX SLTA=2.5
ANTI-TRIGGERING ON FILTERED SIGNAL (y/n)=n
SMOOTHING TYPE=KonnoOmachi
SMOOTHING CONSTANT=40
WINDOW TYPE=Tuckey
WINDOW REVERSED=n
WINDOW ALPHA=0.1
MINIMUM=0.5
MAXIMUM=20
SAMPLES NUMBER=100
SAMPLING TYPE=Log
DO HIGH PASS=false
HIGH PASS FREQUENCY=0
HORIZONTAL COMPONENTS=Squared
HORIZONTAL AZIMUTH=0
### End Parameters ###
### Windowing Log ###
Automatic windowing
Adding window from 134.832 to 174.832 s.
Adding window from 204.864 to 244.864 s.
Adding window from 421.68 to 461.68 s.
Adding window from 615.184 to 655.184 s.
Adding window from 699.44 to 739.44 s.
Adding window from 737.456 to 777.456 s.
Adding window from 807.392 to 847.392 s.
Adding window from 944.432 to 984.432 s.
Adding window from 1002.29 to 1042.29 s.
Adding window from 1040.3 to 1080.3 s.
Adding window from 1493.5 to 1533.5 s.
Adding window from 1555.31 to 1595.31 s.
Adding window from 1683.57 to 1723.57 s.
Adding window from 3386.35 to 3426.35 s.
Removing window from 204.864 to 244.864 s.
Removing window from 807.392 to 847.392 s.
### End Windowing Log ###
### Time Windows ###
# Number= 12
# Start time End Time Window length
134.832 174.832 40
421.68 461.68 40
615.184 655.184 40
699.44 739.44 40
737.456 777.456 40
944.432 984.432 40
1002.29 1042.29 40
1040.3 1080.3 40
1493.5 1533.5 40
1555.31 1595.31 40
1683.57 1723.57 40
3386.35 3426.35 40
### End Time Windows ###

Thanks

Luigi

Hi Luigi,

Thanks for your report.
There is no simple way to work around this issue right now because the time was saved relative to the beginning of the signal and it is now an absolute time with format "yyyyMMddhhmmssz". I will add some code that offers some compatibility. I don't think that it will be in the next release (3.3.3) because it requires too many modifications. It will be for 3.4.0 to be released later. But it will be available sooner if you are running Linux as preview through the git repository.

I also note that some keywords for naming components are not recognized when reading SAF format. Is that correct that components are not properly set in geopsy while reading this file?

Best regards,

Marc

Thanks Marc.

I realized, after writing the post, that strangely not even the releases of Geopsy, used to save the HV files (snapshot and 2.9.0), could correctly read the previously created log file due to an incorrect reading of the saf file time. This problem can be solved by inserting in the table the duration of the recording instead of the End Time.
Using the realease 3.3.2. with saf file geopsy does not read the start time (###), but the final one does. Once I managed, I don't know how, to save an HV with this release and when I opened the log file, the start and end time columns both reported absolute times.
As for the components, Geopsy reads 1vertical, 2North, 3 East correctly.

Finally, I would like to point out that in releases after 2.9.0. rotate spectrum does not work (the program crashes).

Best Regards

Luigi

Hi Luigi,

I'm about to produce 3.3.3 that fixes, among other points, reading of log files.
I've just checked an old SAF file (from 2002!) and I can read it correctly. Can you send me an example of SAF file with an invalid starting time in Geopsy?

Best regards,

Marc

Hi Marc,
I have been using the same header since 2005, extracted from your own .saf file. So I'm sending you one this year. Together with the .log file of the H / V tool obtained with the release snapshot 0.0.0 (considering that 3.3.2 does not save the H / V result). If I try to upload this file with 3.3.2 I have a negative answer, in the sense that the release does not recognize the log file.
It seems to me that the real problem is this which, sometimes I have also encountered with older releases (2.9.0.)

Best regards
Luigi

Hi Luigi,

Next release 3.3.3 can read your SAF file without error.
The log file is properly read by 3.4.0-preview (only through git) both for restoring time windows and parameter values. This fix was not possible in 3.3.3.

Best regards,

Marc