×

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

Bi-monthly release with minor bug fixes and improvements

Read More...

guiding stops: scheduler does not recover

  • Posts: 1185
  • Thank you received: 370

Replied by Wolfgang Reissenberger on topic guiding stops: scheduler does not recover

Are you sure that also in the middle of a sequence a stopped guiding is not restarted? As far as I understand the code, when guiding aborts while a capture sequence is running, it leads to an aborted sequence. In this case, the scheduler restarts it and ensures, that the guiding is running.

Could you provide a log file that shows such a case?

For the other case I already have created a solution and submitted it for review.

- Wolfgang
Last edit: 4 years 5 months ago by Wolfgang Reissenberger.
4 years 5 months ago #45270

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

  • Posts: 969
  • Thank you received: 94

Replied by alacant on topic guiding stops: scheduler does not recover

Hi Wolfgang

No, the scheduler does not attempt to restart guiding in the middle of a sequence; it does not abort and restart as you describe. My original case was in the middle of a sequence, not at the end.
Logs:
with a physical session:
drive.google.com/open?id=1yVK-Cn8tRKMmpP6xAwbY8pnigIRoyTLD
and with the simulator:
www.indilib.org/media/kunena/attachments/4679/log_17-03-30.txt
Both logs show that guiding fails to restart between two captures in mid session.

Thanks so much for your time on this,
Steve
Last edit: 4 years 5 months ago by alacant.
4 years 5 months ago #45279

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

  • Posts: 1185
  • Thank you received: 370

Replied by Wolfgang Reissenberger on topic guiding stops: scheduler does not recover

Hi Steve,
I mean at the end of a single capture sequence, not of the entire schedule sequence. As far as I understood from your log file, you have a single shot in the capture sequence and in the scheduler, you set it to "repeat for x runs".

For the guiding interrupts at the end of the capture sequence, the fix is already contained in the latest sources.

- Wolfgang
4 years 5 months ago #45288

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

  • Posts: 969
  • Thank you received: 94

Replied by alacant on topic guiding stops: scheduler does not recover

Hi Wolgang.
No. The scheduler has only one entry: a sequence of 72 capture frames of 300s. It is within this capture sequence that the guiding fails. The scheduler does not receive the abort expected and so the next frame in the sequence begins without guiding.
Thanks again,
Steve
4 years 5 months ago #45289

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

  • Posts: 1185
  • Thank you received: 370

Replied by Wolfgang Reissenberger on topic guiding stops: scheduler does not recover

Oh yes, you are right, I could reproduce it now. When I interrupt during dithering, the capture sequence is not interrupted.
The following user(s) said Thank You: alacant
4 years 5 months ago #45292

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

  • Posts: 969
  • Thank you received: 94

Replied by alacant on topic guiding stops: scheduler does not recover

OK.
Does your commit restart the guiding at any stage of the sequence or only at the end of the sequence?
The expected behaviour when guiding fails (abort and get the scheduler to restart guiding) does not work.
Thanks again.
4 years 5 months ago #45294

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

  • Posts: 1185
  • Thank you received: 370

Replied by Wolfgang Reissenberger on topic guiding stops: scheduler does not recover

OK, the good news is that there is another fix under development that addresses this situation. It was intended for another problem, but it covers this case as well.

But it isn't ready yet, so please be patient...

- Wolfgang
The following user(s) said Thank You: alacant
4 years 5 months ago #45298

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

  • Posts: 1185
  • Thank you received: 370

Replied by Wolfgang Reissenberger on topic guiding stops: scheduler does not recover

OK, now the fix is in review. If you want to test it, you can get it from the KDE Phabricator as D25105 .

Thanks for your support in fixing this issue.
- Wolfgang
4 years 5 months ago #45304

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

  • Posts: 969
  • Thank you received: 94

Replied by alacant on topic guiding stops: scheduler does not recover

Great news. Thanks.
Do I get the git sources and build the source as per the instructions at KDE? I'm currently on the stable branch . Will this update the stable installation?
TIA
Last edit: 4 years 5 months ago by alacant.
4 years 5 months ago #45305

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

  • Posts: 1185
  • Thank you received: 370

Replied by Wolfgang Reissenberger on topic guiding stops: scheduler does not recover

If you want to obtain the diff from Phabricator, you need an account at KDE Phabricator. Here is the documentation how to obtain the access.

If you have configured everything, you need to call the following inside the kstars directory
arc patch D25105
This creates a new branch and checks it out. Now you can compile KStars and test it. As long as you do not call a "make install", your installation remains untouched.

HTH
Wolfgang
4 years 5 months ago #45306

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

  • Posts: 969
  • Thank you received: 94

Replied by alacant on topic guiding stops: scheduler does not recover

Will it reach the rmaster branch where I can build the code as per the normal method?
4 years 5 months ago #45307

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

  • Posts: 1185
  • Thank you received: 370

Replied by Wolfgang Reissenberger on topic guiding stops: scheduler does not recover

Sure, typically within a few days. I'll post an update as soon as it happened.
The following user(s) said Thank You: alacant
4 years 5 months ago #45308

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

Time to create page: 0.202 seconds