Location

BrowserRoom SystemPhone Dial-in

https://bluejeans.com/293724745/

  1. Dial: 199.48.152.152 or bjn.vc
  2. Enter Meeting ID: 293724745 -or- use the pairing code

Dial-in numbers:

  • +1 408 740 7256
  • +1 888 240 2560 (US Toll Free)
  • +1 408 317 9253 (Alternate Number)

Meeting ID: 293724745

(back to the list of all DMLT meeting minutes)

Time

10:00am PT

Attendees

Please add yourself to the attendee list as you connect to the meeting.

Regrets:

DMLT Meeting Goals

  • Weekly meeting to keep the DM leadership team coordinated, informed, and in agreement on the vision, priorities, and challenges facing DM construction, including surfacing and resolving issues and ambiguities needing our attention. The goal of this meeting is to provide information and decisions that help each one of us better direct our own (or our team's) activities.

Discussion Items

Guidelines: Propose items in line with the meeting rationale (see above); include as much information in the agenda notes; summarize, don't go into details while on the call; maximize time available for discussion. 

TimeItemWhoNotes
5minActions from past meetings
  • Review status of outstanding actions:
10minNews & progress over the past week

Systems Engineering (added on-the-spot)

Followup on Camera workshop issues:

  • Preservation of Camera e-Traveler: Richard Dubois and Gregory Dubois-Felsmann preparing a discussion paper for what is involved in preserving the data (and functionality), intended to lead to near-term change request.
  • Expansion of Camera DAQ (Summit) data buffer to accommodate ~8-10 days of data seems plausible.
    • Expect this could lead to another near-term change request.
  • Move of DM data-ingest functionality from Base to Summit, and creation of a centralized Summit Data Service
    • Kian-Tat Lim: Donald Petravick has prepared a memo on the idea and it will be shared at the Systems Engineering meeting tomorrow.
    • A key task at this point is to really collect all the use cases so that this can be scoped correctly.
    • Physical limitations (space, power, cooling) at the Summit are a serious concern.
  • Frossie Economou notes considerable interest in understanding the relationship between DM's QA tools and what the Camera will be building; planning to visit SLAC this summer.
10minReview preparations & discussion
  • The Director's Review is in ~2 weeks (July 27-29, 2016)
    • Still not clear on what is the deadline for final presentations to be delivered (will be double-checking with PMO)
      • July 20th continues to be the working assumption (for final delivery to reviewers; we need the presentations earlier for intra-project review).
    • Director's review speakers: still assuming JB, MJ, KTL.
    • WG progress: need 1-2 slide summaries of WG status by the end of this week:
      • Your WG objectives
      • What has been accomplished
      • Projected timeline to completion of remaining activities
    • Construction progress: need T/CAM contributions by 7/12 (see Jacek's e-mail)
10minWG UpdatesWG Chairs
5minLSST 2016 preparations
5minNext DMLT F2F Location and Dates
  • The draft proposal is to meet in Seattle, mid-October
5min

Dates for the IN2P3 conference


IN2P3 is organizing a "Getting ready for doing science with LSST data" workshop next year in Lyon. From their (accepted) funding proposal

We foresee that the following topics would be covered by the workshop program:

  • Scientific performance of the LSST image processing software stack processing or reprocessing of archive (CFHT-LS) and Subaru HSC images
  • Pushing the accuracy frontiers in astronomical image processing reaching LSST goals in astrometric and photometric precision, milli-mag photometric calibration
  • Data management and data handling requirements and solution in the LSST era
    • How to ensure efficient data organization and access suitable for LSST image processing and data analysis.
    • How to get most out of the parallel computing infrastructure
    • Ensuring efficient and seamless access to the LSST data for the scientific community parallel database issues, query methods and data format, etc.
They'll invite (at least) Don and Robert to be on the SOC, and have asked for DM presence at the workshop. They're asking us what dates would work best for DM – the current ones on offer are:
Note : we have excluded two weeks where the Monday corresponds to some holidays in France 
(May 8th, June 5th) 
May 2017
  • week 20: Mon 15 - Fri 19
  • week 22: Mon 29 - Fri 2 June
June 2017
  • week 24: Mon 12 - Fri 16
  • week 25: Mon 19 - Fri 23    ( <=== we should try to avoid this week) 
  • week 26: Mon 26 - Fri 30
July 2017
  • week 27: Mon 3 - Fri 7
What would work best for us?

DMLT Travel & Availability This Week


Postponed for subsequent DMLT / proposed for future DMLT:

TimeItemWhoNotes
5minUpdates re recent Nebula activity & processes
  • Lessons learned from the Nebula security incident
5minDM source code license policy
  • Proposal is to move to the BSD license, in line Jim Bosch's proposal in DM-5031 - Getting issue details... STATUS and the series of comments that followed.
    • Postponed: no time to discuss

Overdue RFCs

Status of unhandled work/technical debt.
  • Following discussion at the May DMLT, Jim Bosch filed tickets describing some technical debt issues.
  • There may be other work in danger of falling through cracks: Jim is probably not infallible.
  • Identifying and assigning this work is necessary for producing resource loaded plans.

--- Add more proposed topics here.


Action items