Smart Solo Data Formatted as PH5 Contains Duplicated Traces

[timronan]

In expirment 21-002, 9N 2020, running:
ph5toms -n master.ph5 -p . -s 2020-11-07T18:14:00 -t 2020-11-07T18:16:00 --station 8010 --channel GPZ
leads to an output miniseed that contains:

9N.8010..GPZ | 2020-11-07T18:14:00.000000Z - 2020-11-07T18:15:59.999000Z | 1000.0 Hz, 120000 samples
9N.8010..GPZ | 2020-11-07T18:14:18.000000Z - 2020-11-07T18:15:59.999000Z | 1000.0 Hz, 102000 samples

This seems to be occurring because Smart Solo data does not have a zero padded buffer between epochs.

[hrotman-pic]

I ran this command on the 21-002 archive rebuilt from SEGD that was newly written out in July of 2022. The replacement was submitted in September 2022.
ph5toms -n master.ph5 -s 2020-11-07T18:14:00 -t 2020-11-07T18:16:00 --station 8010 --channel GPZ -o mseed_test8010 -F MSEED

Miniseed output:
mseed_test8010$ msi -S *ms
DCC|2023,037
9N|8010||GPZ|2020,312,18:14:00.000000|2020,312,18:15:59.999000||1000|120000|||||||2023,037

Potentially, this duplication is fixed. I can do more spot checks on the first SmartSolo experiments and if they show the same I think we could close this as resolved by changes to SmartSolo SEGD writeout?