Data Management
Space shortcuts
Page tree
Skip to end of metadata
Go to start of metadata

(back to the list of all DMLT meeting minutes)

Location

Browser

Room System

Phone Dial-in

https://gemini.zoom.us/j/93625401560?pwd=cjdFb1ZWeGx1eVJGSVBUVmpMRUg5UT09


Meeting ID: 936 2540 1560 

password: 161803

Dial closest IP: 162.255.36.11 (east coast) and 162.255.37.11 (west coast) Then use the Zoom meeting ID 936 2540 1560 as the dialing extension. For example: 936 2540 1560@162.255.37.11 or: 162.255.37.11##936 2540 1560 Password: 161803

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

Time

10:15am PT

Attendees

Regrets

Discussion Items

ItemWhoNotes
NotesTim Jenness last time
Project Updates
  • All - hands meeting  9am PST - invite sent
  • AAS Town Hall 18:30-20:00 PST, Seattle Convention Center - Ballroom 6B  presentation staging
  • AMCR - presentation staging Seattle (anyone know the location?)
  • Group of 15 scientists requesting to visit summit on Saturday after their conference
  • Chile Holiday  
  • EPO good review only comments.
  • DM mothly report
    • should get thinner ultimately at the end should be very very short..
    • we can close WBSs - specific would be good. Put in the report and get Kevin to close it. Small cleanup can be on a generic charge number. Close out report: requirements verification.  Kevin wants no more charges to hit the account if it's done.
    • can say "Work under operations" delivered or informed on.
  • Summit - difficult to get rooms
    • Base control room seems to have stalled. Should be clone of summit to allow observing support.
DEI


See  #inclusion and https://www.lsst.org/about/dei

Community link: https://community.lsst.org/c/eji/45


Monthly
report due this week. https://docs.google.com/document/d/1DjQ62u1G4qkewLyoGckBVgcmYz1FJL8E1ukF-k91lKw/edit#heading=h.m2nv7zs59upm


At least one Epic for each ops milestone (l3)  - they are all linked up.

I think this shows Milestones with NO epic blocking it

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Refresh


Review of Project Milestones


https://www.lsst.org/about/project-status

Level 2 Milestones


See also LSST Verification & Validation Documentation and LDM-692 (VCD).

Test Plans due in the next 45 days

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh

Milestones due in the next 45 days

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh

Risk Review



Risk items needing review

Key Summary T Created Updated Due Assignee Status days since review
Refresh

Overdue risks (obligation date passed)

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Refresh

Risk mitigations due at the end of this month

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh

Overdue risk mitigations

 

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Refresh

DMLT Travel & Availability this week



Any Other Business


Discussion of what DP1 means now that ComCam is no longer going on the telescope. Pre-cursor data release should involve our pipelines generating the data and should consider what would happen if the outputs do not match the quality of existing data releases. Also need to understand that work is needed beyond what the default pipelines generate (such as HiPS) if a non-Rubin team is generating the data products. Some discussion of treating DP1 as a small set of LSSTCam data from early commissioning. Should not use Data Previews driving commissioning. LATISS is not going to be useful for a public DP. A DP of early LSSTCam data might distract from team focus on trying to improve image quality. The formal HSC PDR4 data would be acceptable for DP1 – the data have been verified, are using our pipeline, and there is scientific interest from the community.

TCAM Standup

Frossie Economou

as needed
Action review



DMLT Action Items (Confluence quick tasks)

Confluence action items on DMLT meeting minutes pages are meant to be mainly low-level actions that can be completed quickly.  More substantial tasks should appear in JIRA.  The label "DMLT" can be used (with any component) to mark a task as resulting from a DMLT action item.

DescriptionDue dateAssigneeTask appears onLabel(s)
  • Frossie Economou Will recommend additional Level 3 milestones for implementation beyond just the DAX-9 Butler provenance milestone.   
15 Mar 2022Frossie EconomouDM Leadership Team Virtual Face-to-Face Meeting, 2022-02-15 to 17meeting-notesdmltdmlt-f2f
  • Kian-Tat Lim Convene a meeting with Colin, Tim, Robert, Yusra to resolve graph generation with per-dataset quantities (likely based on Consolidated DB work).  
18 Mar 2022Kian-Tat LimDM Leadership Team Virtual Face-to-Face Meeting, 2022-02-15 to 17meeting-notesdmltdmlt-f2f
15 Nov 2022Gregory Dubois-FelsmannDMLT meeting-2022-10-24dmltmeeting
  •  Kian-Tat Lim  Convene a meeting following up vF2F discussion about what to do with Jenkins  
24 Nov 2022Kian-Tat LimDM Leadership Team Virtual Face-to-Face Meeting - 2022-10-18dmltmeeting-notesdmlt-f2f
13 Feb 2023Gregory Dubois-FelsmannDMLT meeting-2023-01-30dmltmeeting
24 Apr 2023Gregory Dubois-FelsmannDMLT meeting-2023-04-17dmltmeeting

DMLT Action Items (JIRA)

JIRA tasks with label "DMLT" but not TESTPLANS:

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh