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
So this may take a bit of work to develop, but a very useful feature to have in Obspyck would be to make multiple picks per trace over long timescales (e.g. one day), then associate these picks to specific events for doing single-event locations or for cutting slicing discrete waveforms for further analysis. This feature would be great for picking aftershock datasets where there are many seismic events per day.
I guess you would need a window containing a table showing all the existing picks for multiple stations, then you'd be able to select a group of picks and associate them to an individual event. The user could then calculate multiple event locations per obspyck 'session'.
This would certainly be on my wish-list, but I completely understand if it is unfeasible right now.
The text was updated successfully, but these errors were encountered:
So this may take a bit of work to develop, but a very useful feature to have in Obspyck would be to make multiple picks per trace over long timescales (e.g. one day), then associate these picks to specific events for doing single-event locations or for cutting slicing discrete waveforms for further analysis. This feature would be great for picking aftershock datasets where there are many seismic events per day.
I guess you would need a window containing a table showing all the existing picks for multiple stations, then you'd be able to select a group of picks and associate them to an individual event. The user could then calculate multiple event locations per obspyck 'session'.
This would certainly be on my wish-list, but I completely understand if it is unfeasible right now.
The text was updated successfully, but these errors were encountered: