ojf
commented
8 years ago Camera information should end up in the headers. I assume the exposure time, UT, etc. get written in by Here is the relevant code from add_headers.py for updating the image headers. Add_headers had to add all the header keywords relevant to data reduction except for the exposure time. What follows is that code:
# add_headers used to use pyfits, which is why the astropy is imported as pyfits.
import astropy.io.fits as pyfits
# we had to read in the time of the exposure from the headers, and then process it, and then write it out to the correct header keywords. Presumably you know what time it is in your code, so here is the code for writing it out. I'm happy to help w/ these time routines--which can be a bit much.
# first convert DateObs (a string) to a python struct_time, then write two header keywords
ObsTime = time.strptime(DateObs+' UTC', "%Y-%m-%dT%H:%M:%S %Z")
ImageHdr['DATE-OBS'] = (DateObs, "Time at start of exposure")
ImageHdr['UT'] = (time.strftime("%H:%M:%S",ObsTime), "UT time at start of exposure")
ImageHdr['OBSERVAT'] = ('mro', "per the IRAF observatory list")
# there are three options are imtype = 'object', imtype = 'bias', imtype = 'flat'
ImageHdr['IMAGETYP'] = imtype
# FILTER can be any string, IRAF just looks for matches, so why not write the name of the filter (since Evora knows that)
ImageHdr['FILTER'] = filter
# Finally, this is an arbitrary string that IRAF displays in ccdlist. It's optional, and I think we probably want to figure out how we'll save files onto the client's machine before worrying about asking the user for this keyword.
ImageHdr['OBJECT'] = object_name
tristan3214
jwhueh
Oliver will comment.