[DAMD-33] Do we need total mag as well as fiber mag? Created: 29/Jun/18 Updated: 19/Nov/20 Resolved: 19/Nov/20 |
|
| Status: | Won't Fix |
| Project: | Data Model |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Normal |
| Reporter: | Kiyoto Yabe | Assignee: | hassan |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Description |
|
In the last DRP telecon, we discussed a possibility of using photometric information for the redshift measurement in 1D-DRP. In that case, 1D-DRP refers to pfsConfig or operational database for the photometric information. Currently, "fiberMag" is allocated in pfsConfig and that may be useful to match with the spectroscopic data. On the other hands, the target selection is made using total magnitudes, so the total magnitude may be useful information. Also it may be useful to think about (for example) the aperture corrected spectroscopic data, and also any other purposes. We should keep talking about this further, but I'd like to file this ticket as a bookkeeping thing to add "totalMag" or "CModelMag" as well as "fiberMag" in pfsConfig. |
| Comments |
| Comment by rhl [ 09/Mar/19 ] |
|
I agree that we should add total (probably model) magnitudes to the pfsDesign files (which will propagate to the pfsConfig files. These magnitudes need to be available to the further processing as they are useful for e.g. constructing redshift priors. The fiber magnitudes are a bit tricky as they depend on the seeing (and the seeing is a function of wavelength), and the photometric corrections applied using calibration stars are not strictly applicable to extended sources. None the less, the HSC outputs provide fibre magnitudes at a range of seeings, and can probably be used to correct for some/much of this. |
| Comment by hassan [ 19/Nov/20 ] |
|
Implemented as part of |