POCS
POCS copied to clipboard
panoptes
Adjust Duration Constraint for time past meridian
The Duration constraint currently has a few flaws, most notably that it is only checking for the time when the target hit meridian when the mount allows for tracking up to 30° (2 hours) past the meridian. This is causing a number of viable transits to not get scheduled because it thinks they need to stop at meridian.
Simple fix is to add 2 hours to the time of the meridian. Note that this does require the mount be properly set to this behavior although that is what our setup instructions currently specify.
Note that it also appears there are just some small bugs in the Duration constraint as well.
On PAN001 I added 2 hours to the time past meridian, which is the same as what happens in the PR that I'm working on. The target in question passed the meridian at 08:05 UTC so should have gone until 10:05, but ended up hitting the limit at about 09:37(with star trail showing in the last image).
Image: Wasp50/14d3bd/20181209T050632/20181209T093737.fits HA-MNT: 1.5478°
Similar to the above, the last observation of the night for PAN001 last night only did 46 of 60 exposures before it hit the limit. Actually star trails appear at the second to last exposure with the last exposure just being star trails.
Image: Tess_Sec07_Cam01/14d3bd/20181209T123831/20181209T144733.fits HA-MNT: 1.7614
Based on the above I will probably set this for 1.5 hours instead of 2 hours. Not sure if the discrepancy is because of a mis-alignment so this should be re-examined on a unit with better alignment/tracking.