Scheduler completing after first job

INDI Library Clients Ekos
1

Hi,
I’m having this problem on 3.6.8 stable

I’m trying to do a mosaic 10x5 with 50% overlap

The sequence run the first job an then stop, marking everything as completed.
This the log of the run from kstars:

2024-01-16T22:18:14 Shutdown complete. 2024-01-16T22:18:14 Ekos stopped. 2024-01-16T22:18:13 INDI devices disconnected. 2024-01-16T22:18:10 No jobs left in the scheduler queue after evaluating. 2024-01-16T22:18:10 Greedy Scheduler: empty plan (0.079s) 2024-01-16T22:18:08 Job 'NSF-Part_1' is complete. 2024-01-16T22:16:04 Job 'NSF-Part_1' capture is in progress... 2024-01-16T22:16:04 Job 'NSF-Part_1' guiding is in progress. 2024-01-16T22:15:56 Starting guiding procedure for NSF-Part_1 ... 2024-01-16T22:15:55 Job 'NSF-Part_1' slew is complete. 2024-01-16T22:15:53 Job 'NSF-Part_1' is slewing to target. 2024-01-16T22:15:51 Manual startup procedure completed successfully. 2024-01-16T22:15:50 Mount already unparked. 2024-01-16T22:15:46 Greedy Scheduler plan for the next 48 hours starting mar gen 16 22:15:46 2024 (0.844)s: 2024-01-16T22:15:46 NSF-Part_1 01/16 22:15 --> 22:18 job completion 2024-01-16T22:15:46 NSF-Part_2 01/16 22:19 --> 22:22 job completion 2024-01-16T22:15:46 NSF-Part_3 01/16 22:23 --> 22:27 job completion 2024-01-16T22:15:46 NSF-Part_4 01/16 22:28 --> 22:31 job completion 2024-01-16T22:15:46 NSF-Part_5 01/16 22:32 --> 22:35 job completion 2024-01-16T22:15:46 NSF-Part_6 01/16 22:36 --> 22:39 job completion 2024-01-16T22:15:46 NSF-Part_7 01/16 22:40 --> 22:43 job completion 2024-01-16T22:15:46 NSF-Part_8 01/16 22:44 --> 22:47 job completion 2024-01-16T22:15:46 NSF-Part_9 01/16 22:48 --> 22:51 job completion 2024-01-16T22:15:46 NSF-Part_10 01/16 22:52 --> 22:55 job completion 2024-01-16T22:15:46 NSF-Part_11 01/16 22:56 --> 22:59 job completion 2024-01-16T22:15:46 NSF-Part_12 01/16 23:00 --> 23:03 job completion 2024-01-16T22:15:46 NSF-Part_13 01/16 23:04 --> 23:07 job completion 2024-01-16T22:15:46 NSF-Part_14 01/16 23:08 --> 23:11 job completion 2024-01-16T22:15:46 NSF-Part_15 01/16 23:12 --> 23:16 job completion 2024-01-16T22:15:46 NSF-Part_16 01/16 23:17 --> 23:20 job completion 2024-01-16T22:15:46 NSF-Part_17 01/16 23:21 --> 23:24 job completion 2024-01-16T22:15:46 NSF-Part_18 01/16 23:25 --> 23:28 job completion 2024-01-16T22:15:46 NSF-Part_19 01/16 23:29 --> 23:32 job completion 2024-01-16T22:15:46 NSF-Part_20 01/16 23:33 --> 23:36 job completion 2024-01-16T22:15:46 NSF-Part_21 01/16 23:37 --> 23:40 job completion 2024-01-16T22:15:46 NSF-Part_22 01/16 23:41 --> 23:44 job completion 2024-01-16T22:15:46 NSF-Part_23 01/16 23:45 --> 23:48 job completion 2024-01-16T22:15:46 NSF-Part_24 01/16 23:49 --> 23:52 job completion 2024-01-16T22:15:46 NSF-Part_25 01/16 23:53 --> 23:56 job completion 2024-01-16T22:15:46 NSF-Part_26 01/16 23:57 --> 00:00 job completion 2024-01-16T22:15:46 NSF-Part_27 01/17 00:01 --> 00:05 job completion 2024-01-16T22:15:46 NSF-Part_28 01/17 00:06 --> 00:09 job completion 2024-01-16T22:15:46 NSF-Part_29 01/17 00:10 --> 00:13 job completion 2024-01-16T22:15:46 NSF-Part_30 01/17 00:14 --> 00:17 job completion 2024-01-16T22:15:46 NSF-Part_31 01/17 00:18 --> 00:21 job completion 2024-01-16T22:15:46 NSF-Part_32 01/17 00:22 --> 00:25 job completion 2024-01-16T22:15:46 NSF-Part_33 01/17 00:26 --> 00:29 job completion 2024-01-16T22:15:46 NSF-Part_34 01/17 00:30 --> 00:33 job completion 2024-01-16T22:15:46 NSF-Part_35 01/17 00:34 --> 00:37 job completion 2024-01-16T22:15:46 NSF-Part_36 01/17 00:38 --> 00:41 job completion 2024-01-16T22:15:46 NSF-Part_37 01/17 00:42 --> 00:45 job completion 2024-01-16T22:15:46 NSF-Part_38 01/17 00:46 --> 00:49 job completion 2024-01-16T22:15:46 NSF-Part_39 01/17 00:50 --> 00:54 job completion 2024-01-16T22:15:46 NSF-Part_40 01/17 00:55 --> 00:58 job completion 2024-01-16T22:15:46 NSF-Part_41 01/17 00:59 --> 01:02 job completion 2024-01-16T22:15:46 NSF-Part_42 01/17 01:03 --> 01:06 job completion 2024-01-16T22:15:46 NSF-Part_43 01/17 01:07 --> 01:10 job completion 2024-01-16T22:15:46 NSF-Part_44 01/17 01:11 --> 01:14 job completion 2024-01-16T22:15:46 NSF-Part_45 01/17 01:15 --> 01:18 job completion 2024-01-16T22:15:46 NSF-Part_46 01/17 01:19 --> 01:22 job completion 2024-01-16T22:15:46 NSF-Part_47 01/17 01:23 --> 01:26 job completion 2024-01-16T22:15:46 NSF-Part_48 01/17 01:27 --> 01:30 job completion 2024-01-16T22:15:46 NSF-Part_49 01/17 01:31 --> 01:34 job completion 2024-01-16T22:15:46 NSF-Part_50 01/17 01:35 --> 01:38 job completion

