Hi Steve,

I want to populate the Average Delay field using all the great data collected by CCDAP4 about the time to complete things, only I'm not sure how?

Alternatively, I think it would be great if Navigator could reach out to CCDAP4 and retrieve this information and do that calculation for me. Perhaps John could export an XML file for Navigator to use? Would only be fair, since you do that for him! :-)

Thanks,
Jonathan

Somehow I missed this post for a while, sorry. Importing this info from CCDAP4 is on the list of things to do.

For now, the easiest way to come up with the "Average Delay" for CCDNavigator is to examine a log file of CCDAP4. Be sure to use a session log that ran successfully all night and didn't have any unusual problems. Figure out the total elapsed time (in minutes) of the session from when CCDAP4 started the session (but don't count time used for taking flats, darks, etc) until the end of the session (likewise just to the end of the last light frame). It's easy in the CCDAP4 log to see these times, they're on each log entry so you just have to find the point where the system was waiting for darkness and then started to slew to the first target. That's the starting point. The ending point would be when the last light frame was saved and CCDAP4 started to park the scope). Then subtract the actual time spent imaging (eg. number of light frames times their exposure) and then divide by the number of light frames. That will be the value to put in CCDNavigator.

Thanks Steve. That's what I did. I had just assumed that John's measurements were intended to support your calculations too, so I figured there must be some plan for how to use them.

Maybe when you can import them, you'll figure that out!

Thanks,
Jonathan

Jonathan,

Would you please post a log or two from all night CCDAP4 runs that ran normally with no aborts or other unexpected behavior?

Thanks!

Hi Steve,

Here you go!

Thanks,
Jonathan

CCDAP4_logs.zip (21 KB, 15 downloads)