[scautoloc] playback of historic data

[cweidle]

EDIT:
originally I thought the issue might be related to numeric characters in the network code, but it turned out to be a duplicate of #104 (see comment below).
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::

When running scautoloc with picks from stations with network code 5H I run into:
17:26:59 [error] Autoloc3: MISSING STATION 5H.COO05
In an scxmldump -fI, the stations of this network are contained, thus I assume that the inventory is fine.

I have a playback setup where I write picks to xml files and then call scautoloc
seiscomp exec scautoloc --ep pick.xml -d $host --station-config mystation.conf --debug > origins.xml

mystation.conf is

* * 0 60
5H * 1 60
II * 1 180

From the debug output I get the feeling that only stations with [A-Z] network codes are read.

17:26:58 [debug] Reading station locations from DB
17:26:58 [debug] Initialized station II.RAYN
17:26:58 [debug] Initialized station II.UOSS

the same when reading mystation.conf

17:26:58 [debug] Reading station configs from file 'mystation.conf'
17:26:58 [debug] Station II RAYN pattern II * config: usage=1 maxnucdist=180
17:26:58 [debug] Station II UOSS pattern II * config: usage=1 maxnucdist=180

in both cases, stations from network 5H are missing.

Also, when I run scolv, the stations from network II are shown on the map, but network 5H is missing.
Since this is an official network code from FDSN I would like to avoid renaming it.

[cweidle]

Just see that this might be the same as #104 as the stations are offline and have an END in the inventory. Is there a suggested way to fix this?

EDIT:
if you don't mind messing with your inventory, a quick fix using tabinvmodifier
create rules file 5H.rules:

Nw: 5H 1980/001
Sa: End=2025/001 * *,* *,*,*

write into database (spread must be running):

bin/seiscomp exec tabinvmodifier -r 5H.rules

all stations/locations/channels of network 5H will now have end date 2025-01-01T00:00:00
Don't set the time too late though, 2049 will set the end date to 1912 ... but that's a problem for the next generation.

[jsaul]

I committed a fix to the issue. Please give it a try.