Hi Steve,

It was after midnight last night when I built a plan to image M13. When I set my target criteria, I overrode the plan start time to coincide with the availability of M13 (about 45 minutes later - 1:20). Note, my Session Date said 2/21/2009.

When the plan was built, it was built not for 1:20 on 2/21 but for 1:20 on 2/22:

Session starts on 2/22/2009 at 01:20

M13 starts at 01:20 local time

RA = 16:41:41 DEC = +36° 27' 38" PA = 0.0 degs

Red filter for 12 frames at 150 seconds binning 1x1
Green filter for 12 frames at 150 seconds binning 1x1
Blue filter for 12 frames at 150 seconds binning 1x1
Luminance filter for 37 frames at 150 seconds binning 1x1

I don't know what I'm doing that causes this and of course, it's a problem when I import it into CCDAP as it wants to wait until the next day to start. I did just reset the date over in CCDAP to get around it but I was wondering if the target start time of 1:20 was really the rise time for 2/21 or 2/22?

Thanks,
Jonathan

Hi Jonathan,

CCDNavigator plans sessions for the date selected starting at the beginning of astronomical darkness on that date. If you start it running just after midnight on 2/21, it plans a session starting at astronomical darkness on 2/21. Then (rightly) M13 would be imaged at 1:20 am on 2/22.

If you had set the date to 2/20, it would have planned M13 for 1:20 am on 2/21.

Ahhhh! Thanks for the workaround! Given my target selection criteria, you can see why I reasoned it was doing THAT day and not another date of its choosing.

Perhaps in a future version this all can be made more obvious.

Thanks,
Jonathan

It's on my list...