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

convert seismic data reader and writer into standalone tools #5

Closed
rmodrak opened this issue Dec 17, 2014 · 2 comments
Closed

convert seismic data reader and writer into standalone tools #5

rmodrak opened this issue Dec 17, 2014 · 2 comments

Comments

@rmodrak
Copy link
Collaborator

rmodrak commented Dec 17, 2014

Currently, routines for reading and writing seismic traces are tied to individual solver repositories. Converting them to standalone tools would reduce dependencies between classes and make for a much simpler import system. Before proceeding though, we would need to be sure that our ability to (1) parallelize data processing operations and (2) handle multicomponent data would not be adversely affected.

@rmodrak rmodrak changed the title make seismic data reader and writer into standalone tools convert seismic data reader and writer into standalone tools Dec 18, 2014
@rmodrak
Copy link
Collaborator Author

rmodrak commented Dec 18, 2014

This issue should be considered concurrently with Issue #6 "use obspy input/ouput and signal processing tools where it makes sense".

@rmodrak
Copy link
Collaborator Author

rmodrak commented Dec 21, 2014

This item has been completed: the seismic reader and writer have been decoupled from the solver interfaces. In their place, reader and writer modules have been added to seistools. The import system has been greatly simplified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant