×

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

Bi-monthly release with minor bug fixes and improvements

How to repeat jobs created by mosaic planner ?

  • Posts: 163
  • Thank you received: 26
There was no logging active during that run, however tonight it's active: verbose, file etc.
The rest of the jobs ran smoothly, by the eay, so I suspect the hiccup from before was an edge case.
We'll see soon :)
For the rest I'm really pleased by how stable everything runs now, even on the Rpi4.
7 months 3 weeks ago #95521

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

  • Posts: 163
  • Thank you received: 26
Tonight the hiccup happened again. I've enabled logging as you requested (verbose and all).

Each job has a sequence with 20 lights.
Starting conditions of the mosaic panels 1 to 4: 40, 24, 20, 20 lights respectively.
Result: 40, 41, 20, 20 lights.
What is strange: 41 lights in the second panel (starting at 24) not 40, not 44 (24+20)...

Please help me out, this is frustrating to say the least. (us Dutch people don't have the luxury of many clear nights ;) ).

Picture of the analysis tab:


Log, excerpt from the last actual light recieved (23:17:32) onward:
(I've put it in spoiler 'brackets' because then this post remains somewhat readable)
Warning: Spoiler!
Last edit: 7 months 3 weeks ago by Bart.
7 months 3 weeks ago #95538
Attachments:

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

  • Posts: 163
  • Thank you received: 26
And for good measure the content of the scheduler (.esl) file:

Warning: Spoiler!
Last edit: 7 months 3 weeks ago by Bart.
7 months 3 weeks ago #95539

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

  • Posts: 167
  • Thank you received: 23
@Bart,

Did you open/move/edit one or more FITS files during the running sequence ?

I've been struggling with the same problems as you since posting this topic some weeks ago and I'm starting to suspect that as soon as the timestamp or other file properties of the FITS file changes, the process starts acting weird.

Unfortunately we haven't had a clear night here yet to try again.
7 months 3 weeks ago #95544

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

  • Posts: 163
  • Thank you received: 26
I first imaged M31 for a few lights, just for the heck of it (and waiting for full darkness).
Then opened the schedule, ran that, checking if focus, align and guidibg went well. It did, so I went home and left it running.
Didn't explicitly open one of the fits.
Last edit: 7 months 3 weeks ago by Bart.
7 months 3 weeks ago #95547

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

  • Posts: 167
  • Thank you received: 23
Please can anyone from the developers indicate whether opening FITS files has an impact on the numbering or more specifically on the strange numbers when creating a mosaic?
7 months 3 weeks ago #95572

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

  • Posts: 167
  • Thank you received: 23
Quote Hy:

1- Set each of the 4 mosaic tile scheduler jobs to have the same non-empty group name, and set each of them to have the "Repeat until terminated" completion condition. Of course, to set that you need to double click on a job (the + above the table turns into a checkbox), make sure those two items are set properly, then click the checkbox above the scheduler queue table. It's a good idea to then save that schedule to disk so you can re-load it the next time.

Why should one double click every job? If the "Repeat until terminated" option is selected and the group name has been given in the mosaic planner, the created jobs looks fine.

What is the advantage to double click every job to have the "+" changed in a "v"?
7 months 3 weeks ago #95661

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

  • Posts: 163
  • Thank you received: 26
Essentially he wants us to make sure that each job in that schedule has 'repeat until terminated' checked.

(And yes, of course they are)

My hunch is that it has to do with some condition where the 'imager' tab wants to keep going to finish the x images in the sequencer, and at the same time, the scheduler (greedy?) wants to stop that job in order to keep the number of images of the (four) jobs roughly equally fast growing.
It happened before only with the first job, the subsequent jobs go on very well. That's likely because the 'number of required images' is equal to the number of images in those subsequent sequences. Except for the first one to start for that evening.

Cheers!
Last edit: 7 months 3 weeks ago by Bart.
7 months 3 weeks ago #95662

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

  • Posts: 167
  • Thank you received: 23
I just started a 2 x 2 mosaic of the Pelican Nebula
Each time 15 shots of 60 seconds, completely according to the instructions.



Fingers crossed !
7 months 3 weeks ago #95663
Attachments:

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

  • Posts: 167
  • Thank you received: 23
Only one night and some quick processing, so there is still work to be done.
But conceptually the mosaic and stitching was successful...

7 months 2 weeks ago #95701
Attachments:

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

  • Posts: 163
  • Thank you received: 26
That looks good!

Now I wonder if another night proceeding with this schedule / job group it would also 'just keep going'.

For me, the issue occured recently again, twice in a night.
I have the logs, but would any dev still like to help out please? :)
7 months 2 weeks ago #95722

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

  • Posts: 1224
  • Thank you received: 566
If you have 'Repeat until terminated' checked for all your tile jobs then the same schedule should continue to collect images for all tiles.

If you have verbose logs to share, please post links to them along with your description of what problem you're reporting in as much detail as possible. I've alerted Wolfgang who is more familiar with what I think you're describing.

Hy
7 months 2 weeks ago #95730

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

Time to create page: 2.156 seconds