Open
Conversation
…algorithm to correctly emit events in case of sparse messages, use clock-time punctuator, and remove duplicate events
Standalone build via docker compose works locally
…ender to handle rtcm timestamps
linda-baker
reviewed
Jan 15, 2026
linda-baker
left a comment
linda-baker
left a comment
There was a problem hiding this comment.
ReflectionDiffBuilder seems like exactly what I was missing when I set up the BSM/SPAT/MAP message progression counts in the first place. Seems like a solid way to handle the diffs.
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
4 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.
Implements requirements to perform CTI-4501 validation on RTCM messages in the CIMMS
Included:
References are to the Software Design Document, July 2025 update.
The Message Count Progression and Minimum Data Events include the ability to aggregate the events.
Not included:
Broadcast Rate Event Aggregation - The SDD mentions that broadcast rate events should be aggregated but does not provide a design or data structure; see issue: MAP/SPAT/RTCM Broadcast Rate Event Aggregation #10 so broadcast rate event aggregation is not implemented here pending discussion and clarification of the design to be done in a later, separate PR.
Broadcast Rate Notification Configuration - The SDD contains "Table 16: Broadcast Rate Notification Configuration" but has a comment saying notification configuration may not be necessary because the required broadcast rate is well-defined by CTI-4501. Also there is no algorithm defined for these notifications, so no additional "Notification" messages are generated beyond the individual Events in this PR.
Tests
The
test-runner-clitool is updated to be able to create and send integration test scripts that include RTCMs.Includes unit and integration tests for each new topology.
Integration test documentation is added to the Wiki:
Verified new and existing unit and integration tests pass.