Open liamtoney opened 5 years ago
This seems like a good idea, but I'm not sure how we would treat the metadata. Perhaps have a related script that generates an xml response file or something?
There are sort of two issues here now.
If we accomplish both of these, we'd have an end-to-end (DATA-CUBE3 to EarthScope) solution — which would be nice. @uafgeotools/watc staff have existing tools for creating ObsPy Inventory
objects from scratch — these then can be exported as StationXML, validated, etc. This would provide another option along with the GUI-based approach using EarthScope's Portable Data Collection Center (PDCC) (that code hasn't been updated since 2015, maybe it's aging out?).
I think this could be accomplished without introducing any breaking changes, meaning that backwards compatibility remains for those already using this tool. Thoughts @jegestrich @davidfee5 @amiezzi?
tools for creating ObsPy
Inventory
objects from scratch
This tutorial from the ObsPy docs basically shows exactly what we'd want — note that use of the obspy.clients.nrl
module to facilitate access to the Nominal Response Library (NRL). Some adjustments are needed for infrasound data, but again, these have already been implemented in WATC codes.
2. Potentially adding functionality for the script to output StationXML files as well. These can be converted to dataless SEED (an older format) for EarthScope submission.
Work on this is being done in a private repo for the case of Yasur 2023 deployment. Script could be generalized and included in this repo. I think having it be a separate script probably makes more sense than making cube_convert.py
even larger...?
Right now the code automatically "removes the response" by simply dividing by a calibration value. However, we might not want to automatically do this. Potentially a future thing to address...