You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 35 Next »

Logistics

Date

  – 

Expect the DMLT meeting to start in the morning of  and conclude around lunchtime on  to enable travel that afternoon.

That there will a a pre-DMLT SST meeting on  .

Location

  • Princeton

Hotel / Per Diem

  • There is a block booking at the Nassau Inn.  Group Code "Booking ID" is 24465.  Please contact Yusra AlSayyad for assistance. 

Travel

Attendees

Traveling


Local

Agenda

Day 0: 2018-11-05

DM-SST meeting. Schedule will be provided by Leanne Guy.

Day 1: 2018-11-06

TimeTopicChairNotes
09:00WelcomeWil O'Mullane
  • Review outstanding actions
  • Review & adjust agenda





Break





Lunch





Break




17:00Close

Day 2: 2018-11-07

09:00



Break






Lunch






Break





17:00Close

Day 3: 2018-11-08

09:00



Break





13:00Close


Pre-Meeting Planning

Suggested topics for discussion


TopicRequested byTime required (estimate)Notes
Review of the DM people transitioning to commissioning
As discussed at the PST F2F meeting in September, DM should review the names of people going into commissioning
Milestone test plans
Continue work on content and dates for upcoming milestones
Descope optionsKian-Tat Lim

DBB and Consolidated DB SLAKian-Tat Lim
Are there ways of providing greater uptime and lower latency using rolling upgrades, schema evolution with backfill, planned Observatory maintenance windows and daytime maintenance, etc.?
Review of Calibration plansKian-Tat Lim
What raw data is being taken? What products are being generated? What are the possible CPP execution periodicities?
Unusual Commissioning modesKian-Tat Lim
What things that we normally think of as slowly-changing (e.g. camera geometry, voltage setpoints) might not be during Commissioning?
Review of L2 milestones due during calendar 20191 hour
Review of plans for S19 development cycle2 hours
Review impact of portal scope changesJohn Swinbank / Wil O'Mullane1.5 hours
  • What portal development will happen, and when?
  • How does this impact on other aspects of the DM system (e.g. who provides the UI for specifying and managing alert filters)?
Status of DPDDificationJohn Swinbank0.5 hours
  • Update on work started at the May DMLT F2F.
LSST Data ModelJohn Swinbank1 hour
  • Work has been ongoing in the DM-SST to develop a formal DM data model and to refine the way in which LSE-163 (DPDD), the cat pacakge, LDM-153 (the baseline schema) are generated and managed.
  • This should be presented to and agreed by the DMLT.
Transition to operationsJohn Swinbank1 hour
  • Early Ops funding is now available, and during FY19 (ie, this year) the ADs for both Data Facility and Science Operations (Margaret Gelman and Wil O'Mullane) are funded at 0.25 FTE. That's half an FTE coming out of DM management. How are we handling that?
  • Similarly there's a total of ~15 FTEs funded across Data Facility and Science Ops during FY20.
  • What are the plans and schedule for transitioning staff?
Product Tree and Document TreeUnknown User (gcomoretto)0.5 hour
  • Based on the modeling work done before the review this year, review proposed product tree, components characterization and relation with the document tree
Test Approach Using Jira0.5 hour
  • How to do test specs and test runs with ATM in Jira
Summit and Base Data Center Status and PlanningJeff Kantor1 hour
  • Brief overview of Summit and BDC construction status and move-in schedule
  • Identification of planned deployments of DM equipment to BDC, visits, tests/rehearsals in FY19 (and IT support required)
Workflow management1 hour
  • Where are we on the decision and implementation of a WMS?
L3 milestonesJohn Swinbank / Wil O'Mullane0.5 hour
  • We're lacking L3 milestones in PMCS which describe the availabilities of services and capabilities which we know are coming, particularly later in construction.
  • Obvious examples include:
    • Butler Gen 3 / PipelineTask as the regular production environment;
    • Roll-out of the Pegasus WMS (or some other WMS);
    • Data back bone capabilities.
  • In addition, some existing milestones seem unclear about who is delivering what. For example:
    • “DM-SUIT-16: Commissioning DAC“ — is that really a SUIT deliverable?
    • “DM-SQRE-5: Notebook service ready for general science“ — is that really a SQuaRE deliverable?

  • We should have milestones describing the delivery of effectively everything in LDM-148.
  • The half hour time estimate is for Wil O'Mullane to state the above, set expectations, and develop a timeline for delivery. If we actually start creating milestones during the meeting, it could take arbitrarily long.


  • Attached Documents

No files shared here yet.

  • No labels