Page History

...

Item

Who

Notes

Project updates

There are many sources of project documentation (Docushare, Confluence, lsst.io, CLO, Slack, LCRs, etc etc).
- Docushare is the official system of record.
- But Docushare also contains myriad obsolete or unnecessary documents; shouldn't all simply be transferred to Operations.
- Expectation that Operations will use Docushare, but there remains work to do to sort this out.
- Software documentation, etc, belongs on lsst.io.
- No concrete action emerging from this.
Wil O'Mullane has asked Jeff Kantor to organize a review of networking.
- Likely carried out by telecon.
Discussion of (alternate) standard visits, and interaction with satellite trails.
Ongoing conversation with AURA leadership on coronavirus; more news when we have it.
- Leanne Guy requested not to make an announcement re the algorithms workshop until Victor has met with AURA leadership today.
Request from leadership to make sure that anybody transitioning from construction into commissioning is clear what their roles are.
DOE review of Camera finances in May (the DOE equivalent of the EVMS audit).
Camera schedule contingency dropping; now at ~30 days.

vF2F todo items

Task report

pages	120788118
columns	description,duedate,assignee
pageSize	40

CCB

Level 2 Milestones

Test Plans due in the next 45 days

Jira

server	JIRA
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues	20
jqlQuery	labels = TESTPLAN and resolution = Unresolved and due <= 45d order by id asc
serverId	9da94fb6-5771-303d-a785-1b6c5ab0f2d2

Milestones due in the next 45 days

Jira

server	JIRA
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues	20
jqlQuery	project = DM and labels = L2Milestone and team not in ("Telescope and Site") and resolution = Unresolved and due <= 45d order by id asc
serverId	9da94fb6-5771-303d-a785-1b6c5ab0f2d2

Rapid data processing at the LDF

Deferred from last week's meeting.
RHL will need to perform rapid processing in Chile (“rapid”, as distinct from “prompt”).
Some of that processing will need to be reproduced at NCSA.
- e.g. need to be able to generate quick-look ISR images both on the mountain and at NCSA.
- And the results of this processing should then be available as permanent data products.
We should expect that we don't know what types of processing will be necessary early in commissioning; need a general approach to running pipelines.
Possible to imagine this as a prototype of prompt processing, but it's not clear how that meshes with expected schedules.
Kian-Tat Lim identifies three issues:
- Does the generalization of processing fit into the existing prompt processing framework?
- Do we need a new framework?
- How long does it take to build such a new framework?
Consider e.g. deploying OCPS at NCSA, or generalized prompt processing.
We note that LDF is already busy, and there may be an opportunity cost to rolling out a service like this.
Agreed that:
- Robert Lupton will provide use cases, including soliciting them from the Commissioning Team;
- Based on those use cases, Kian-Tat Lim & Unknown User (mbutler) will consider how much effort would be involved in standing up such a service.
- The DMLT will then decide whether this overrides other priorities.

Robert Lupton — mediating with the Commissioning Team, provide Kian-Tat Lim & Unknown User (mbutler) with a list of example use cases for rapid processing at the LDF. 23 Mar 2020
Kian-Tat Lim & Unknown User (mbutler) — propose a design and schedule for deploying a rapid processing system at the LDF. 20 Apr 29 May 2020

DMLT travel & availability this week

Wil O'Mullane en route to Spain (visa renewal; mostly on leave this week in Ireland and UK - talk in Bath on Friday).

...

Space shortcuts