Hmm, may need some refactoring here, the measureXX primitives are quite tied to the adcc / qametric database model. Would be better to split out the measurement and reporting functionalities. Also with GPP, the percentiles concept is depreciated, as is things like "zenith values" for IQ...
[ ] Create new reduce_archive recipe for GMOS Imaging, adding:
- addReferenceCatalog
- determineAstrometricSoltution
- measureIQ
- measureCC
- measureBG
[ ] Add astrometric pointing errors to output header in geminidr/core/primitives_register.py:determineAstrometricSolution(). Currently has the option to upload them to the fits server, but in the new world we want these added to the header, and this seems like a reasonable thing to record in the output headers anyway. Near end of primitive, but inside extension loop - add them to the extension header as there could be multiple extensions with different values.
[ ] Add IQ measurement to header in measureIQ
[ ] Add CC measurement to header in measureCC
[ ] Add BG measurement to header in measureBG
Hmm, may need some refactoring here, the measureXX primitives are quite tied to the adcc / qametric database model. Would be better to split out the measurement and reporting functionalities. Also with GPP, the percentiles concept is depreciated, as is things like "zenith values" for IQ...
[ ] Create new reduce_archive recipe for GMOS Imaging, adding:
[ ] Add astrometric pointing errors to output header in geminidr/core/primitives_register.py:determineAstrometricSolution(). Currently has the option to upload them to the fits server, but in the new world we want these added to the header, and this seems like a reasonable thing to record in the output headers anyway. Near end of primitive, but inside extension loop - add them to the extension header as there could be multiple extensions with different values.
[ ] Add IQ measurement to header in measureIQ
[ ] Add CC measurement to header in measureCC
[ ] Add BG measurement to header in measureBG