Skip to content

Conversation

@fpezzinosn
Copy link
Contributor

Description

@swift-nav/devinfra

Added 3 new messages related to Atmospheric Corrections and Bounds

  • MSG_SSR_STEC_CORRECTION (new evolution of SBP 1531): One Message per Tile
  • MSG_SSR_GRIDDED_CORRECTION_BOUNDS (new extension of SBP 1532, TROPO + Residuals)
  • MSG_SSR_TILE_DEFINITION (new evolution of SBP 1526)

API compatibility

Does this change introduce a API compatibility risk?

No, just adding new messages.

API compatibility plan

If the above is "Yes", please detail the compatibility (or migration) plan:

JIRA Reference

https://swift-nav.atlassian.net/browse/OTA-120

@fpezzinosn fpezzinosn force-pushed the fpezzinosn/OTA-120 branch from c8e70e3 to c36f4e1 Compare May 5, 2022 14:31
@fpezzinosn fpezzinosn force-pushed the fpezzinosn/OTA-120 branch from c36f4e1 to 13e0b06 Compare May 5, 2022 15:19
@fpezzinosn fpezzinosn self-assigned this May 5, 2022
@fpezzinosn fpezzinosn marked this pull request as ready for review May 5, 2022 15:21
@fpezzinosn fpezzinosn requested review from a team and notoriaga as code owners May 5, 2022 15:21
type: u8
desc: SSR Solution ID.

- MSG_SSR_STEC_CORRECTION_NEW:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll look for a better name to differentiate it with the existing message, _NEW isn't the best of suffixes

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Standard procedure here is to add _DEP (or _DEP_A if _DEP already exists) for the existing message and have this new message occupy the old name. I would go ahead and do that in this PR since these messages should be treated like the real thing.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And what happens with the IDs of the messages?
The message validator threw the following Previous ID: 1531, Current ID: 1533, so I guess I should have kept the original ID.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@isaactorz ^^ this is a bug with the message validator that we didn't notice during review, it's a common pattern to rename messages (the ID and contents of the message must remain the same)

@fpezzinosn fpezzinosn merged commit d506873 into staging May 6, 2022
@fpezzinosn fpezzinosn deleted the fpezzinosn/OTA-120 branch May 6, 2022 20:01
fpezzinosn added a commit that referenced this pull request Jun 17, 2022
Co-authored-by: Jason Mobarak <jason@swift-nav.com>
fpezzinosn added a commit that referenced this pull request Jun 17, 2022
* Add support for SSR_ORBIT_CLOCK_BOUNDS message [OTA-65] (#1108)

* Add support for MSG_SSR_CODE_PHASE_BIASES_BOUNDS message [OTA-119] (#1127)

* Add Atmospheric Corrections and Bounds [OTA-120] (#1131)

Co-authored-by: Jason Mobarak <jason@swift-nav.com>

* Add support for MSG_SSR_ORBIT_CLOCK_BOUNDS_DEGRADATION message [OTA-133] (#1137)

* Add Integrity Flags messages [OTA-121] (#1132)

* Add transformation parameter message [OTA-149] (#1144)

* Add leap second message [OTA-148] (#1145)

* Clean up the documentation for the new messages [OTA-150] (#1149)

Co-authored-by: swiftnav-svc-jenkins <42622338+swiftnav-svc-jenkins@users.noreply.github.com>
Co-authored-by: Jason Mobarak <jason@swift-nav.com>

* Updates messages to ICD v1.2 [OTA-161] (#1155)

* make all

Co-authored-by: Jason Mobarak <jason@swift-nav.com>
Co-authored-by: swiftnav-svc-jenkins <42622338+swiftnav-svc-jenkins@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants