- 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.
See #inclusion and https://www.lsst.org/about/dei
Community link: https://community.lsst.org/c/eji/45
At least one Epic for each ops milestone (l3) - they are all linked up.
I think this shows Milestones with NO epic blocking it
See also LSST Verification & Validation Documentation and LDM-692 (VCD).
Test Plans due in the next 45 days
Milestones due in the next 45 days
Risk items needing review
Overdue risks (obligation date passed)
Risk mitigations due at the end of this month
Overdue risk mitigations
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.
