Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't automatically convert to Pa? #1

Open
liamtoney opened this issue Sep 20, 2019 · 4 comments
Open

Don't automatically convert to Pa? #1

liamtoney opened this issue Sep 20, 2019 · 4 comments
Labels
enhancement New feature or request question Further information is requested

Comments

@liamtoney
Copy link
Member

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...

@liamtoney liamtoney added the question Further information is requested label Sep 20, 2019
@liamtoney liamtoney pinned this issue Apr 17, 2020
@davidfee5
Copy link
Member

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?

@liamtoney liamtoney unpinned this issue Jul 15, 2022
@liamtoney liamtoney added the enhancement New feature or request label Sep 22, 2023
@liamtoney liamtoney pinned this issue Sep 22, 2023
@liamtoney
Copy link
Member Author

There are sort of two issues here now.

  1. Ensuring the script can output miniSEED files in the form that EarthScope wants them.
  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.

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?

@liamtoney
Copy link
Member Author

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.

@liamtoney
Copy link
Member Author

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...?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants