×

INDI Library v1.9.7 Released (29 Jul 2022)

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

Scheduler Bug: Artificial Horizon stopped the complete queue instead of moving to the next schedule

  • Posts: 78
  • Thank you received: 2
The Artificial Horizon is a nice feature, but if a Job is running into the Limit the scheduler stops the complete queue instead of the related job only :(

With this behavior the feature is quite useless, my setups where sleeping 5 hours - just because of this - instead of capturing the next Target :'(

 

 

Thanks for your help!
6 months 3 days ago #80430
Attachments:

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

  • Posts: 78
  • Thank you received: 2
So here are the recent logs:  

File Attachment:

File Name: log_07-17-18.txt
File Size:23 KB


Have checked the code github.com/KDE/kstars/blob/stable-3.5.7/...eduler/scheduler.cpp and the bug seems to be in the void Scheduler::findNextJob() ... 
It selects the previous "aborted" job :'(

 
6 months 3 days ago #80431
Attachments:

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

  • Posts: 78
  • Thank you received: 2
So i have fixed this bug with changing  github.com/KDE/kstars/blob/stable-3.5.7/.../scheduler.cpp#L3684 currentJob->setState(SchedulerJob::JOB_IDLE); to currentJob->setState(SchedulerJob::JOB_ABORTED);

With this, the Job is aborted and the next job in the queue is executed
6 months 2 days ago #80442

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

  • Posts: 25
  • Thank you received: 1
Will this fix the same issue that occurs when using the Altitude Limit?
6 months 2 days ago #80460

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

  • Posts: 78
  • Thank you received: 2
I guess so, because the artificial Horizon is implemented by the altitude limit!

CS
6 months 2 days ago #80461

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

Time to create page: 0.690 seconds