Does the APCC model erase the results of the Keypad Ortho Model or simply override it?
If the APCC pointing corrections are turned off, does the most recent Keypad Ortho Model once again take effect or does a new one need to be built?
APCC does not erase the keypad ortho model. The keypad model resides in the CP controller and is used to compensate for non-orthogonality at all times, whether an external model is used or not. Once created, it does not turn off. External models will actually use it without knowing that it's there. It is as if the scope is now perfectly orthogonal, so any external model would not have any ortho component in their data.
From: John Upton <upton@...>
Sent: Tue, Sep 14, 2021 9:56 pm
Subject: [ap-gto] Interactions Between Keypad and APCC Orthogonality Models? #Mach2GTO #APCC #Keypad
I am looking for some clarifications regarding the interactions / interoperability of the Ortho Model performed by the Keypad versus the pointing model created by APCC? The questions I want to understand are:
For some observing and simple single object imaging sessions, I think I would like to just have the orthogonality error corrected without creating / running a normal pointing model. It would simplify / speed up plate solving on both sides of the meridian. Ideally, for a quick portable imaging session, I would prefer not to have to rerun the Keypad Ortho Model at the beginning of each session when I don't want to run APPM. I will be guiding for these sessions and since they involve only a single target, plate solving will suffice for the evening's only target.
- I assume the APCC model takes precedence when a Keypad Ortho Model has been built. Is that correct?
- Does the APCC model erase the results of the Keypad Ortho Model or simply override it?
- If the APCC pointing corrections are turned off, does the most recent Keypad Ortho Model once again take effect or does a new one need to be built?