We were observing objects that were very far west. RTS2 continued to follow objects to airmass ~ 3, I am not sure if this is beyond the actual software limit horizon, but it was outside the horizon plotted in xephem. We should re-implement airmass limits per target so it doesn't observe that low anyway.
At about 3:57 AM it was pointed about 5 hours west, and should have slewed to a new target that was only 2.5 hours west, but did not, emitting an error message that the target was below the horizon. (Either its computation was flawed, or it skipped the target for some reason and then went to the next in queue, which actually was below the horizon.) However, it kept taking images at the old target and putting them in the new target's directory. I set rts2-mon to off, stowed the telescope, added the target back into the queue, and set rts2-mon back on. It was then able to slew to the target.
We were observing objects that were very far west. RTS2 continued to follow objects to airmass ~ 3, I am not sure if this is beyond the actual software limit horizon, but it was outside the horizon plotted in xephem. We should re-implement airmass limits per target so it doesn't observe that low anyway.
At about 3:57 AM it was pointed about 5 hours west, and should have slewed to a new target that was only 2.5 hours west, but did not, emitting an error message that the target was below the horizon. (Either its computation was flawed, or it skipped the target for some reason and then went to the next in queue, which actually was below the horizon.) However, it kept taking images at the old target and putting them in the new target's directory. I set rts2-mon to off, stowed the telescope, added the target back into the queue, and set rts2-mon back on. It was then able to slew to the target.