So I probably nailed down where the problem was with my last post, but actually it is not the root cause of the issue. In fact, that problem might not be considered as an issue per se, except that it has side effects which cause confusion.
The option "remember job progress" is counting the number of captures relevant to the sequence being run (that is, a count of existing fits files prefixed with the right folder assembly), and uses that number to check if the job is complete or not, and how many captures it still needs.
If I add multiple identical jobs to the scheduler list, and "remember job progress" is engaged, the algorithm of the scheduler will consider all jobs immediately finished as soon as the first job is finished. This happens because all jobs are identical, therefore the same set of captures is checked to determine whether the job is completed or not.
But if you try to reproduce, it's not the case. It is due to an additional issue: the job captures are only enumerated while estimating the duration of the jobs, and only for jobs that are NOT estimated yet.
By the way, I could also observe that modifying a job (by changing the sequence file for instance) should reset the duration, but actually does not: only a new job will arrive with no estimated duration.
Therefore to reproduce the actual issue, one scenario is to create a job with a sequence, start the scheduler and run it to the end, duplicate the job into a new one, and start the scheduler again. No module will get triggered, only captures, and the wrong message about calibration will appear in the logs.
Because this is, well, a set of intertwined issues, this will be a bit more involved to fix
it's not even clear what needs fixing. Option "remember job progress" is clearly not compatible with job duplication, but having multiple sequences with realignment and focus might be interesting for prioritizing. Focus could be configured with the checkbox "refocus if HFR...", but what about alignment? That makes guiding obligatory, but it is optional nonetheless. And meridian flip? Or perhaps the way the scheduler currently works is simply too flexible for its own good.
In any case I may start by adding logs which clarify the situation for the end-user, reminding how the scheduler will address jobs. I could then fix the duration estimation, which should trigger for any change, or at least reset when the job is modified. Then probably I could add one level of folders between the scheduler output and the sequence output, say the job index (not very bright though), in order to avoid jobs mixing up when counting captures. Perhaps from there I could add a new button aside the mosaic macro, which would enable users to generate multiple jobs to capture a certain total exposure on a particular object.
Any other ideas on this?
-Eric