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.

Read More...

Hy Murveit replied to the topic 'Latest git fails to build' in the forum. 2 days ago

It seems that make install cannot be modified to be given a single target.
The truth is you don't even need to copy/install the kstars executable anywhere,
You can just run it from wherever it is compiled without any installation.
In Jerry's script, I believe that would be by typing this on the command line:
~/Projects/kstars-build/bin/kstars
That what I tend to do.

Hy

Read More...

Hy Murveit replied to the topic 'Latest git fails to build' in the forum. 2 days ago

Got it. Try it this way and see if it works.

On line 285, instead of:
make $jobs || exit 1
try changing that to:
make $jobs kstars || exit 1
and you should bypass those errors, and make things compile much quicker too.
The way it was currently set, it compiled everything including tests and doc etc.

Jasem will hopefully get the documentation issues sorted out, but in any case, this should work and be faster.

Hope that helps,
Hy

Read More...

Hy Murveit replied to the topic 'Latest git fails to build' in the forum. 2 days ago

Sorry, don't remember the script and from your snippet, I can't tell what the $jobs variable is set to.
I'm sure we could set it up so that it doesn't compile the documentation.
Hy

Read More...

Hy Murveit replied to the topic 'Latest git fails to build' in the forum. 2 days ago

Won't it build if you run
make kstars
as opposed to
make

Hy

Read More...

Hy Murveit replied to the topic 'Platesolving offset from center' in the forum. 6 days ago

Not sure about the offset, but platesolving should work for your 6" SCT. I platesolve with a 10"RC (focal length 2000) plus a ZWO ASI1600 camera, very reliably.
Make sure (a) you are in focus, and (b) you have all the appropriate index files are installed.
You can also try ASTAP if the internal solver is not working?
Can you post an image from your SCT (with the platesolving exposure) and we can see if we can plate solve it?

Hy

Read More...

Hy Murveit replied to the topic 'Greedy scheduler and refocus' in the forum. 6 days ago

If you'd like to refocus every hour, you can use the Limits menu on the Capture tab, and make sure you save the change back to your sequence file (the file named L_1h_120s.esq in your picture). Something like the image below, but remember to edit the lines of the capture sequence and click the checkmark, then save the file, like any other change to the capture sequence.



Read More...

Hy Murveit replied to the topic 'Autofocusing the moon' in the forum. 6 days ago

I honestly am not sure what's in the gradient autodocus scheme. The Linear and Linear 1-Pass schemes depend on star detection, so won't work on images without stars.

Read More...

Hy Murveit replied to the topic 'Artificial Horizon gone bonkers' in the forum. 7 days ago

Toni,
It is fixed in the latest code.
If you want to fix things in your self-compiled code, just comment out those 4 lines as described above.
Hy

Read More...

Hy Murveit replied to the topic 'Artificial Horizon gone bonkers' in the forum. 1 week ago

Pit,

Thanks for reporting this. I looked into it and tracked down the issue to the following.
I have submitted an MR which will hopefully be merged soon.

I believe you compile from code, can you make the following change and test?
(I'd have you just use the latest code but I don't necessarily recommend you using that right now.)

In the file kstars/kstars/skycomponents/artificialhorizoncomponent.cpp
find the function called appendGreatCirclePoints (starts on line 268)
and comment out these 4 lines which are not far from the top of the function (lines 274-277)
invent.kde.org/education/kstars/-/blob/m...oncomponent.cpp#L274

    // std::shared_ptr<SkyPoint> sp0(new SkyPoint());
    // sp0->setAz(az1);
    // sp0->setAlt(alt1);
    // region->append(sp0);

It is not perfect--it makes little jagged lines near the horizon (which is what those 4 lines fix in horizon mode and were supposed to fix in equatorial mode too), but that is far better than the current rendering mess. I need some consulting to get it totally right, if you have any clue how to fix, let me know!

Hy

Read More...

Ron,
Thanks for your feedback. I sent you a PM. Let's discuss and figure out an approach to improving things.
Hy

Read More...