8000 Feature Request: Waveform plots ordered by order in weights.dat · Issue #299 · mtuqorg/mtuq · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Feature Request: Waveform plots ordered by order in weights.dat #299

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
ammcpherson opened this issue Feb 17, 2025 · 2 comments
Open

Feature Request: Waveform plots ordered by order in weights.dat #299

ammcpherson opened this issue Feb 17, 2025 · 2 comments

Comments

@ammcpherson
Copy link
Member

Hello,

Currently the waveform plots seem to have a default ordering option of 'by_azimuth', and users can of course choose to sort 'by_distance' or 'by_azimuth.' In the old CAP code, if you did not choose an ordering option, it would order the waveforms by the order in the weights.dat file. This offers immense customization about what waveforms to showcase, particularly in the case where the user has a large number of stations (>10) and needs to crop the wavefield plot for publication purposes.

Thanks,
Amanda
@rmodrak
Copy link
Member
rmodrak commented Feb 17, 2025

Perhaps try your hand at this using the following?
Dataset.sort_by_function(function, reverse=False)

@rmodrak
Copy link
Member
rmodrak commented Feb 17, 2025

One possible complicating factor is that weights are defined per trace, whereas sorting would occur per station (because datasets are organized per station).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rmodrak @ammcpherson
0