Welcome, Guest
Username: Password: Remember me
25 Jul 2018
Glad to announce of release of INDI Library v1.7.4 on 2018-07-25. A few drivers were added in this release as we continue to improve & stabilize existing drivers.
Read More...
  • Page:
  • 1
  • 2

TOPIC: Scheduler - Unexpected behavior since 2.9.7 update

Re:Scheduler - Unexpected behavior since 2.9.7 update 2 weeks 1 day ago #28138

Wow this is interesting. Your capture "EasternVeil_Light_Halpha_240_secs" appears erratically in the log (started 22:16, then 22:30, 23:06, 23:15, 23:19, 00:28, 00:30, 01:57), and always states "1 out of 30 is complete", just after execution is prepared... Sounds not good at all, I'll have a look. I hope it's not D14357...

I assume you got no captures out of this schedule? Could you provide .esl and .esq as well?

-Eric
The following user(s) said Thank You: El Corazon

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

Re:Scheduler - Unexpected behavior since 2.9.7 update 2 weeks 1 day ago #28140

  • El Corazon
  • El Corazon's Avatar Topic Author
  • Offline
  • Expert Boarder
  • Expert Boarder
  • Posts: 146
  • Karma: 1
  • Thank you received: 28
I feared that you would ask for those.... I had turned off the mini-PC controlling the rig before downloading these files, just saved the log.
I will have to wait until tonight before I get to these files. But as I wrote, the .esq file I had used before under 2.9.6 and it had worked fine, moving through the sequence from Ha to Oiii to Sii, etc. It only stopped doing this last night after I had updated to 2.9.7

Actually, I got good frames out of this session. No problem with the exposures, they look fine, I just got more frames than I wanted and only of one kind, the first one in the capture schedule (Ha and later, after manually deleting Ha from the imaging .esq file, Oiii). From the way it works at the moment, there is probably only one target and one filter I can get from the schedule.

I'll upload the .esq and .esl file tonight, but please note that both have changed since the initial problems started. I had to manually edit them to continue to get the frames I wanted and I needed the scheduler to align the scope to the coordinates in the FITS files I had already collected so that I can stack the frames afterwards. Thus, neither the .esq nor the .esl files will reflect what they were when the Ha frames were collected.

Aside from that, I like what you have done to the scheduler, Eric! The refocusing upon filter change is great, and the fact that ASAP now works as it is supposed to is also great.

Best

Jo

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

Re:Scheduler - Unexpected behavior since 2.9.7 update 2 weeks 1 day ago #28141

Thanks, more fixes to come!

No issue for the seq/capture files, I'm not in a position to study that log right now. Could you also check the verbosity of the capture and scheduler modules? They don't tell much in the log, and what they tell seems unrelated to what you have in the end. I don't know if you process your guiding values afterwards, but this part is very verbose on the opposite, and could be muted a bit.

-Eric

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

Re:Scheduler - Unexpected behavior since 2.9.7 update 2 weeks 1 day ago #28145

  • El Corazon
  • El Corazon's Avatar Topic Author
  • Offline
  • Expert Boarder
  • Expert Boarder
  • Posts: 146
  • Karma: 1
  • Thank you received: 28
I'll need to look into the capture and scheduler verbosity. I am not sure where to find those, though, do they appear in real time at the bottom of the modules? If so, those seem to reset after I quit Ekos, is there a way to retrieve them and if so, where would they be stored, if not in the log folder?
I have never processed my guiding values, actually not sure what that would accomplish. If the stars are small and round, I consider the guiding was good and that's about the extent of processing I expend on it.

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

Re:Scheduler - Unexpected behavior since 2.9.7 update 2 weeks 1 day ago #28147

The Logs button is on the second button group on the first Ekos tab. There you can select the verbosity, and the modules you want logs for. If you don't use the guide information, you can disable the log output there.

-Eric

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

