Simulate with inventory #3049
Draft
Simulate with inventory #3049
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
to specify the original instrument for deconvolution part
and use pre_filt instead for stabilizing deconvolution
|
Still needs tests, and |
|
CC @igmuhlmann regarding your gitter post |
|
Bumping this to 1.5.0 |
|
This pull request has been mentioned on ObsPy Forum. There might be relevant details there: https://discourse.obspy.org/t/simulating-instrument-response/1624/2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Makes it possible to use
Inventory/Responseobjects as input inStream/Trace.simulate()andobspy.signal.invsim.simulate_seismometer.Why was it initiated? Any relevant Issues?
These routines are very old, from before these new objects and when mostly poles and zeros dictionaries and the like were used to describe instrument responses.
PR Checklist
masterfor new features,maintenance_...for bug fixesJust add the "build_docs" tag to this PR.
Docs will be served at docs.obspy.org/pr/{branch_name} (do not use master branch).
Please post a link to the relevant piece of documentation.
clients.fdsn) should be tested for the PR,just add the "test_network" tag to this PR.
CHANGELOG.txt.CONTRIBUTORS.txt.from all the CI builds look correct. Add the "upload_plots" tag so that plotting
outputs are attached as artifacts.