Versions Compared

Key

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

...

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 on one Epic for each ops milestone (l3)  - they are all linked up.

I think this shows Milestones with NO epic blocking it

Jira
serverJIRA
jqlQueryfilter=23200
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2


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

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQuerylabels = TESTPLAN and resolution = Unresolved and due <= 45d order by id asc
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2

Milestones due in the next 45 days

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = DM and labels = L2Milestone and team not in ("Telescope and Site") and resolution = Unresolved and due <= 45d order by id asc
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2

Risk Review



Risk items needing review

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,status,days since review
maximumIssues20
jqlQueryproject = "Risk Management" AND issuetype in (RM-Risk, RM-Opportunity) AND status = "Active Risk/Opportunity" AND component = "Data Management" AND "Days Since Review" >= 60 ORDER BY cf[14809] DESC, status DESC, cf[13108] ASC
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2

Overdue risks (obligation date passed)

Jira
serverJIRA
jqlQueryproject = "Risk Management" AND issuetype in (RM-Risk, RM-Opportunity) AND status = "Active Risk/Opportunity" AND status = "Active Risk/Opportunity" AND component = "Data Management" AND "Obligation Date" < now() ORDER BY cf[14809] DESC, status DESC, cf[13108] ASC
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2

Risk mitigations due at the end of this month

Jira
serverJIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = "Risk Management" AND issuetype in (RM-Risk, RM-Opportunity) AND status = "Active Risk/Opportunity" AND status = "Active Risk/Opportunity" AND component = "Data Management" AND "Obligation Date" < now() ORDER BY cf[14809] DESC, status DESC, cf[13108] ASC
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2

Overdue risk mitigations

 

Jira
serverJIRA
jqlQueryproject = rm AND issuetype = rm-handling AND status = Planned AND component = "Data Management" AND "Anticipated completion date" <= endOfMonth() AND "Anticipated completion date" <= now() ORDER BY status DESC, component ASC, assignee ASC, reporter ASC
serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2

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 Standupas needed
Action review



...