Date & Time 

  10:00 PDT

Location

Browser

Room System

Phone Dial-in

https://bluejeans.com/103664856

  1. Dial: 199.48.152.152 or bjn.vc
  2. Enter Meeting ID: 103664856 -or- use the pairing code

Dial-in numbers:

  • +1 408 740 7256
  • +1 888 240 2560 (US Toll Free)
  • +1 408 317 9253 (Alternate Number)

Meeting ID: 103664856

Attendees

Regrets

Discussion items

ItemWhoNotesConclusions and Action Items
Project Science Updates
  • Dave Monet has started working for LSST at the 20% level. His time will be shared with DM and Commissioning validation work. He will focus on the astrometry. He is currently still on-boarding and will start by looking at the HSC reprocessed data.
  • Algorithms workshop is now at SLAC 3 – 5 December 2019 
  • If you are interested in attending a meeting at DM's expense, please be sure to express your interest in advance on the DM Conferences and Workshops pages  
  • The DM Conferences and Workshops pages has been considered advisory in the past, the statement now is that no TR will be accepted unless it has been previously announced on this page. Wil is finding it difficult to coordinate/approve TRs  without knowing everyone who is interested. 
  • Suggestion that we add a column to this table to indicate by when a decision is needed. In the past, people have not received feedback sufficiently in advance to make (cost effective) travel plans.
  • Leanne Guy Ensure a mechanism to provide timely feedback on requests to attend meetings and conferences.  
Outcomes from PCW sessions

Several SST members ran sessions at the PCW, we will review the conclusions from the breakouts and future work for the SST


Crowded Fields

  • In early 2019, the PST asked the SMWLV SC 1) what are the science cases for studying the galactic plane and 2) should the PST instruct the project to observe and process crowded fields more completely.
  • SWLV said yes and delivered supporting science cases. 
  • Jim Bosch and Robert Lupton put together a confluence page summarizing the current baseline for processing crowded fields ("best-effort"), and proposed direction forward 
  • This was presented to representatives of the SMWLV SC at the PCW last week.
  • One key difficulty has been around explaining why we cannot 'just run DAOPhot'. This is more of an integration problem with the rest of the LSST Stack, we want to build on top of our other data products,  to produce a consistent set of data products, and DAOPhot is not as automated as we need. 
  • SC reps at the PCW seemed to be understanding 
  • Historically, crowded fields processing has not been assigned the same priority as other science, it was assigned a lower priority as it was considered hard. It is probably in the top 5 hard things we need to do, but no harder than other hard things. It has now been assigned equivalent priority. 
  • Estimations of scope, person-years, have not been done.  
  • Jim Bosch will write a DMTN, 
DM-21062 - Getting issue details... STATUS , suitable for public consumption. 

DIA workshop 

  • Lots of really good discussions and questions requiring further study and investigation came out of this workshop, e.g 
    • How many images needed for a good DCR template, what is the quality metric 
    • Real/Bogus training and everything considered to be hard, e.g. shift and stack, light echos, comets, etc - what needs to be in the real/bogus training 
    • Strong engagement from the AGN community, concerns about DCR corrected template made from a year of AGN observations.
    • AGN, Variable stars, Strong Lensing - are the DIA or Direct Image products better for the science? What are the validation tests?
    • DESC want surface brightness  at location of suspected transient - is this int
    • ... and many more interesting ideas that Michael Wood-Vasey will write-up in  a summary document 
DM-21063 - Getting issue details... STATUS

Photo-z

  • Summary notes from the photo-z session
  • Melissa Graham proposed the following workflow:
    • Generating Photo-z (Beyond Year 1)
      • Community provides input on regions (spec-z surveys) to be used for training.
      • LSST generates DR photometry for a ‘pre-release’ training-set region (e.g., 10%).
      • Community trains the algorithm, builds the model.
      • LSST applies the model to full DR and estimates pz.
      • LSST & Community does science validation of the photo-z.
    • If issues with the LSST photometry are revealed, iteration would be needed.
  • Michael Wood-Vasey is uneasy with this approach,  but there should be something built by DM that is independent of the Community? It is an Ops deliverable that depends on unpaid work
  • Several updates made during and post the meeting to the linked summary notes above. 
RFC-620

Major changes are being proposed to the solar system processing and to the solar system data products in the DPDD. These have been discussed in detail with the SSSC already and are presented in 

RFC-620 - Getting issue details... STATUS

The goal of this discussion is to ensure that the SST has reviewed this proposal, provided feedback and reached a consensus before moving to LCR

  • Eric has read is and is broadly OK, with everything.

  • K-T and  Mario did a detailed arch review and the arch team are happy

  • It was developed with the SSSC so they are on board 

  • Mario has stated that some stuff is not in the RFC that he wants to understand a little more, eg. 

  • Mario wants dir of fast moving stuff from the trailed source - can you use adaptive moments now - wants this now. old time lines no longer valid

  • Collin points out that details are missing about nightly changing MPC database. Colin Slater  will follow up with Mario Juric

  • Colin Slater and add a note to the RFC that information about nightly changing database is lacking to inform the dm-ccb   

