-
Notifications
You must be signed in to change notification settings - Fork 4
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
Advice for a different datalogger #3
Comments
Hi @cjhopp, depending on how much data it is I think option 1 would be the quickest way to get started, assuming it is feasible at all. Otherwise both options 2 and 3 are feasible - I cannot comment a lot on option 3 as I don't know the details. I agree that option 2 is potentially a lot of work but it could most likely also be done in a modular way so that DUGSeis works with ASDF and other formats. All of the logic actually reading the files is contained here: https://github.com/swiss-seismological-service/DUGseis/blob/main/dug_seis/waveform_handler/waveform_handler.py All the best, |
Hi @krischer ,
Thanks again, |
Hi @krischer ,
Thanks for this fantastic bit of work! I'm planning to use DUGseis for an upcoming experiment but the seismic data are recorded by a different datalogger than those that have been used by ETH in the past. I've got functions for reading the output data to obspy Streams and also for converting to hdf5 (for use with previous dugseis versions).
My question is: what initial advice would you give for inserting a different waveform reader 'plugin' into DUGseis?
Any quick thoughts you have would be really appreciated,
Chet
The text was updated successfully, but these errors were encountered: