MSEED files support #283
Open
MSEED files support #283
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Gautzilla
added
the
data format
Contributor
Author
|
I'm still trying to figure out a way of creating small mseed files on the fly for adding the feature to the test suite. |
Contributor
|
I think @cazaudo is better suited to review this PR. |
cazaudo
approved these changes
Dec 18, 2025
Contributor
Author
|
Note for 2026: I tried to isolate the obspy-dependent part to keep basic users from the obspy/windows hell. I still have some tests that don't pass: maybe it is because i changed the data returned by get_data() to a 2D array? I'll have to look back at it in january! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🐳 What's new?
This PR adds support for accessing MiniSEED data within the osekit ecosystem.
🐳 How does it work?
The metadata/data access is based on ObsPy.
The osekit AudioFileManager has been tweaked so that reading .mseed info/data use ObsPy rather than soundlib.
As ObsPy doesn't access data lazily with frame indexes, the AudioFileManager loads the entire file data and returns the requested frames afterwards.
🐳 Note
The MiniSEED data seems to be stored as large integer values (at least, that is the case with the OOI dataset). Hence, I'd recommend normalizing the data with
Normalization.PEAKto get it back into the WAV data[0.,1.]range.resolve #282