Open EastEriq opened 4 days ago
Another occurrence yesterday
Taking flats
{14:57:34.644|inst.XerxesMountBinary[08_1]} slewing to RA=351.81, Dec=30.05
{14:57:40.616|obs.unitCS[08]} checking if slaves of unit 08 are ready, #1
{14:57:44.997|obs.unitCS[08]} checking if mount is tracking
{14:57:45.327|obs.unitCS[08]} checking if slaves of unit 08 are ready, #2
{14:57:49.853|obs.unitCS[08]} checking if mount is tracking
{14:57:50.173|obs.unitCS[08]} checking if slaves of unit 08 are ready, #3
{14:57:50.759|obs.unitCS[08]} checking if mount is tracking
{14:57:51.094|obs.unitCS[08]} checking if slaves of unit 08 are ready, #4
{14:57:51.768|obs.unitCS[08]} checking if mount is tracking
{14:57:52.115|obs.unitCS[08]} checking if slaves of unit 08 are ready, #5
{14:57:52.645|obs.unitCS[08]} checking if mount is tracking
{14:57:53.749|obs.unitCS[08]} Cannot get initial brightness estimate. Aborting
Sun at -2.1°, too high to focus - wait, or use ctrl+c to stop the method
Clearly it is about early returns of UnitObj.readyToExpose
in getMeanCountPerSec
(line 296 of takeTwilightFlats.m
). In such cases MeanValPerSec
is returned as NaN and line 116 of takeTwilightFlats.m
rightly terminates the script. (Reminder, a shortcoming of it is that brightness estimates are global for all telescopes, instead of individual).
I'll start with adding some report messages in readyToExpose
, in order to make more apparent what causes the problem, before deciding what to improve.
It happened on two different mounts this evening. The routine was taking images which were still too bright, then printed on stdout
in one instance, and
in the other.
As a side note, all those messages printed to stdout should be made more readable, there is no point in preserving fidelity to original misconceptions.