Use as many tests vectors as possible, in various configurations.
- simple_test tested OK
- simple_test_no_twilight tested OK
- duplicated_scheduler_jobs_no_twilight tested OK
- duplicated_scheduler_jobs_duplicated_sequence_jobs_no_twilight tested OK
- complex_job tested OK
Note there is an issue with parking/unparking when executing jobs one after the other. When the second job tries to unpark the telescope simulator, it loops on "Mount parked". This is under control, to be pushed later on.
Message "Manual scheduled focusing is not supported" is still annoying when running test vectors in sequence, to be investigated and eventually removed very soon.
Guider is doing weird things when used with the simulator. It detects offset on the guide star although the simulator always produce the same image, only noise is different from frame to frame, and this seems to cause issues with drift calculation. Or the settings of my guider page are completely off... However, the guider is able to produce a guiding deviation that exceeds the bounds acceptable for exposure, and capture suspends.
Now this is still an issue in the last differential: capture module suspends for 60 seconds waiting for the guider, guider never really asserts return to bounds, and capture module never asserts the suspend timer neither. Ooof.
To get a guiding abort with the simulator in a development VM, pause the VM for a few minutes or hours.
This will cause a large instant deviation that will abort the guiding procedure.
This currently causes the Scheduler to properly abort, but then loop indefinitely without succeeding in restarting its jobs.