Repository navigation
Add the element inspector panel - #82
Merged
Merged
Conversation
One PropertyGrid section per OMM field showing the value, the step the format writes it to, and the metres one step is worth at a chosen horizon, from DataTerm. Orbital fields are editable and the sensitivities follow. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0172daf2smMjPmMGvUhQo9fH
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
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.
Requested by Matt · project thread
Before: the app had no way to see what each element-set field's quantization is worth;
DataTermexisted only behind tests.After:
ElementInspectorPanelshows onePropertyGridsection per OMM field with its value, the step the format writes it to, and the metres one step moves the position at a horizon chosen with a slider (0–30 days). The combined data term sits at the top. Orbital fields are editable, the sensitivities recompute on each edit, and "Reset to as written" restores the element set.How: each figure is
DataTerm.Measure's half-step shift for that field, doubled to read per whole step (linearised ∂r/∂field). The epoch is shown with its step but marked not measured, becauseDataTermdoes not perturb it yet (item 27, #23).MEAN_MOTION_DDOTreads 0 m because SGP4 never reads it. Identity fields sit in a collapsed section. Until the catalogue panel lands, the panel shows the ISS element set committed inTleParserTests, andSelect(ElementSet)is the hook the catalogue will call.Not yet registered with the app: the shell (item 10) has not merged, so the one-line registration follows in a later commit once it does. Rendered headlessly through
ImGuiAppHarnessto check it draws without ImGui asserts (ISS, 1 day: data term 10.4 m; RAAN, argument of perigee and mean anomaly about 11.9 m per step each; mean motion 0.43 m). No committed test:Osculator.Testsdoes not reference the app project, and the arithmetic isDataTerm's, whichDataTermTestsalready covers.Fixes #33
🤖 Generated with Claude Code
https://claude.ai/code/session_0172daf2smMjPmMGvUhQo9fH
Generated by Claude Code