Fix timesystem config #252
Open
Conversation
This file contains 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
added 4 commits
December 15, 2024 16:36
1. time system boundary settings 2. realtime preset settings 3. Time system presets 4. Realtiem presets.
…le proper setting of bounds and presets.
|
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.
Closes #52 and addresses https://jira.jpl.nasa.gov/browse/OMM-104.
Updates the timeSystems configuration in config.js and the time plugin to allow for setting of default bounds, presets, and clockoffsets for applicable modes (fixed/realtime), time systems (scet/ert/etc), and clocks (scet.lad, ert.lad, etc)
Settings are now modified in a modeSettings object that contains entries for
Documentation is updated to show how these settings are used.
Note: This requires the following change in core to apply the default time conductor bounds:
nasa/openmct#7964
Note: This will only apply to the first load. Another change to core needs to be enabled to enforce default bounds on time system change. I'm not sure where this might be applied and was hoping someone could point me to it.