Difference between revisions of "2012 Software Review Planning Meeting: May 4, 2012"

From GlueXWiki
Jump to: navigation, search
m (Text replacement - "http://argus.phys.uregina.ca/cgi-bin/private" to "https://halldweb.jlab.org/doc-private")
 
Line 34: Line 34:
 
#*:
 
#*:
 
# Organization of Hall-D preparations for Review
 
# Organization of Hall-D preparations for Review
#* Introductory talk ([http://argus.phys.uregina.ca/cgi-bin/private/DocDB/ShowDocument?docid=1949 preliminary sildes]) with notes.
+
#* Introductory talk ([https://halldweb.jlab.org/doc-private/DocDB/ShowDocument?docid=1949 preliminary sildes]) with notes.
 
#* Numbers for the table
 
#* Numbers for the table
 
#** Software Manpower within collaboration ([https://halldsvn.jlab.org/repos/trunk/docs/offline/ProjectProgress/manpower_survey.pdf PDF],[https://halldsvn.jlab.org/repos/trunk/docs/offline/ProjectProgress/manpower_survey.ods ODS])
 
#** Software Manpower within collaboration ([https://halldsvn.jlab.org/repos/trunk/docs/offline/ProjectProgress/manpower_survey.pdf PDF],[https://halldsvn.jlab.org/repos/trunk/docs/offline/ProjectProgress/manpower_survey.ods ODS])

Latest revision as of 16:07, 24 February 2017

Main Hall-D Software Review Page


Connecting

Phone:

  • +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 #)

Agenda

  1. Previous Meeting (Apr. 27, 2012)
  2. Status of Review Organization (JLab organizers)
    • Committee (Wenaus(chair), Marchand, McBride, Purske, +1??)
    • Charge
    • Agenda
  3. Time-line for preparations
  4. Organization of Hall-D preparations for Review

Minutes

Attendees: David L., Mark I., Matt S., Curtis M. (Eugene was ited up with S&T review dry runs and couldn't make it)

All Hall's SRP meeting

Dave and Mark reported briefly on the meeting earlier in the week organized by Rolf for all Hall's. Highlights were:

  • Rolf wanted the afternoon talk shaved down to 20 minutes instead of the current 45. Extra slides could be backups.
  • Written materials don't really need to be done prior to June 1st

Slides

We discussed the length of the afternoon talk some to try and decide on how best to prepare for it without more definite guidance. We agreed that the first step would be to generate the 45 minute talk as planned and then exercise one of a couple of options for cutting it down. The two main options are:

  1. Mark certain slides as ones to skip, but keep them inline. That way, they are right there if questions emerge, but that can be quickly jumped through if there are no questions.
  2. Make copy of talk and move slides to backups until just a 20 minute talk remains.

Both options are similar, and both require that the same 45 minute talk be prepared first. It was agreed that David will proceed with that and then we can revisit the issue once the slides are in front of us.

We agreed that first drafts of all slides are needed by the end of next week so we can review them prior to the review Rolf will ne scheduling for May 14/15.

It was reiterated that one slide should emphasize the various workshops and tutorials we've had for GlueX.

Written Documentation

  • The RMP (Research Management Plan) document needs to be taken from elements already in the PAC proposal. Curtis will

work on this next week.

  • The Computing Plan document is well underway, but quite a bit more work is needed on it.
    • Matt will work on Physics Analysis section
    • We agree to have complete draft by the start of the collaboration meeting, May 21st/

Action Items

  1. First draft of slides ready by Friday May 11 (Curtis, Mark, David)
  2. Research Management Plan document prepared from PAC Proposal (Curtis)
  3. Check collaboration meeting schedule to try and fit dry runs into that schedule (Curtis)
  4. E-mail Rolf to tell him about dry runs during collab. meeting and ask if they can be considered out final dry run (Curtis)
  5. Add PAC Proposal cover sheets to DocDB (Matt)
  6. Add small spreadsheet used for proposal computer requirements to DocDB (also, full spreadsheet) (Mark)
  7. Complete new computing requirements spread sheet with time-modeling (Curtis, Matt)