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
Move plot class and associated functions to own submodule in order to
reduce the amount of code held in signal/scan.py. Generally more logical
to have them separated for clarity. Does not close issue #33 but is a
good start.
Addresses issue #33
For now I have just moved the SeisPlot class to a new submodule, plot. I still think breaking this down into separate scripts in the submodule for each type of plot will help clean up the code somewhat, but the priority was to reduce the amount of code in signal/scan.py
Summary plots for triggered event summaries and located events summaries have been revamped and the plotting functions moved to independent submodules in the plot module.
The only remaining work to be done is the coalescence video.
hemmelig
changed the title
plot submodule
Plotting submodule - deprecation of QuakePlot class
May 29, 2020
I propose moving the SeisPlot class out into a submodule QMigrate.plot that contains a series of functions that can be called to plot:
In theory this is an entirely internal change, so I see zero change for end users.
It has the added benefit of reducing complexity of the signal/scan.py file.
The text was updated successfully, but these errors were encountered: