Provide calibrated units and pixel uncertainty metadata to Data Tool - #74
Draft
paulnord wants to merge 2 commits into
Draft
Provide calibrated units and pixel uncertainty metadata to Data Tool#74paulnord wants to merge 2 commits into
paulnord wants to merge 2 commits into
Conversation
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
1 participant
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.
Connect Tracker's existing units, pixel calibration, and position/time column identities to the Data Tool fit-report features in OpenSourcePhysics/osp#9. Requires that OSP API; this is the small companion change, with no AutoTracker implementation changes.
Data Tool receives live metadata through FitMetadataProvider. Source dataset IDs and column IDs preserve provenance through local column names. Tracker table exports retain metadata units even when displayed units are hidden.
Pixel uncertainty is offered only for directly calibrated PointMass x/y with known length units and a constant conversion. The adapter uses the relevant image-to-world transform row norm, including rotation and anisotropic scale. Derived quantities and varying calibration are excluded.
A position-component callback identifies position versus time so OSP can include line-fit velocity and quadratic-fit velocity at t=0 and acceleration in copied reports. It does not label position-versus-position or derivative columns as position data. No tracking, optimizer, numerical derivative, or project-file behavior changes.
Validation: builds against the updated OSP classes on macOS; 17 real Tracker calibration and column-identity checks pass. The changed metadata adapter transpiles with SwingJS; the other three source files passed transpilation earlier. OSP's desktop and Chromium/Firefox/WebKit suites exercise the consumer API, layout, and copied motion results. The Tracker integration fixture was not run inside a browser or on native Windows/Linux.
Integration notes and the standalone test are in test/FIT_METADATA.md.