[OBSPROC-33] Review the pfsDesign generation script in 2022Nov run and plan for 2022Dec run Created: 30/Nov/22  Updated: 26/Dec/22  Resolved: 26/Dec/22

Status: Done
Project: PFS observation processing/procedure
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: Kiyoto Yabe Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to PIPE2D-1110 Make match filterName between pfsConf... Done

 Description   
  • 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
      • 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).
    • gaiaDB

 Comments   
Comment by Kiyoto Yabe [ 26/Dec/22 ]

Changes made during Dec. run have been merged, so I close this ticket and file another one for the next run.

Generated at Sat Feb 10 16:44:34 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.