Logistics
Date
–
Location
This meeting will be held on Zoom:
- Join Zoom Meeting: https://washington.zoom.us/j/91337592385 (ID: 91337592385)
- Join by phone (US) +1 786-635-1003
- Join using SIP 91337592385@zoomcrc.com
For the meeting passcode, see #dm-camelot on Slack.
Participants
Agenda
Day 1: 2020-09-15 | ||||
---|---|---|---|---|
Time (Project) | Topic | Coordinator | Pre-meeting notes | Running notes |
Moderator: John Swinbank | ||||
09:00 | Welcome | Wil O'Mullane |
|
|
09:15 | Project news and updates |
|
| |
09:40 | John Swinbank transition |
|
| |
09:45 | Community support |
|
| |
10:30 | Break | |||
Moderator: Leanne Guy | ||||
11:00 | Improvements to the build and release system |
|
| |
12:00 | DMTN-148 |
| Move to have DMLT accept this document. Its a good overview of the situation/plan. KT shows diagram asks is this the flow ?
How are validity ranges stored : Tim - uses the directory structure and filename. QE curves come from Camera directly and are imported. Jim - big wall in gen 3 be tween certified and those not yet certified. Export and import deserve the ??? we need more research on that. RHL not sure squash in there for e.g. images. CamGeom deprecation was slipped in the document .. though Jim and TIm want to do this but surprised to see it in here. Otherwise happy with Document. John - if there are technical comments it does not need all DMLT but then we are back to the outstanding action. Colin - found it difficult to get a feel for what its describing - KTs diagram is a huge help. This may be partially why DMLT have not commented in detail. John agrees on the contend gave similar feedback to Chris - but nothing from DMLT was taken as all ok not befuddlement. If the latter we should include diagram and update. Tim - defects easy to handle perhaps its worth having a worked example. Jim asks if KT diagram works for defects .. Tim says yes but there may be other approaches. Jim - technote is good for the products which are fairly automatic (human yes/no) not the merged by human ones. John - we need write down we do not know when that is the case. This is somewhat the case in this doc GPDF crosstalk corrections are handled ? Tim - yes. In a given CDB3 instance when you replace a calibration is it replaced (is it bi-temporal). Jim its not but the idea would be to have a new collection not to actually replace the old one (new name). RHL - all the special cases for detectors are not covered - it may not be a uniform and nice as this makes it out to be. It could be messier when we get to it ... so hesitate to sign off. Back to CameraGeom ....
Jim - how we access calibrations is different to how they are written - may need Robert to propose an alternate design. There is a feasability issue. KT - best way forward ?
From zoom: John - where were we commenting on this document?
| |
QE 12:30 | Break | |||
Moderator: Wil O'Mullane | ||||
12:45 | Security trade-offs / RFC-723 |
| ||
13:15 | Generation 3 middleware plans and acceptance criteria |
|
| |
14:30 | Close | |||
Day 2: 2020-09-16 | ||||
No sessions! | ||||
Day 3: 2020-09-17 | ||||
Moderator: K-T Lim | ||||
09:00 | Milestones | In discussion at the JDR, a couple of issues emerged surrounding DM's milestones:
How can we address these? | Recording is on by consent of all for internal use. Frossie says she did not hear it quite the same (for first point of slide 2)- automation would be good. But we need a coherent story. Would be great to have automation for Levl3 milestones - but unlikely to get it. From chat: problem is that the milestones are not written in quantifiable ways Question about lag - yes updates lag by a month. How do you know which milestones are dependened on by others .. in DMTN-158 which show predecessors and successors. Could add line for predecessors, sucessors .. Michelle/Yusra woudl like that. John Swinbank add predecessor successor line ot milestone in DMTN-158 – | |
09:30 | Team status |
[ins] In [2]: import random [ins] In [3]: random.shuffle(teams) [ins] In [4]: teams Out[4]: ['SQuaRE (Frossie Economou)', 'DAX (Fritz Mueller)', 'Data Facility (Michelle Butler)', 'Alert Production (John Swinbank)', 'DM Science (Leanne Guy)', 'Data Release Production (Yusra AlSayyad)', 'Architecture (Kian-Tat Lim)'] (Sorry Frossie!) |
| |
10:30 | Break | |||
Moderator: | ||||
11:00 | Team status |
| ||
11:30 | Quiet Day |
| ||
12:00 | Wrap up |
|
Attached Documents
Action Item Summary
Description Due date Assignee Task appears on 15 Mar 2022 Frossie Economou DM Leadership Team Virtual Face-to-Face Meeting, 2022-02-15 to 17 18 Mar 2022 Kian-Tat Lim DM Leadership Team Virtual Face-to-Face Meeting, 2022-02-15 to 17 17 Nov 2023 Frossie Economou DM Leadership Team Virtual Face-to-Face Meeting - 2023-Oct-24 30 Nov 2023 Yusra AlSayyad DM Leadership Team Virtual Face-to-Face Meeting - 2023-Oct-24 11 Dec 2023 Gregory Dubois-Felsmann DM Leadership Team Virtual Face-to-Face Meeting - 2023-Oct-24 02 May 2024 Frossie Economou DMLT Meeting - 2024-04-22 22 May 2024 DMLT Meeting - 2024-04-22 22 May 2024 Richard Dubois DMLT Meeting - 2024-04-22 22 May 2024 Fabio Hernandez DMLT Meeting - 2024-04-22 22 May 2024 Tim Jenness DMLT Meeting - 2024-04-22 22 May 2024 Cristián Silva DMLT Meeting - 2024-04-22 Richard Dubois DMLT Meeting - 2024-04-29 Cristián Silva DMLT Meeting - 2024-04-29
Pre-Meeting Planning
Topic | Requested by | Time required (estimate) | Notes |
---|---|---|---|
Build system status | 30 minutes | In May 2020 we were unable to make a 19.0.1 patch release because of incompatible changes to the build and release system since the 19.0.0 release. The Architecture team were tasked with updating and simplifying the build and release system to ensure that this couldn't happen again (ie, whatever changes are made to the underlying infrastructure, we should always – within reason – be able to reproduce and update old releases). This session is an opportunity to review the plans that were made and the progress towards implementing them. | |
Community support | 30 minutes | As we move closer to operations, members of both Science Collaborations and the wider scientific community are taking an increasing interest in using our Science Pipelines and other software. We need to be able to provide them with technical support, without imposing an unreasonable burden on our on-project staff. In particular, in May of this year, specific concerns were noted about members of the community using Slack channels which were originally indented for technical discussion on the DM system to ask for technical support. Providing a coherent approach to support is challenging, given the wide range of interests and skills in the community, limited on project resources, and the need to provide a system which both supports the construction project now and which fully transitions into the System Performance department's Community Engagement team in the future. How much progress have we made since May? Do we now have a coherent message on what support we are providing, and through which channels? Have we clearly communicated that message to the leadership of the various science collaborations? Melissa Graham I (Leanne) might call on you to join this session | |
L3 milestones | 45 minutes | In discussion at the JDR, a couple of issues emerged with L3 milestones:
How can we address these? | |
G3 middleware acceptance | 1 hour | Present the criteria which have been developed for Gen3 achieving “feature parity” with Gen2, the associated test plan, and the associated timelines. | |
Jenkins futures | 30 minutes | The AP team would like to be able to run ap_verify in Jenkins against ticket branches in other packages. Kian-Tat Lim tells us this would involve a substantial retooling of Jenkins, but that some work in this direction is already in place. It'd be useful to understand what changes are planned. (This may be the same as “build system status” above; Kian-Tat Lim and/or Unknown User (gcomoretto) might wish to comment.) | |
DMTN-148 | 30 minutes | We need to work out a way of finally signing off on DMTN-148. Development is assuming it is accepted but it's still technically in limbo. | |