I sometimes add lets say 30-40 pics of 2 mins to the capture schedule and, while it is running, I want to modify that number to add a few more, or add some with different exposure, or remove a block. I believe the current implementation does not allow for changes while running, right? Is there any major showstopper that does not allow it?
Set 1 -> AZ GTi, redcat51+Canon 6D, guide: 30mm+ZWO ASI 120MM.
Set 2 -> Star Adventurer, lenses+Canon 6D
Set 3 -> NEQ6, LX90-8' OTA/MN150 + 450D peltier, guide: 50mm+QHY5.
I can understand not allowing modification of the job currently running, but I agree - would sure be nice if I could modify the params of other jobs in the queue while a job is running.
I'm not sure what the deal is for modifying the capture sequence for the currently running job. Would need to check the code to see the implications of changing the sequence of a running job.
As far as changing the sequence for upcoming jobs: as I recall, the main "show stopper" is that the only editor for the capture sequence file is the capture module itself (and it is busy when jobs are running). That is, if you tried to be tricky and text-edit the .esq file for the next job (at your own peril), then, when the next job started, it would read the new .esq file, and get your new version. I'm not recommending text-editing that file, just saying it would be possible, and that I've done it (though not for this scenario).
I agree it would be nice to be able to have an editor for .esq files that didn't require connections to indi devices or a running ekos, but that is not currently implemented.
Any volunteers?
Hy
AP1100 mount, GSO RC10 mount w/RSF focus, ZWO ASI1600 imager & guider, Astronomik Filters, ONAG.
KStars/Ekos/Indi on NUC10 with Ubuntu 22.04
Projects: Greedy Scheduler, Terrain, Polar Align, Analyze, Linear Focuser, SEP MultiStar & GPG Guide, FITS autostretch.