×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Scheduler still capturing after job completion

  • Posts: 249
  • Thank you received: 62
1) I disabled "Remember Job Progress" only and run a test. Scheduler completed the job, briefly shown 'no jobs running' then turned the status to 'capturing' again.
2)Then kept 'remember Job progress' disabled and added a (simulator) filter wheel. Run a test capturing 10s per each filter (R,G,B ).
Still a new job was selected after completion.

Attached a screenshot of the scheduler during first test .
2018-09-20T14:39:23 Job 'Polaris' is selected for next observation with priority #10 and score 40.
2018-09-20T14:39:23 Job 'Polaris' target is 109.438 degrees from Moon (score +20).
2018-09-20T14:39:23 Job 'Polaris' target altitude is 46 degrees at 20/09/18 14:39 (score +20).
2018-09-20T14:39:23 Job 'Polaris' will be run at 20/09/18 14:38.
2018-09-20T14:39:23 Job 'Polaris' target is 109.438 degrees from Moon (score +20).
2018-09-20T14:39:23 Job 'Polaris' target altitude is 46 degrees at 20/09/18 14:39 (score +20).
2018-09-20T14:39:23 Astronomical twilight rise is at 05:12:00, set is at 21:00:00, and current time is 14:39:23
2018-09-20T14:39:22 Job 'Polaris' is complete.
2018-09-20T14:38:48 Job 'Polaris' capture is in progress...
2018-09-20T14:38:48 Job 'Polaris' slew is complete.
2018-09-20T14:38:47 Job 'Polaris' is slewing to target.
2018-09-20T14:38:44 Mount already unparked.
2018-09-20T14:38:43 Dome unparked.
Last edit: 5 years 6 months ago by Ferrante Enriques.
5 years 6 months ago #29666
Attachments:

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

  • Posts: 1029
  • Thank you received: 301
Hum, I did not notice the "0/0" in column "Captures", and the lack of imaging duration. That's an interesting situation, what is exactly the configuration in your sequence file? It seems the Scheduler is unable to calculate the time required to complete the job. Do you have any frame captured actually?

-Eric
Last edit: 5 years 6 months ago by Eric.
5 years 6 months ago #29668

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

  • Posts: 249
  • Thank you received: 62
yes, frames are there. And yes, the frame count in the scheduler does not increase.
I use a simple 10s x filter sequence for testing. Just keep the cooling off because during the day is still quite hot.
In the scheduler configuration please note that 'focus' is disabled during the day and 'align' and 'track' are disabled as my mount has encoders.
Attached the configuration file.

Thanks
Last edit: 5 years 6 months ago by Ferrante Enriques.
5 years 6 months ago #29670
Attachments:

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

  • Posts: 1029
  • Thank you received: 301
Would it be possible to have the full verbose log of your test? I'll check what is happening. I assumed that the job would repeat because the scheduler considered it was not finished. That behavior is controlled by Remember Job Progress, and there is a potential issue when you don't have a filter wheel in the setup that makes the capture check unable to find the frames. But there the "0/0" is puzzling, it's possible that this strange count is confusing the scheduler. At least it's not preventing you from running captures! I believe running the job until a fixed timestamp should allow you to shut your observatory down properly.

-Eric
The following user(s) said Thank You: Ferrante Enriques
5 years 6 months ago #29672

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

  • Posts: 249
  • Thank you received: 62
Run a test with all simulators devices (CCD guider, telescope, focus and filter) in a local configuration .
Kept "Renember Job Progress" not checked and used three filters.
Still the count is 0/0 and the scheduler tries to restart the job after completion.
Attached the full verbose log of this test (job completion is line 662. Line 1039 is where I manually stopped the job).

Thanks again for helping

EDIT: also run test with different 'Job Completion Conditions'.
'Repeats for 1 run' enters a loop of runs until I manually stop it.
'Repeat until <time>' repeats batches until it reaches the scheduled time and then triggers shutdown, as you said.
The following user(s) said Thank You: Eric
Last edit: 5 years 6 months ago by Ferrante Enriques.
5 years 6 months ago #29675
Attachments:

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

  • Posts: 220
  • Thank you received: 14
Same problem here, I noticed that it does not create a directory, like it did before,
but save image in Kstars/Light and remain in "capturing" ..have to stop manually.
Scheduler is very important.

Thanks.
5 years 6 months ago #29700

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

I just committed a few fixes to GIT, please check or wait for nightly and report back.
The following user(s) said Thank You: Teseo
5 years 6 months ago #29743

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

  • Posts: 220
  • Thank you received: 14
Hi knro, I see your change, compiled and tested with simulators. Now photo is saved in just directory, only work remain in "capturing".
Add log and file used as test ( test photo of polaris without align, guide, ecc.. ).

Thanks.
Last edit: 5 years 6 months ago by Teseo.
5 years 6 months ago #29746
Attachments:

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

Sorry I didn't understand "Only work remain in capturing"?
5 years 6 months ago #29751

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

  • Posts: 220
  • Thank you received: 14
Sorry, you are right, my english is horrible.

When he finishes capturing, remains in "capturing", for end have to press stop button.

Add video.
Last edit: 5 years 6 months ago by Teseo.
5 years 6 months ago #29755
Attachments:

    capture_edit.mp4

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

  • Posts: 220
  • Thank you received: 14
Would it be possible to correct the scheduler?
It is a very important part of Ekos

I expose the problem, but my English is limited.
The problem is: when it finishes capturing the photo, it does not stop (and move on to another if present).
It remains in acquisition and the photo counter always remains at 0.
5 years 6 months ago #29827

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

I plan to check it soon don't worry about it.
The following user(s) said Thank You: Teseo
5 years 6 months ago #29829

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

Time to create page: 0.314 seconds