Hi Wolfgang, thank you for your efforts in sorting this situation out.
The 3.6.8 release indeed addressed some of the issues I experienced with 3.6.7 and reported here, most notably the gain and offset values are now used correctly even when "--" is not overridden in the text fields.
However, the frame counting problems continue. although not entirely in the same manner. First of all, the Scheduler now counts the frames correctly, but not all of them.
- It may be expected, but it is not counting images stored on the remote computer which is running the INDI server, so only "Save locally" works.
- A more serious problem is that when I had both light and flat frames in the same sequence, the Scheduler counted lights correctly but did not count flats at all. The progress number of acquired frames would just stop increasing after the lights were done, even though the Capture module was continuing to shoot flats.
But here is the most problematic scenario, which, similar to my previous report
here
, has do to with the interaction between the Scheduler and the Capture module.
This is the sequence file I started with, you will see the file naming pattern for all 3 tasks was the same:
<PlaceholderFormat>/%T/%F/%T_%F_%Es_Readmode_2_Gain_%G_Offset_%O_Temp_%C</PlaceholderFormat>
I see the Type, Filter, Exposure and Temperature defined for each task, but Gain and Offset are not. And while they are applied correctly to the file names, I wonder if their missing from task definitions is what causes the Capture module to not see the files when the Scheduler reloads the sequence upon guiding failure. So,
- Start a Scheduler job with the sequence file provided here
- While guiding is fine, both Scheduler and Capture show correct capture counts
- When guiding fails (star lost), the Scheduler restarts it and also does something that makes the Capture module reset its capture counts to 0. It very well could be just reloading the sequence file, using which the Capture module fails to count the files on the disk because of missing explicit Gain and Offset definitions. Possibly expected, but wanted to also note that the Setup tab is following the Capture module and showing its incorrect counts.
- I had to adjust the sequence file to subtract target capture counts and restart the Scheduler with the updated sequences.
After a few iterations (my guide camera is really outdated), I was down to just one task in the Capture module, and when this scenario happened again, I decided to see if the correct capture counts in Scheduler will help it stop the job. They did not: even after scheduler was showing 100% of captures done, the job did not stop and continued shooting (I suspect because it waits for completion of the Capture module, which in this case has incorrect counts).
Importantly, in my Capture settings, "Always reset sequence when starting" is not checked, and in Scheduler "Remember job progress" is.
The full log is quite large, so I will attached its version stripped from mount and camera output. Searching for "sees" shows that the Scheduler indeed "saw" correct number of captures, but I do not see anything indicative of a problem in the Capture module, although its logging was switched on.