Deadline for comments from SST people on RFC is COB . 

Addressing old SST tickets
(if time permits) 

DM-13098 - Getting issue details... STATUS

DM-14790 - Getting issue details... STATUS

DM-16716 - Getting issue details... STATUS

DM-16553 - Getting issue details... STATUS

Deferred
AOB
  • No meeting next week due to the JSR or following week due to holiday
  • Next meeting Monday 9 September 2019 , 11:00 PDT


List of SST tasks (Confluence)

DescriptionDue dateAssigneeTask appears on
  • Robert Lupton Clarify the meaning of time in the object table. 1 sentence description in sdm_schemas, can link to a short DMTN.  Update 2022-02-09: Meeting to resolve this on 2022-02-21  
28 Feb 2022Robert Lupton2018-11-05 DM SST F2F Agenda and Meeting notes
  • Gregory Dubois-Felsmann check if SDM standardization is adequately represented in project documents, and whether DMTN-067 should be required.
31 Mar 2022Gregory Dubois-Felsmann2022-02-14 DM-SST Virtual F2F Agenda and Meeting notes
28 Feb 2023Leanne Guy2023-01-23 DM-SST Agenda and Meeting Notes
  • Leanne Guy talk to Steve R about presenting plans for the ShearObject table to PST and SciCollab chairs   
20 Mar 2023Leanne Guy2023-02-27 DM-SST Agenda and Meeting Notes
31 Mar 2023Jim Bosch2023-02-27 DM-SST Agenda and Meeting Notes
  • Leanne Guy  talk to Gregory Dubois-Felsmann to review the original intent of the AFS-related Portal requirements before deciding on a course of action  
29 May 2023Leanne Guy2023-05-01 DM-SST Focus Meeting - Brokers in Commissioning
  • Leanne Guy Prepare to consult the PST on the question of providing compressed PVIs for AP outputs, to cover the period before the data become available in a DR.  
02 Jun 2023Leanne Guy2023-03-27 DM-SST Agenda and Meeting Notes
  • Jim Bosch Incorporate 30-60 day period for raws on disk into the strawman proposal and present to KT  
26 Jun 2023Jim Bosch2023-05-08 DM-SST Agenda and Meeting Notes
  • Parker Fagrelius Patrick Ingraham  how long will it take to do a scan as described? No need to scan the whole WL range but will require additional points outside nominal lambda range.  
30 Jun 2023Parker Fagrelius2023-03-27 DM-SST Agenda and Meeting Notes
31 Jul 2023Colin Slater2023-07-10 DM-SST Agenda and Meeting Notes
  • Eli Rykoff , Leanne Guy  Develop a proposal for what calibration processing, hardware, data we actually need and what will be needed for DR1. This has implications for the ORR and for prioritisation of work in commissioning  
31 Jul 2023Eli Rykoff2023-01-30 DM-SST Agenda and Meeting Notes
  • Yusra AlSayyad will look to see if there is any effort to help on option 1  
28 Aug 2023Yusra AlSayyad2023-08-14 DM-SST Agenda and Meeting Notes
  • Jim Bosch  Provide a physical example of that a  up on cell table would look like fo the Colin Slater / DAX team to review  
31 Aug 2023Jim Bosch2023-02-27 DM-SST Agenda and Meeting Notes
30 Nov 2023Gregory Dubois-Felsmann2023-10-23 DM-SST vF2F Agenda and Meeting Notes
30 Nov 2023Leanne Guy2023-10-23 DM-SST vF2F Agenda and Meeting Notes
  •  "What is the pathway to defining the data products that are required to meet DMS-REQ-0266" Jeffrey Carlin   
30 Nov 2023Jeffrey Carlin2023-10-23 DM-SST vF2F Agenda and Meeting Notes
  • Jeffrey Carlin follow up with KT on DMS-REQ-0176 and DMS-REQ-0315 to update/disaggregate this for latest base/summit infrastructure split.  
30 Nov 2023Jeffrey Carlin2023-10-23 DM-SST vF2F Agenda and Meeting Notes
  • Jim Bosch Follow up on the possibility of investigating further the ability to process 2 collections in parallel.   
31 Jan 2024Jim Bosch2023-12-04 DM-SST Agenda and Meeting Notes
31 Jan 2024Jeffrey Carlin2023-12-04 DM-SST Agenda and Meeting Notes
Gregory Dubois-Felsmann2023-10-23 DM-SST vF2F Agenda and Meeting Notes