2022-10-31 DM-SST Agenda and Meeting Notes

Short : ls.st/dmsst 

Zoom: https://noirlab-edu.zoom.us/j/97839121776?pwd=K1JPeUpSMXFvSXJSa2xORGkyVk5zdz09

Zoom Meeting ID: 978 3912 1776 
Zoom Password: 512314

Dial closest IP: 162.255.36.11 (east coast) and 162.255.37.11 (west coast) then use the Zoom meeting ID 978 3912 1776  as the dialing extension.

For example: 978 3912 1776 @162.255.37.11 or: 162.255.37.11##978 3912 1776  Password: 512314

Dial-in numbers:

+1 346 248 7799 (US Toll)

+1 669 900 6833 (US Toll) Meeting ID: 936 2540 1560 International numbers available: https://gemini.zoom.us/u/adcUNrbXzS

• LSST@Europe last week, lots of good talks.

Focus on SIT-Com Science Units:

• their organization and deliverables in commissioning. How do we stand them up
• template for verification specification 
• Jira organization - epics, farming out of tickets
• meetings ... what will help them get started, how do we sustain momentum
• transition to going on sky - different cadence, active on-sky
• rehearsals? taking and processing  data with AuxTel, producing reports.   
• Using AuxTel to automate processes, incl. data taking, analysis and reporting  - do some rehearsals

Slides with discussion points (as-delivered PDF)

• Eric: Who is writing the test plans and executing them?
  
  • Keith: SU's role is writing down the scientific methodology, and making sure that that code has been implemented, looking at results. Small separate group handles the formal syseng aspect.
• RHL: Overlap here between verification and validation. More interested in putting effort into validation, how much of that is in scope for SU's?
  • Keith: do not want to delay start of survey due to delays in science validation. Have to prioritize things things that can't be corrected after-the-fact (i.e. image quality).
  • RHL: but does verification mean that the data-taking is good? Prioritize good-data-taking over verification.
• GPDF: Named metrics are all tied to requirements. SU provide user support in understanding those, or in formal definition?
  • SU's role is to write down that detailed description.
  • GPDF: need a pathway for formally adopting each of these detailed descriptions. Science-mgmt sign-off. Everyone is in agreement on this.
• CTS: What does Ex-Officio mean?
  • Members that aren't on-project, so need special dispensation to have commissioning data access.
• CTS: way to test the workflow of handoffs from project to SU to syseng?
  • Keith: Yes, use milestone of "first light requirements" to test this.
• Eric: "sections of construction papers", not necessarily whole construction papers.
• GPDF: Good for proposed template to have useful macros to make requirements linkable/etc. Include link to LVV verification elements.
• GPDF: in Spherex, have a "requirements closure memo" which can say that multiple tests together satisfy a particular requirement.
• Discussion about doing the documentation "bottom up" i.e. do some tests on real data and write up the results vs. writing down the process for testing in prose then performing the test on data.

Next steps: Keith will start working on slides to present to the SU leads, post to #dm-sst and iterate there.