[Aavso-photometry] RE: DSI Pro]

[Bruce Skelly]

Hi Justin,

I reported this to Meade.  I sent them the output of the FITS verifier, along with the relevant
pages of the standard.  My contact said that he forwarded it onto engineering.  I don't think that
it would hurt if additional people were to report it.  I wish I had a trouble ticket number that I
could refer you to, but I don't.

If you ever do have problems with a FITS file, the FITS Verifier is a quick way to verify that
your file complies with the standard.  It is at ( http://fits.gsfc.nasa.gov/fits_verify.html )

Yours,

Bruce
--- Justin Pryzby <justinpryzby at users.sourceforge.net> wrote:

> > Dear Mr.Fabrizio,
> > This is Nagai.
> > 
> > I think, the DSI Pro is the good equipment.
> > And, the AutoStar makes the FITS file.
> > But, Photographing time is not included in the FITS file.
> It is there, but not written properly..
> 
> I'm looking at a file from Freddy of Netherlands, soul on IRC,
> from some months back.  It has:
> 
>   INSTRUME= 'Deep Sky Imager'    / Imager Model
>   TIME-OBS= '20:31:03'           / UTC Time
>   DATE-OBS= '01/10/2005'         / UTC Date
>   EXPTIME =                  16. / Total Exposure Time
> 
> I suspect that the reason some software might not know the date of
> exposure is because the new and recommended format for date of
> observation is in the style: 2005-12-30T23:59:58.
> 
> The exposure time is typically in seconds
> 
> The D/M/Y format is not allowed by the FITS standard [0] for files
> written after January 1, 2000.  Also, I note that the DSI software is
> using a 4 digit year where a 2 digit year is expected.
> 
> Justin
> 
> References
> 
> [0] http://archive.stsci.edu/fits/fits_standard/node40.html#SECTION00942000000000000000
> _______________________________________________
> 
> Aavso-photometry mailing list
> Aavso-photometry at mira.aavso.org
> http://www.aavso.org/mailman/listinfo/aavso-photometry
> 
>