search

NCAR / ucomp-pipeline

Data processing pipeline for UCoMP
Other
6 stars 3 forks source link

NUMSUM may vary across extensions #25

Closed bberkeyU closed 1 year ago

bberkeyU commented 2 years ago

While recipes typically have 1 NUMSUM for all extensions we should not assume that is the case.

In ucomp_l1_average_data.pro line 100 we divide the data by file.numsum which seems to be the NUMSUM form the first extension in a FITS file. This will normally be the correct answer, but the real-time code does not guarantee this to be the case. I recommend using the NUMSUM from the extended fits header to correct an individual extension.

bberkeyU commented 2 years ago

I believe we currently apply the individual extension numsum to the flats and darks but apply the file.numsum (first extension) to the science data.

mgalloy commented 2 years ago

51aa0adee1fd3c04deb11ec9da102f56c8e77745 removes normalization from dark/flat creation since it now in all reading of UCoMP data.