Re:Scheduler - Unexpected behavior since 2.9.7 update 2 weeks 1 day ago #28149

  • El Corazon
  • El Corazon's Avatar Topic Author
  • Offline
  • Expert Boarder
  • Expert Boarder
  • Posts: 146
  • Karma: 1
  • Thank you received: 28
Yes, I know that and as far as I remember, I have all the important ones selected, but I don't know where these logs are saved. Apparently not in the logs folder. I see them displayed at the bottom of the respective modules, at least I think that;s where they go, but I don't know where they are being saved. If they are being saved anywhere.

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

Re:Scheduler - Unexpected behavior since 2.9.7 update 2 weeks 1 day ago #28153

Everything is saved in the KStars log file once you select it.

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

Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info

Re:Scheduler - Unexpected behavior since 2.9.7 update 2 weeks 1 day ago #28166

  • El Corazon
  • El Corazon's Avatar Topic Author
  • Offline
  • Expert Boarder
  • Expert Boarder
  • Posts: 146
  • Karma: 1
  • Thank you received: 28
All the documentation is now in the Dropbox folder (see my first post above).
I do not see where the verbose logs for the modules I selected are saved.
What am I missing?

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

Re:Scheduler - Unexpected behavior since 2.9.7 update 2 weeks 1 day ago #28174

  • wvreeven
  • wvreeven's Avatar
  • Away
  • Gold Boarder
  • Gold Boarder
  • Posts: 263
  • Karma: 2
  • Thank you received: 53
They should be in ~/.local/share/kstars/logs and are saved there in a sub directory named for the date at which KStars was started.

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

Modded Canon EOS 700D with a WO ZS 71 ED on a SW HEQ5-Pro /
QHY9 CCD and filter wheel with an 8" RC on a SW AZ-EQ6

Re:Scheduler - Unexpected behavior since 2.9.7 update 2 weeks 1 day ago #28179

All good in terms of log verbosity. I can see debug logs for the scheduler. I was surprised at the lack of debug logs from the capture module, but it appears to be the expected amount. Sorry for causing confusion.

I'm now looking for regressions into D14357.

-Eric

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

Re:Scheduler - Unexpected behavior since 2.9.7 update 2 weeks 1 day ago #28180

Do you have option "Remember Job Progress" set in your configuration? That may be a hint of why the count of captures is never updated.

EDIT: I'm deducing from your log that you have that option disabled, sorry for asking.

EDIT2: wrong deduction! :) seeing log "1 out of 30 is complete" means you have "Remember Job Progress" enabled as root condition.

-Eric

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

Last Edit: by TallFurryMan.

Re:Scheduler - Unexpected behavior since 2.9.7 update 2 weeks 1 day ago #28181

Workaround for this is to disable "Remember Job Progress" until a fix is pushed.

From what I understand in the log, when the Scheduler finishes guiding calibration and triggers the Capture module, the Capture module is informed that there is 1 capture for Ha in storage. Then it proceeds to capture one frame. Image arrives, sequence count is incremented. In the log, each time there is a "NFocus Elapsed Time", one frame was captured. I count 13 captures between 22:30 and 23:05.

That's where the system goes wrong is: a dithering process starts at 23:05 at the guider level. This goes on until 23:05:58 at which the sequence is resumed. Something is taking place until 23:06:15, (delay based on guidingRate()?), that causes the sequence to be prepared again. Because of this, the current capture sequence count is reset to the initial value provided by the Scheduler, and the whole sequence restarts.

This is clearly not a regression from D14357, but is probably an integration problem with the dithering process.

I believe that this can be fixed very simply by properly incrementing capturedFramesMap each time a capture arrives. This should be done at capture.cpp:1219.

Still, the other issue that bugs me is the lack of logs from the Capture module. There should obviously be more of them. Perhaps the Guide module is owning all the bandwidth, I don't know.

-Eric
The following user(s) said Thank You: knro, Herrhausen, El Corazon

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

  • Page:
  • 1
  • 2
Time to create page: 0.170 seconds

Login



3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!


Gallery

Replica

Why INDI

Replica