Hi Chris, et al,
Many thanks for your speedy response and associated information.
I can see your point of view, and indeed being able to have a high resolution time token for use in filenames can indeed be seen as a convenience for perhaps a limited number of users of SGPro. So, given your experience as an ASCOM developer and your association with SGPro, are you able to answer me this:
1 - Is the value written into the file header variable ‘DATE-OBS’ a direct transcription of the parameter ‘LastExposureStartTime’ property in the ASCOM camera driver, with or without any necessary formatting adjustments?
2 - If ‘DATE-OBS’ is not ‘LastExposureStartTime’, then why do I not see ‘LastExposureStartTime’ in the FITS headers?
3 - In the case of the SGPro ASCOM driver for QSI cameras, does the ‘LastExposureStartTime’ property facilitate millisecond resolution? If so why does it not appear in the FITS header?
4 - If the ASCOM driver does not facilitate this resolution of time, is it in your opinion a change that could be implemented, obviously by SGPRo or QSI, if requested to so, for the reasons I have already explained? I appreciate that in answering this question it in no way indicates that it will happen.
My local Astro society and associated Pros have spent considerable time and effort in establishing which proprietry applications that actually reflect time accurately dispite what’s written in headers, etc., not many if any. Until now the need for a comprehansive image capture application, like SGPro, has not proven necessary. Now however SGPro’s other capabilities are being put to great use, and hence my feature request to up the game in terms of the recording of high accuracy time.
Thanks you for your consideration, and I look forward to hearing from you again.