2

Edoardo,

Please send your .esq (capture sequence) and .esl (scheduler) files, as well as your full log file, and I’ll try and reproduce.
Also, if you can find your settings, I can see which settings you used (on linux ~/.config/kstarsrc).

Hy

1 Like
3

Hy,
Thank you for the response.
Will give you those files in a couple of hours.
Where can I find the full log?

Regards,
Edoardo

4

On linux it’s inside this directory: ~/.local/share/kstars/logs
Of course, there’s enabling logs etc you can find the menus on the top row of the leftmost ekos tab (a button called “Logs”).
You should (next time if you didn’t this time) set it to Verbose, File, and enable all the checkboxes in the Ekos section.
However, I can hopefully reproduce it with the .esl, esq and kstarsrc files.
Hy

1 Like
5

Hy,
sorry for the late response, had a rough working day.

I’ve attached the zip with files.

I was trying to make some night sky flat to check why my flats are not working.

P.S.: I’m also having problem dithering using PHD2, I’ve set 30 pixel in the guiding configuration but the images looks like no dither is done

NSF.ZIP (47.5 KB)

6

I tried reproducing but had other issues (no idea why simulator kept crashing) but I do have an idea of why you were having issues.

I can see that the naming format you chose was this:

/calibration/GAIN_121./OFFSET_5./CCD-TEMP_-20/FLAT-DATE_20240114-NSF/FILTER_Idas-LPS-D3/FRAME_%T/%T_%e

Nowhere are you using the target name (which is %t) so all of your jobs would write the same filename for their first image.
Therefore, when the 2nd job starts up, it will notice that that it’s file has already been written (by the first job) and assume its work is done.
If you add %t in the filename or directory structure somewhere, then they should have unique names and all should work.
Alternatively, you can uncheck Remember Job Progress in the main KStars settings menu, under Ekos → Scheduler.

Hy

1 Like
7

With respect to dithering, dither works within a job.
It doesn’t dither across jobs.
So, if you configure things as you have, with 50 different jobs, then you won’t dither.
I don’t really understand why you have configured things to have one 120s exposure for each of 50 jobs,
but it seems like you wouldn’t need dithering if you only have one exposure per tile.

Hy

1 Like
8

Thank you so much for catching that. I will try again next to add the timestamp to the names!

[quote=“Hy Murveit”]With respect to dithering, dither works within a job.
It doesn’t dither across jobs.
So, if you configure things as you have, with 50 different jobs, then you won’t dither.
I don’t really understand why you have configured things to have one 120s exposure for each of 50 jobs,
but it seems like you wouldn’t need dithering if you only have one exposure per tile.

Hy[/quote]

Sorry, regarding dithering I was referring about a single job, took 50 photos with a single one without dithering.

But next clear sky I will try again since I think the problem lies in having started PHD2 guiding outside of ekos (but it was configured to use it).

I have this doubt because it’s not the first time it happend and the last time I don’t remember fiddling with PHD2. I will keep you posted!

9

No, not the timestamp. That will not help you. %t is the target name, e.g. NSF-Part_10 in your example.
The target name is what you need.
The timestamps are ignored when the scheduler looks to see if the job has already been captured.

BTW, I am not familiar with using PHD2 with Ekos, but others here can help you with that.

Hy

1 Like
10

Sorry, my bad, I was stupid to read “target” and think “timestamp”

For the dithering, before rising another non-existant problem I will try to debug it a little more and report back.

Thank you for your support!