Ken can you explain why the session was aborted around 02.46.40? Also, I see that around 02.45.11 Meridian Flip failed but the flip had already happened after the midnight. Do I read this right?
Finally, what happens when I get the message “plate solve might be bad” or something like that and if I don’t click “OK” and ask the sequence to continue? Is the sequence aborted in that case?
Aprox time of issue: <02.46.40>
Link to Logs
Useful Info
OS: Microsoft Windows 10 Pro Ver: 3.1.0.457 .NET: 4.8
There is a safety mechanism built in that attempts to prevent a wild slew based on a potentially bad solve. In this case you asked your mount to slew here:
Telescope: Slewing to J2000 RA: 12.0312333333333 (12h01m52.44s) Dec: -18.8942972222222 (-18°53'39.47")
But you ended up more than an hour away. ASTAP still managed to solve it, but SGPro was unsure because of the large error. After this, the blind solver took over and then a bug in SGPro exposed itself. Here, the solver is not supposed to consider large differences in in location as an issue because it is literally designed to compensate for this situation (blind solves should only validate scale). I’ll fix that up.