DM-51096: Use toy pointing model to calculate mount error#150
Merged
mfisherlevine merged 5 commits intomainfrom Jun 2, 2025
Merged
DM-51096: Use toy pointing model to calculate mount error#150mfisherlevine merged 5 commits intomainfrom
mfisherlevine merged 5 commits intomainfrom
Conversation
Contributor
Author
|
I made the above changes that we discussed. Attached are plots of three different expIds, one good one and two of the trailed images from last week that weren't caught. A simple linear model of the Az/El/Rot changes seems to work fine. The way it works is that the standard method is to calculate the RMS(actualPosition-demandPosition). Here we first calculate RMS(actualPosition-modelPosition) and if that RMS is less than some value (here set to 1.0 arcsec for Az and El and 5.0 arcsec for Rot), we use the standard RMS. If it is greater than that value , then we replace the (actualPosition-demandPosition) errors with the (actualPosition-modelPosition) errors. Here is a PR, but maybe more changes are needed. |
mfisherlevine
force-pushed
the
tickets/DM-51096
branch
from
64c24f6 to
7924174
Compare
Use the exposure's time on sky, the tracking ra/dec and the location of the telescope to make a linear pointing model to calculate the residuals from, to be able to see when the real pointing model was not supplying values or the TMA wasn't tracking for any other reason, in order to be able to identified streaked images.
mfisherlevine
force-pushed
the
tickets/DM-51096
branch
from
7924174 to
67f568c
Compare
mfisherlevine
changed the title
mfisherlevine
force-pushed
the
tickets/DM-51096
branch
from
67f568c to
1e3a20e
Compare
mfisherlevine
force-pushed
the
tickets/DM-51096
branch
from
b7a1d91 to
21594b3
Compare
mfisherlevine
approved these changes
Jun 2, 2025
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 have been several recent exposures where the images were obviously streaked, but the RubinTV Mount Torque plots reported no issue. This is because the difference between the demand position and the actual position was small because the demand position was not doing what it should. Examples are 2025051900417, where the mount was not tracking, and 2025052000321, where the rotator was still moving rapidly during the exposure. Plots and images attached. In both cases the Mount motion image degradation reported a small value even though the images were unacceptable. The idea is to install a simplified MTPtg model in the mount analysis code in summit_utils to try and flag these. This code seems to do that.