×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

EKOS Scheduler Culmination offset issue.

  • Posts: 41
  • Thank you received: 2
Good afternoon ,

I am a new user of INDI libraries with KSTAR/EKOS. My plateform is a Raspberry 3+ with Rasbian Buster. On Ekos, I used my own mount driver based on the LX200 GPS Protocol + SSAG Cam/ Inova NCCx /450D Canon.
INDI is configured localy on the rasp.

I am using this new configuration since a month. with succes. I succeed in programming a 20 variables stars / night through the Ekos scheduler.
The issue that I get is comming from the fact that in my home sky in Paris, I have a small windows to the sky ( 10X20°) to make those daily variables photometric measurements.
So using the scheduler with the " ASAP" or " ON" is working perfectly but I need to rework the scenario every day due to the daily sideral shift. So the best option in order to get the star always in the middle of my small windows is to use the "culmination offset" option.
Here is my question: if I am initializing a new scheduler, the function seems to work properly. When I am adding some "culmination offset" , the date is shifting for one unknown reason. It woks well when I start programming the scheduler but after some input the problem appear and it going worth. Even is the condition are OK for the next 24 h , the date is shiffting from x Days.
Do you have a idea of what I could have done wrong to be in this situation ?

I send a copy of the scheduler done today showing that the date of 03/06 is changed in 05/06 . I send also the scheduler file ( extention txt ).


Best Regards.
JC
PS: R Oph is at its minimum..
3 years 10 months ago #55024
Attachments:

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

  • Posts: 41
  • Thank you received: 2
I have done some investigation through the log file. And with a simpler exemple, it show that for "HD_133235" , the date seems caculated right for tonight, but at the end that the 8th June wich is set. With "HD_135207" , due to the 8 June shift, the same date is keep and time seems to be OK. And for the Last "XX" star, an additional 1 day shift is added even if at each tiem the 7 June is evaluated, the 9th is set at the end for an unknown reason.

So if somebody know or have an idea of this shift...what I have done wrong ...?

Best reagrds.
JC

[2020-06-07T13:21:18.686 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - "Schedule attempt #1 for 158-second job 'VAR_HD_133235' on row #1 starting at 08/06 22:47, completing at 08/06 22:49."
[2020-06-07T13:21:18.688 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - "Job 'VAR_HD_133235' altitude score is +8 at 07/06 23:21"
[2020-06-07T13:21:18.692 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - "Job 'VAR_HD_133235' Moon separation score is +20 at 07/06 23:21"
[2020-06-07T13:21:18.693 CEST INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'VAR_HD_133235' has a total score of +28 at 07/06 23:21."
[2020-06-07T13:21:18.709 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - "Job 'VAR_HD_133235' on row #1 passed all checks after 1 attempts, will proceed at 08/06 22:47 for approximately 158 seconds, marking scheduled"
[2020-06-07T13:21:18.710 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - "Schedule attempt #1 for 158-second job 'VAR_HD_135207' on row #2 starting at 08/06 22:55, completing at 08/06 22:57."
[2020-06-07T13:21:18.722 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - "Job 'VAR_HD_135207' altitude score is +5 at 07/06 23:21"
[2020-06-07T13:21:18.725 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - "Job 'VAR_HD_135207' Moon separation score is +20 at 07/06 23:21"
[2020-06-07T13:21:18.726 CEST INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'VAR_HD_135207' has a total score of +25 at 07/06 23:21."
[2020-06-07T13:21:18.745 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - "Job 'VAR_HD_135207' on row #2 passed all checks after 1 attempts, will proceed at 08/06 22:55 for approximately 158 seconds, marking scheduled"
[2020-06-07T13:21:18.756 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - "Schedule attempt #1 for 158-second job 'XX' on row #3 starting at 07/06 23:21, completing at 07/06 23:23."
[2020-06-07T13:21:18.771 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - "Job 'XX' is scheduled to start at 08/06 23:02, 300 seconds after 08/06 22:57, in compliance with previous job completion requirement."
[2020-06-07T13:21:18.772 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - "Schedule attempt #2 for 158-second job 'XX' on row #3 starting at 08/06 23:02, completing at 08/06 23:05."
[2020-06-07T13:21:18.784 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - "Job 'XX' startup 08/06 23:02 is posterior to transit 07/06 23:06, shifting by 8 hours."
[2020-06-07T13:21:18.786 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - "Job 'XX' startup 09/06 07:02 is posterior to transit 08/06 23:05, shifting by 8 hours."
[2020-06-07T13:21:18.799 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - "Job 'XX' is scheduled to start at 09/06 22:58, in compliance with culmination requirements."
[2020-06-07T13:21:18.800 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - "Schedule attempt #3 for 158-second job 'XX' on row #3 starting at 09/06 22:58, completing at 09/06 23:01."
3 years 10 months ago #55193

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

  • Posts: 41
  • Thank you received: 2
Hi,

I am still trying to understanding what wrong with this culmination offset issue ( try to update Ekos ... ) And I still get this date shifting. Is there any body that get an *.esl file with this function used . Perhaps it will help to understand what is going wrong with my configuration...

Best regards.
JC
PS: R Oph is still at its minimum...
3 years 10 months ago #55316

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

  • Posts: 41
  • Thank you received: 2
Hi every bodies , so I supppose nobodies has encountered this kind of issue. This could be relevant to Astroberry only ?

Regards.
JC
3 years 10 months ago #55835

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

Time to create page: 0.170 seconds