search

adjtomo / pysep

Seismogram Extraction and Processing: Seismic data retrieval and record sections
https://pysep.readthedocs.io
MIT License
29 stars 15 forks source link

vertical marker lines for record sections #70

Open carltape opened 1 year ago

carltape commented 1 year ago

In some cases it is nice to see reference lines that are specified by the user. For example, in the following record section, we want to plot the origin times four different earthquakes: image So the user specifies four absolute times, and IF the record section settings do not contain any requested moveouts (e.g. variable time shifts applied to seismograms), then the plot will display vertical lines. In this example, it helps show that many of these waveforms are associated with triggered earthquakes that are designated by the user-entered times. Thanks!

bch0w commented 1 year ago

@aakash10gupta @carltape

This is addressed in the latest devel branch. See https://github.com/adjtomo/pysep/pull/73 for how to implement

aakash10gupta commented 1 year ago

@bch0w the above mentioned commit does address the issue if the input tmarks are provide in time units of seconds from the reference origin time. It seems that tmarks inputs in UTCDateTime format are not yet handled though. I can see the utility of such an option especially when studying triggered events and aftershocks. I can see that this can be easily done on the user side as well, so I wanted to open this up for discussion.

bch0w commented 1 year ago

@aakash10gupta This might get tricky when mixing absolute/UTC time markers with time shifts, since any trace with a time shift now has a different definition of T=0. For a standard, distance sorted, no time-shift record section, I agree this is will be easy, but it quickly gets complicated when trying to account for time shifts and all available sorting options.

I think @carltape Matlab scripts have a curved line that shows the time-shifted tmarks? I can see that working in most cases but it may take some trial and error to find an optimal implementation.

I will re-open this issue since this feature is not as fully-implemented as desired.