×

INDI Library v1.9.9 Released (30 Nov 2022)

Bi-monthly INDI Library released with new drivers and bug fixes.

Scheduler won't capture same object twice (on 2 consecutive days)

  • Posts: 279
  • Thank you received: 54
I had my first formal run with the scheduler yesterday, on M 45 and everything went beyond expectations except for some images that were not to my liking (nothing related to KStars and friends).

I wanted to run the scheduler again today on M 45 with a different sequence that I created in the capture module (same exposure, same filters but fewer captures) but when I started the scheduler, I was greeted with the following message: "No jobs left in the scheduler queue." and the Start Time and End Time were blank as was Est. Duration. What I had to do to make it work is use the NGC number for M 45 and things worked.

I am surprised that I could not run the scheduler with the same object name/number more than once so I assume that there is a way to do that but 'how' is what I don't know. Any enlightenment will be appreciated.

TIA and Clear Skies
2 months 4 days ago #86923

Please Log in or Create an account to join the conversation.

This happens because scheduler is designed to *resume* jobs until all required captures are finished. One simple solution is to change where the images are stored in the sequence, or move the existing images to a different directory.
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
The following user(s) said Thank You: Gilles Gagnon
2 months 4 days ago #86927

Please Log in or Create an account to join the conversation.

  • Posts: 870
  • Thank you received: 83
Hi
The easiest way to implement Jasem's suggestion is to call the jobs:
M45-1
M45-2
This will create a separate folder for each job.
etc.
Cheers and HTH
Steve
kubuntu 22.04
700d, eq6, 120mm. Yes, the old one.
The following user(s) said Thank You: Gilles Gagnon
Last edit: 2 months 3 days ago by alacant.
2 months 4 days ago #86930

Please Log in or Create an account to join the conversation.

  • Posts: 279
  • Thank you received: 54
I am quite sure that all jobs were finished as all my scheduled captures had been captured and saved to disk and the observatory had shutdown.

The first sequence called for 20 captures of 180 seconds for each of the LRGB filters and, as I wanted to add captures to correct for bad images, I created a second sequence consisting of 10 captures of 180 seconds, again for the LRGB filters, under a different name. I thought that the second time being different, except for the target, the scheduler would execute the job but, as mentioned in the first post, it did not.

