CMD: pyDARM gds restart does not work if the most recently exported report is not the report with the latest id/name.
here's the scenario:
- take new measurements
- create a new report
- export new calibration
- tag & upload the now exported report
- restart gds (here the correct npz is verified as having been sent to dmt1 & dmt2)
- for whatever reason decide that we don't want to keep this cal and need to revert to the old one
- re-export old pydarm report that was previously working (this works as expected, including the generation of a new timestamped tag)
- upload re-exported report to ldas
- restart gds
item 9 above fails because the npz from the re-exported report doesn't seem to make it to the dmt machines for some reason. I just tried to pull the log back up with pydarm gds log
but it's not showing the relevant information anymore. Hopefully someone with access to the dmt machines can pull the logs from late Friday night, near midnight CT.