SoftwareReview October 18
Software Review Planning Meeting Friday October 18, 2013, 14:30-15:30.
- +1-866-740-1260 : US+Canada
- +1-303-248-0285 : International
- then enter participant code: 3421244# (remember the "#").
- or www.readytalk.com (and code without the #)
Attendees: Curtis Meyer, Justin Stevens, Mark Ito and David Lawrence.
- Minutes of the last meeting
- Discussion of Presentations
- Morning talk given by Curtis will present an overview of progress and will end with calibration and manpower summaries.
- Afternoon I, given by Mark Ito will provide a picture of how the data flows from the experiment to the analysis. It will also discuss the completed and planned data challenges.
- Afternoon II, given by David Lawrence will focus in on ~two of the major software updates since the last review.
- Afternoon III, given by Justin Stevens will focus on how we do Physics Analysis, describe the Workshop, and Justin will serve as the software user.
- Discussion of Manpower
- Graham's Computing Hardware Acquisition Schedule
- Discussion of Written Material
The meeting started with a brief discussion of the planned talks for the software review, and then the note that was sent to Rolf on these activities. We then moved onto timelines for getting the talks done. Mark also suggested the possibility of moving the description of the online data challenge from his talk into David's talk. We agreed on the following timeline.
- Next week we post a list of the slides that will be in each talk so we can make sure that the relevant topics are covered.
- By November 8, we have first drafts of all four talks.
We then discussed the manpower tables that are included in the written material. These came from a spreadsheet that David put together in 2012 and David agreed to survey the collaboration again to try and updated the manpower situation, and then work on extending the original table to include 2015.
We then moved onto the written material. Curtis agreed to continue working on this for about a week, after which he would try to get input from people. However, if people have comments now, Curtis would be more than happy to incorporate them. Also, if people feel important things are missing, now is a good time to at least set up the placeholder for them.
One item that we did discuss was code validation. Curtis noted that there is some material in the written documentation on that now, but it might not be complete. Apparently, Simon has been running some tools on a semi-regular basis. Mark also suggested that we set up a new cron job that we can use to track the performance of the code. Possible speed, memory footprint, etc....
The last item discussed was Graham's request for a computing hardware acquisition schedule. Curtis noted that there is a rough timeline in the written documentation and Mark agreed to try to turn that into a proposed schedule based on expected computing needs.