Always check meridian flip before starting next capture
ClosedPublic

Authored by wreissenberger on May 5 2019, 2:25 PM.

Details

Summary

Diff D20150 had an unexpected side effect. The check for a meridian flip only took place at the beginning of each capture sequence and not before or after each capture. This diff fixes it by adding an additional meridian flip check before the next capture in a capture sequence is executed.

Test Plan

Bug fix test: create a capture job with a single sequence having many captures. Slew the mount to a position is close to the meridian and start the capture. Expected result is, that the capture sequence is interrupted by a meridian flip and after the meridian flip the imaging session is continued.
Regression tests: Test meridian flip behaviour with scheduler running, capturing without scheduler and with an idle mount.

Diff Detail

Repository
R321 KStars
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
wreissenberger created this revision.May 5 2019, 2:25 PM
Restricted Application added a project: KDE Edu. · View Herald TranscriptMay 5 2019, 2:25 PM
Restricted Application added a subscriber: kde-edu. · View Herald Transcript
wreissenberger requested review of this revision.May 5 2019, 2:25 PM
mutlaqja accepted this revision.May 5 2019, 3:54 PM
This revision is now accepted and ready to land.May 5 2019, 3:54 PM
This revision was automatically updated to reflect the committed changes.