Done
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
John Parejko
John ParejkoReporter
Russell Owen
Russell OwenPlanned End
Aug 10, 2018, 11:30 AM
Location (migrated)
here
Components
Checklist
Checklist
Created August 8, 2018 at 4:44 PM
Updated March 6, 2024 at 6:15 PM
Resolved September 24, 2018 at 5:28 PM
RFC-322 has us renaming flux fields in tables, e.g. *Flux_flux to *Flux_instFlux for fluxes in counts, and then adding *Flux_flux to mean physical flux (e.g. in Jy).
However, source tables also have getters and setters for instrument flux, such as
getPsfFlux
. At present (before implementing RFC-322) there is an obvious mapping between field names in source tables and the accessor names, e.g.getPsfFlux
returns fieldpsfFlux_flux
. If we implement RFC-322 without also renaming the getters and setters then that linkage is broken. For examplegetPsfFlux
will return data frompsfFlux_instFlux
instead ofpsfFlux_flux
. I fear users will find that confusing and upsetting.Thus I propose that as we implement RFC-322 we also rename the getters and setters:
get/set*Flux
becomesget/set*InstFlux
, for examplegetPsfFlux
becomes.getPsfInstFlux
.I further propose that we do not add getters and setters for physical flux. By not defining them we reduce the danger that old code will read the wrong thing from source tables:
getPsfFlux
will simply not exist, instead of returning the wrong thing. (We may decide to add them later, if we really miss them, but that decision is out of scope for this RFC.)I have taken the liberty of adding as watchers those who weighed in on RFC-322