You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
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.
The text was updated successfully, but these errors were encountered: