Feature: Blue Support #122
Merged
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
777arc
approved these changes
Jan 5, 2026
Member
|
Thanks for all the great effort @Teque5 !!!! |
Teque5
force-pushed
the
feature/blue
branch
2 times, most recently
from
93d0eef to
deaea7a
Compare
Teque5
force-pushed
the
feature/blue
branch
3 times, most recently
from
f32a5df to
cf17f1f
Compare
Teque5
force-pushed
the
feature/blue
branch
2 times, most recently
from
77bb858 to
eb83345
Compare
* Non-SigMF Converters
* Initial code by KelseyCreekSoftware
* fromfile() now autodetects SigMF, BLUE, & WAV formats automatically
* allow converters to --archive (.sigmf) or create SigMF pairs (.sigmf-data & .sigmf-meta)
* Converters now support conversion to non-conforming dataset without
writing datafiles back to disk
* BLUE
* Validated implementation against lots of files beyond nonsigmf-examples repO
* parse into (fixed, adjunct, extended) keys
* add CRC validation for bluefile metadata
* add support for metadata-only (0 sample) BLUE files
* WAV
* Drop support for float WAV files; tricky to support NCD
* Single entry point (sigmf_convert)
* conversion returns metadata for newly created file
* enforce checksum calculation
* account for metadata-only files with heading & trailing bytes
* ensure for NCD conversion that both input & output are in same folder
* homologate API for wav & blue converter
* integrate feedback from KelseyCreekSoftware
* add conversion checks
* add UX improvements
* windows path issues
* require input and output files for converters
* NCD Improvements
* fixed some usage edge cases with all NCD files
* Fix bug in sigmffile._count_samples for NCD files
* Fig bug in read_samples when using some NCD files with header & trailing bytes
* Hashing
* simplify implementation
* add related tests
* move from sigmf_hash to hashing -> API change
* Docs
* new docs for converters
* simplify doc build procedure
* rewrite general use patterns
* added support table for BLUE format codes
* Tests
* add tests for blue (.cdif) and wav (.wav) converters
* added tests for all supported BLUE types
* split converter tests into separate files
* allow epsilon differences due to float conversion patterns
* simplify wav tests
* Project
* Increment to v1.6.0
* Simplified install: drop scipy optional dependency and [apps] entirely
* Add utils.get_magic_bytes() for autodetection purposes
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In addition to adding support for common BLUE/Platinum files this PR also fixes some unreported bugs related to reading captures when
header_bytesandtrailing_bytesexist.I validated the bluefile i/o against nonsigmf examples repo and many other
.cdiffiles I had around.TODO before converting to full PR:
Now ready.