Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

ItemWhoPre-Meeting NotesNotes and  Action Items
Project/Science Updates
  • No PST meeting last week. 
  • All full proposals for community brokers accepted. 
  • Problems with u-band filters. Don't think it is measurement errors, hard to measure on the mountain (no photons) 
Photo-z
  • brief summary re. PZ, commissioning, SITCOMTN-010 (Keith BechtolMelissa Graham will explain)
  • DESC PZ WG and DM could mutually benefit from using their RAIL software (PZ evaluation infrastructure) to help the science community participate in PZ validation during commissioning.
  • At the stage of trying to get the community to write LoRs. Deadline is end Sept. 
  • Melissa thinking about the process of validation during commissioning as open . Zero-th level is to just use the released data products.  Could do better.  Want to do better an start making more specific plans. 
  • Which commissioning data will photo-z be done with. What teams do we need to set up if we want to use unreleased commissioning data. 
  • LPG: What are the use cases for early access to commissioning data. We have previously said that pz estimators will work with Object catalog data. 
    • MLG: 1: time  - we don't want people to have to wait until comissioning data is released? and 2) pz will have a more integrated role in commissioning 
  • RHL - interested in photo-z for testing photometry. Will be useful to have a competent redshift team working early to run testing early, e.g   to test galaxy photometry. 
  • Need to develop a plan for how people will join teams  during commissioning. 
  • CS: What is a sufficient threshold for involvement in photo-z to allow people to join? Key os to define this threahold and this and consider adding people  based on meeting a threshold of involvement. 
  • CS: Work on pz does not end with the end of commissioning - follow the formal manner initially, once we start releasing public products, anyone can be involved. 
  • Intercollaboration WG with DESC pz working group or using the DESC RAIL software. ICA picks out the key pieces of work to be done for DM to use with the commissioning data so that pz codes are wrapped in the RAIL infra, write pz metrics to work with RAIL. Code will need to be added for dm to use RAIL during commissioning, which one DM/DESC does. 
  • CS: Can we get a presentation from the RAIL team to tell us about their software?
  • CS: Not a good idea for DM to convert products to their format. Needless diversion. Rather get their sq to read our parquet tables - our products are easy to read and if they are not we should change them. 
  • LPG: This ICA defines a lot of work to be done by DM - we don't have the resources for this. Also looks like scope creep w.r.t our requirements 
  • MLG: We can  maybe use the directable in-kind effort. Need to define how the in-kind contributions work and how can we work with in-kind teams
  • Get back to DESC in September. 
  •  Melissa GrahamLet DESC know that we will pick this up again in September  
  •  Melissa Graham update dmtn-049 to state that all members of the photo-z redshift teams become part of the commissioning team.  
  •  Melissa Grahamreach out to photo-z in-kind team to discuss how photo-z inkind contributions might work with RAIL.  
10 oldest DM-SST issuesLeanne Guy
  1. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-20967
  2. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-20940
  3. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-19505
  4. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-21023
  5. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-15763
  6. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-21323
  7. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-20780
  8. Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-13740


AOB

Next meeting is   


...