-
Type:
Task
-
Status: Done (View Workflow)
-
Priority:
Normal
-
Resolution: Done
-
Component/s: None
-
Labels:None
- What we noticed during the 2022Nov run and will be fixed for the next run
- general
- script
- Also, maybe we should fit the `EUPS` mechanism so that we can switch to different versions, but need to check if this is possible.
- brokenFiber and brokenCobra should be separated in fiberStatus (see
DAMD-143)
- fiber allocation
- Do we need to control the calibrators (sky and fluxstds) not to be closed to bright fibers?
- targetDB
- targets
- `target` table has columns for epoch and proper motion but pfsDesign datamodel not (see
DAMD-137). - filterNames should follow the rule of fluxCalibration:
- HSC: {g,r_old,r2,i_old,i2,z,y}_hsc
- PS1: {g,r,i,z,y}_ps1
- Gaia: {bp,rp,g}_gaia
- SDSS: {u,g,r,i,z}_sdss
- `target` table has columns for epoch and proper motion but pfsDesign datamodel not (see
- sky objects
- `cat_id` is not propagated to pfsDesign (see
OBSPROC-34) --> done - We couldn't utilized the file of mapping between tract information and target coordinates
- We should think about more on how to make sky targets in a field with diffuse feature and very high target density (such as M31).
- `cat_id` is not propagated to pfsDesign (see
- targets
- gaiaDB
- relates to
-
PIPE2D-1110 Make match filterName between pfsConfig and flux calibration
-
- Done
-