It is barely possible to restructure the data flow without touching the usage of the data objects. Thus, I suggest to refactor the entire PyLoT code and try to debug the following code blob…
HASH format is now missing in
writephasesneeds to be re-implemented.
Done with [cb457fc7ec](marcel/pylot#39/commits/cb457fc7ec5b5260a0315cd9d4…
Removed unnecessary code. Trying to get an overview of the data handling to be able to further simplify. These changes might break PyLoT in the first place but fixing makes it better than before.
I just saw that obspy.io nowadays supports many of the file formats which are used by PyLoT. Instead of using untested self-written code, PyLoT should exploit the capabilities of obspy.
HASH format is now missing in writephases needs to be re-implemented.
There is no difference between ObspyDMTdataStructure and PilotDataStructure. Why are both implemented?
For actual implementation I would need a test data set. Alternatively, @marcel takes the implementation on this branch for testing purposes. Are there other data structures in use?
This is the…
Design proposal:
- separate data
- event data
- waveform data
- remove structure
- replace by data handlers for
- event data
- waveform data …
- replace by data handlers for