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 meetingsMario Juric
  • Review status of outstanding actions. No outstanding items as far as Jacek Becla can see
10minNews & progress over the past weekJacek Becla, Mario Juric
  • Directors' review
    • 27-29 July at SLAC, DM: ~45 plenary + 1 full day of breakout
    • Need to start thinking who to send from DM
  • Tentatively planning Verification Review for June
  • Discussions between MJ+JB and the Tucson teams (PO, SQuaRE, EPO, SysEng)
  • F2F draft agenda
  • Progress with revisiting WBS for NCSA and SQuaRE
3minReminders and deadlinesJacek Becla
  • Input for monthly status reports, due Tue May 10
  • Input from TCAMs for F16 plan, due Wed May 4
  • Slides for F2F due end of Wed May 11 (per agreement at this meeting. Mario wanted 7 days in advance)
  • Dissiminating information from TCAM and DMLT meetings to the DM team
5minCoordinating travel to larger and/or international eventsJacek Becla
  • Proposing to track through Conferences and Workshops with DM Involvement
    • need to have place for writing justification when proposing attendance through that page
    • currently every traveler must provide agenda. Would be easier if we coordinate / have link handy, if we would deal with situations when agenda not available at the time TRs are submited
5minUpdates re recent Nebula activity & processesDonald Petravick
  • We had a recent security incident on the Nebula cluster; will briefly report here on the cleanup & lessons learned
  • We need to discuss how to prepare for / deal with future cases. Best to have Mario for that. So postponing till next DMLT
10minDMLT F2F planningJacek Becla, Mario Juric

DM Leadership Team Meeting 2016-05-16 to 19, Face-to-Face

  • draft of the agenda updated (see the page above)
    • Need detail from WG chairs, list of breakouts already recognized as needed by the managers
    • Need a list of other items requiring F2F attention
  • deadline for submitting slides: next DMLT phonecon.
  • need to make sure local logistics is taken care of
    • Internet at the Aloft
    • Breakout rooms for Wed, Thu, Fri (NOAO+Steward?)
    • Taking the minutes
    • Lunches (ours + with the local team), dinner
  • discussion:
    • slides 1 week ahead is too much, especially since early notice was not given. Compromise: due end of Wed May 11, which leaves enough time for everyone to digest slides
    • concern: are we doing enough to prepare for the July/Aug reviews? Still not 100% clear what the outputs from the meeting are
    • WGs not fully disjointed
    • suggestion: swap some Tuesday topic with Wed breakout, see Gregory's comment on F2F page
10minWG UpdatesWG Chairs
 DMLT Travel & Availability This Week  
10minMultifit performance updatesJim Bosch
  • Jim writing technical note
  • have not found any "evidence of implausibility" of currently planned approach
  • need better shear estimation code, it is non-trivial
 Status of code supporting different camerasRobert Lupton
  • code related to supporting camera(s) is in worse shape than expected
  • Issue not algorithmic, but at code level, making it all work is not trivial
  • Mostly contained within DM, but need to discuss some issues with the Camera Team as well
  • unclear who is responsible for code in the camera packages. Two models to consider: centralized vs camera-specific teams supporting it
  • (gpdf): similar issues are arising in the SUIT-Camera meetings about visualization
  • lack of anyone in charge who would pay attention and work more closely with the Camera team (file format, header contents etc). Need to reorganize how we communicate with Camera team
  • John will capture need for improving camera packages in the input for F16 plan

 

Postponed for subsequent DMLT:

TimeItemWhoNotes
5minUpdates re recent Nebula activity & processesDonald Petravick
  • Lessons learned from the Nebula security incident
5minDM source code license policyMario Juric
  • 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
 --- Add more proposed topics here. 

 

Action items