DM-47874: Use new timestamps in TMA tracking errors#133
Merged
mfisherlevine merged 6 commits intomainfrom Apr 3, 2025
Merged
Conversation
mfisherlevine
force-pushed
the
tickets/DM-47607
branch
from
069c01f to
ec0ad1d
Compare
mfisherlevine
force-pushed
the
tickets/DM-47874
branch
from
e862a7e to
a9f0fa0
Compare
mfisherlevine
force-pushed
the
tickets/DM-47607
branch
from
cdfd34b to
817bedb
Compare
mfisherlevine
force-pushed
the
tickets/DM-47874
branch
from
a28c958 to
2215456
Compare
mfisherlevine
changed the title
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
2 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.
There has been an ongoing problem with single point errors in the TMA data stream. These are explained in more detail in chapter “Single point errors in the tracking data stream” of TMA tracking jitter and settling time analysis . Julen of Tekniker has now added additional time stamps so that each data stream has it’s own timestamp. This should eliminate those errors. This ticket will implement the use of those new timestamps in the RubinTV tracking error plots, which should eliminat the need for the filterBadValues code.