Conversation
GNSSSignals.jl 2.6 defines GalileoE1B_BOC11, the BOC(1,1) approximation of Galileo E1B that software receivers substitute for the full CBOC(6,1,1/11) spec. It carries the identical I/NAV navigation message (same 4092-chip primary code, 250 bps data rate, page/word structure); only the RF modulation differs, which is a tracking/acquisition concern. Dispatch GNSSDecoderState(::GalileoE1B_BOC11, prn) to the existing E1B decoder unchanged, add a constructor test, and note the support in the README. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
giove-a
changed the title
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #69 +/- ##
=======================================
Coverage 98.15% 98.15%
=======================================
Files 14 14
Lines 1515 1517 +2
=======================================
+ Hits 1487 1489 +2
Misses 28 28 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Summary
Adds decoder support for
GalileoE1B_BOC11, the BOC(1,1) approximation of Galileo E1B introduced in GNSSSignals.jl 2.6.Software receivers commonly substitute a pure BOC(1,1) replica for the full CBOC(6,1,1/11) spec (lower sampling rate, ~0.45 dB correlation loss). The two are distinct signal types in GNSSSignals.jl, but they carry the identical I/NAV navigation message — same 4092-chip primary code, same 250 bps data rate, same page/word structure. The difference is purely in the RF modulation, which is a tracking/acquisition concern, not a navigation-message decoding one.
Accordingly,
GNSSDecoderState(::GalileoE1B_BOC11, prn)dispatches to the existing E1B decoder unchanged, rather than duplicating the Constants/Data/Cache/parsing stack.Changes
src/galileo/e1b.jl— addGNSSDecoderState(::GalileoE1B_BOC11, prn)mapping toGalileoE1BDecoderState, with a comment explaining why the decoder is shared.test/galileo_e1b.jl— add a constructor testset asserting the BOC(1,1) state equals both the direct constructor and the full-CBOC E1B state.README.md— note the BOC(1,1) approximation under supported signals.Notes
GalileoE1B_BOC11is present in the already-required GNSSSignals2.6.GPSL1C_P,GPSL2CL,GPSL5Q,GalileoE1C,GalileoE1C_BOC11,GalileoE5aQ) are all dataless pilot components (get_data_frequency == 0 Hz) with no navigation message to decode.Testing
Galileo E1B test suite passes (16/16), including the 2 new BOC(1,1) constructor tests.
🤖 Generated with Claude Code