Is there a scheduler log or status file (haven't checked yet) I can check somewhere that would tell me the status of jobs? That would hopefully provide me the reason why things did not go as planned.

Thanks again for all help.
2 months 4 days ago #86946

Please Log in or Create an account to join the conversation.

  • Posts: 918
  • Thank you received: 431
Assuming you're running Ekos on the same machine as the files are being stored, I'd guess you're running into the scheduler option "remember job progress"



You could turn that off, though it is useful when jobs are started and suspended and resumed. You could also do what Jasem suggested and move your fits files after the first job is done.

If you want to look into debugging things...

If you run with debug logging for the scheduler, your logs will contain lines like this:
[2022-09-28T19:46:26.073 PDT DEBG ][ org.kde.kstars.ekos.scheduler] -   "/home/pi/mydisk/m77/Light/Red/NGC_7320_Light_Red_240_secs" : 3
[2022-09-28T19:46:26.075 PDT DEBG ][ org.kde.kstars.ekos.scheduler] - Frame map summary:
[2022-09-28T19:46:26.075 PDT DEBG ][ org.kde.kstars.ekos.scheduler] -   "/home/pi/mydisk/NGC_7320/Light/Blue/NGC_7320_Light_Blue_240_secs" : 40
[2022-09-28T19:46:26.075 PDT DEBG ][ org.kde.kstars.ekos.scheduler] -   "/home/pi/mydisk/NGC_7320/Light/Green/NGC_7320_Light_Green_240_secs" : 40
[2022-09-28T19:46:26.075 PDT DEBG ][ org.kde.kstars.ekos.scheduler] -   "/home/pi/mydisk/NGC_7320/Light/LPR/NGC_7320_Light_LPR_120_secs" : 286
[2022-09-28T19:46:26.075 PDT DEBG ][ org.kde.kstars.ekos.scheduler] -   "/home/pi/mydisk/NGC_7320/Light/Red/NGC_7320_Light_Red_240_secs" : 40
[2022-09-28T19:46:26.075 PDT DEBG ][ org.kde.kstars.ekos.scheduler] -   "/home/pi/mydisk/m77/Light/Blue/NGC_7320_Light_Blue_240_secs" : 0
[2022-09-28T19:46:26.075 PDT DEBG ][ org.kde.kstars.ekos.scheduler] -   "/home/pi/mydisk/m77/Light/Green/NGC_7320_Light_Green_240_secs" : 0
[2022-09-28T19:46:26.075 PDT DEBG ][ org.kde.kstars.ekos.scheduler] -   "/home/pi/mydisk/m77/Light/LPR/NGC_7320_Light_LPR_120_secs" : 43
[2022-09-28T19:46:26.075 PDT DEBG ][ org.kde.kstars.ekos.scheduler] -   "/home/pi/mydisk/m77/Light/Red/NGC_7320_Light_Red_240_secs" : 3
[2022-09-28T19:46:26.076 PDT INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'NGC 7320' 15x120\" LPR completed its sequence of 0 light frames."
[2022-09-28T19:46:26.076 PDT INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'NGC 7320' 8x240\" Red completed its sequence of 0 light frames."
[2022-09-28T19:46:26.076 PDT INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'NGC 7320' 8x240\" Green completed its sequence of 0 light frames."
[2022-09-28T19:46:26.076 PDT INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'NGC 7320' 8x240\" Blue completed its sequence of 0 light frames."
[2022-09-28T19:46:26.076 PDT INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'NGC 7320' 35x120\" LPR completed its sequence of 0 light frames."
[2022-09-28T19:46:26.076 PDT DEBG ][ org.kde.kstars.ekos.scheduler] - "Job 'NGC 7320' is configured to loop until Scheduler is stopped manually, has undefined imaging time."
[2022-09-28T19:46:26.077 PDT INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'm77' 15x120\" LPR completed its sequence of 0 light frames."
[2022-09-28T19:46:26.077 PDT INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'm77' 8x240\" Red completed its sequence of 0 light frames."
[2022-09-28T19:46:26.077 PDT INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'm77' 8x240\" Green completed its sequence of 0 light frames."
[2022-09-28T19:46:26.077 PDT INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'm77' 8x240\" Blue completed its sequence of 0 light frames."
[2022-09-28T19:46:26.077 PDT INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'm77' 35x120\" LPR completed its sequence of 0 light frames."
[2022-09-28T19:46:26.077 PDT DEBG ][ org.kde.kstars.ekos.scheduler] - "Job 'm77' is configured to loop until Scheduler is stopped manually, has undefined imaging time."

(Obviously those lines that says "completed its sequence of 0 light frames" is a buggy log line, I'll look into that).

In the above, you can see how it figures out how many captures are completed, e.g. by notiding there were 40 files that started with
"/home/pi/mydisk/NGC_7320/Light/Blue/NGC_7320_Light_Blue_240_secs"
so the key thing is the filename pattern being used.
AP1100 & Orion Atlas Pro, WO/ZS105 w/Moonlight V2 focus, GSO RC10 w/RSF focus
ZWO ASI1600, Astronomik Filters, ST80, QHY 5L-IIm.
KStars/Ekos/Indi on NUC10 & RPi4 w/SSD -- Ubuntu
Projects: Greedy Scheduler, Terrain, Polar Align, Analyze, Linear Focuser, SEP MultiStar & GPG Guide, FITS autostretch.
The following user(s) said Thank You: Gilles Gagnon
2 months 3 days ago #86952
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 279
  • Thank you received: 54
Thanks for reminding me to check the KStars/EKOS options as I tend to forget about them.

Next time I run the scheduler, I will try to generate a log file so I can track what's going on and understand the issue. Unfortunately, not before a few days as clouds are rolling in :( .

Thanks again.
2 months 3 days ago #86954

Please Log in or Create an account to join the conversation.

Time to create page: 0.302 seconds