Hi Eric and Jasem,
I found a new unexpected behavior of the scheduler. I had programmed a sequence in the imaging module to image the Eastern Veil in Ha, Oiii, Sii, LRGB (this was the only .esl instance I had programmed in the scheduler) and encountered the same problem twice last night;
After finishing the Ha sequence (30x240s), the scheduler restarted the Ha sequence instead of moving on to the Oiii sequence. I caught it around 2.45 am, stopped the scheduler, deleted the Ha portion from the imaging sequence (now Oiii was next in line) and restarted the scheduler. Then shortly before 5 am the same thing happened: The Oiii sequence was finished and the sequence was now supposed to move on to Sii, but again the Oiii sequence was restarted, although it had already completed.
This was certainly introduced during the last update to 2.9.7, because the same .esq sequence had worked fine under 2.9.6.
Can you have a look at the code? It appears to me that now instead of moving on to the next exposure set in the imaging sequence, the scheduler forces a restart of the entire sequence from the beginning and doesn't care about the fact that the Ha and Oiii sequence in this case had already completed.
Again, the log is too big to attach, you can download it here: www.dropbox.com/sh/tj5c8nudklv1dus/AACPk...1efnOj1p8Aarxqa?dl=0
Thanks for looking into this.
Jo
I found a new unexpected behavior of the scheduler. I had programmed a sequence in the imaging module to image the Eastern Veil in Ha, Oiii, Sii, LRGB (this was the only .esl instance I had programmed in the scheduler) and encountered the same problem twice last night;
After finishing the Ha sequence (30x240s), the scheduler restarted the Ha sequence instead of moving on to the Oiii sequence. I caught it around 2.45 am, stopped the scheduler, deleted the Ha portion from the imaging sequence (now Oiii was next in line) and restarted the scheduler. Then shortly before 5 am the same thing happened: The Oiii sequence was finished and the sequence was now supposed to move on to Sii, but again the Oiii sequence was restarted, although it had already completed.
This was certainly introduced during the last update to 2.9.7, because the same .esq sequence had worked fine under 2.9.6.
Can you have a look at the code? It appears to me that now instead of moving on to the next exposure set in the imaging sequence, the scheduler forces a restart of the entire sequence from the beginning and doesn't care about the fact that the Ha and Oiii sequence in this case had already completed.
Again, the log is too big to attach, you can download it here: www.dropbox.com/sh/tj5c8nudklv1dus/AACPk...1efnOj1p8Aarxqa?dl=0
Thanks for looking into this.
Jo