Handle 2 or more sensors at a station in a way that passes XML validator

This is an issue the data group has been aware of, but although I brought it up as an issue to open last year, I was previously waiting to open until more existing issues were addressed.

Currently Nexus handles 2 or more sensors at one station by the split channel button. This creates two (or more) overlapping station epochs, which causes failure against rule 111 of the stationXML validator.

We have been rearranging by hand as needed so all the channels are under the same station epoch, either in the raw XML or in PDCC, but this is laborious and error-prone. This issue also has renewed importance since Erebus (201939) currently has 2 sensors at 2 stations and that will expand in the future.

added 1 deleted label

Here are the files requested in the software meeting, a little background on them, and the validation failures (which relate to a couple of other feature requests). Please let me know if you have questions. I am running validation with version 1.7.1 installed on ph51.

1. 2H.ErebusInterim.full.2022094.xml includes two stations, CONZ and ELHT, with two sensors, and this xml will fail rule 111. In this case, each sensor type is also connected to its own datalogger: Q330+Nanometrics Trillium, and Centaur+Nanometrics Titan. I scanned in the Titan data, then used the split channel button in Nexus. You may also want to note that for CONZ, there are two epochs for the Centaur+Titan I created using the split by time button, so I could migrate them to the appropriate epoch with the broadband, which had a datalogger swap (serial number only, no type change) after the Centaur+Titan was installed. ELHT did not have this swap and is a more simple case of the rule 111 failure. Here are the first failures (remainder are all rule 304, which is issue #32 (closed) ) for this stationXML:
   java -jar ${CONDA_PREFIX}/jar/stationxml-validator.jar --input 2H.ErebusInterim.full.2022094.xml --ignore-warnings
   111,Error,2H,,,,2016-12-18T00:00:00,2022-12-31T23:59:00,Sta: CONZ 2019-01-08T08:00:00 2022-01-27T18:00:00 epoch overlaps with CONZ 2020-01-12T03:45:00 2022-01-27T18:00:00
   111,Error,2H,,,,2016-12-18T00:00:00,2022-12-31T23:59:00,Sta: CONZ 2022-01-27T18:00:00 2022-12-31T23:59:00 epoch overlaps with CONZ 2022-01-27T18:00:00 2022-12-31T23:59:59
   111,Error,2H,,,,2016-12-18T00:00:00,2022-12-31T23:59:00,Sta: ELHT 2018-12-29T09:00:00 2022-12-31T23:59:59 epoch overlaps with ELHT 2020-01-06T03:44:00 2022-12-31T23:59:00
   112,Error,2H,,,,2016-12-18T00:00:00,2022-12-31T23:59:00,Sta: CONZ endDate 2022-12-31T23:59:59 cannot occur after network endDate 2022-12-31T23:59:00
   112,Error,2H,,,,2016-12-18T00:00:00,2022-12-31T23:59:00,Sta: ELHT endDate 2022-12-31T23:59:59 cannot occur after network endDate 2022-12-31T23:59:00
   112,Error,2H,,,,2016-12-18T00:00:00,2022-12-31T23:59:00,Sta: NAUS endDate 2022-12-31T23:59:59 cannot occur after network endDate 2022-12-31T23:59:00
   212,Error,2H,CONZ,,,2020-01-12T03:45:00,2022-01-27T18:00:00,Chan: LN1 Loc: 10 startDate 2020-01-12T03:43:18 cannot occur before Station startDate 2020-01-12T03:45:00
   212,Error,2H,CONZ,,,2020-01-12T03:45:00,2022-01-27T18:00:00,Chan: LN2 Loc: 10 startDate 2020-01-12T03:43:17 cannot occur before Station startDate 2020-01-12T03:45:00
   212,Error,2H,CONZ,,,2020-01-12T03:45:00,2022-01-27T18:00:00,Chan: LNZ Loc: 10 startDate 2020-01-12T03:43:18 cannot occur before Station startDate 2020-01-12T03:45:00

2. 2H.ErebusInterim.fullarrange.2022094.xml is the version I converted to dataless to validate and run checks on QC to archive the data. The Centaur+Titan epochs for CONZ and ELHT have been migrated (via copy and pasting of the xml contents) to fall under the respective Q330+Trillium epochs that encompass them. This version passes rule 111, although because I set the network end time in the GUI it again fails rule 112, which relates to #35 (closed). I have included the first failures (the remainder are all rule 304). However, because dataless does not contain network start & end times, this failure did not affect archival of the data at the DMC. java -jar ${CONDA_PREFIX}/jar/stationxml-validator.jar --input 2H.ErebusInterim.fullarrange.2022094.xml --ignore-warnings
   112,Error,2H,,,,2016-12-18T00:00:00,2022-12-31T23:59:00,Sta: CONZ endDate 2022-12-31T23:59:59 cannot occur after network endDate 2022-12-31T23:59:00
   112,Error,2H,,,,2016-12-18T00:00:00,2022-12-31T23:59:00,Sta: ELHT endDate 2022-12-31T23:59:59 cannot occur after network endDate 2022-12-31T23:59:00
   112,Error,2H,,,,2016-12-18T00:00:00,2022-12-31T23:59:00,Sta: NAUS endDate 2022-12-31T23:59:59 cannot occur after network endDate 2022-12-31T23:59:00

2H.ErebusInterim.full.2022094.xml

2H.ErebusInterim.fullarrange.2022094.xml

added PriorityMedium label

removed 1 deleted label

added Type: Bug Type: Enhancement labels

added For: Data label

marked this issue as related to #32 (closed)

Following conversation with the data group, addressing this issue will most likely require some code refactoring.

Sensors would be best handled at the Channel level instead of the Station one.