GlueX Data Challenge Meeting, December 3, 2012

From GlueXWiki
Revision as of 20:20, 3 December 2012 by Marki (Talk | contribs) (Events per file)

Jump to: navigation, search

GlueX Data Challenge Meeting
Monday, December 3, 2012
1:30 pm, EST
JLab: CEBAF Center, F326/327

Agenda

  1. Announcements
  2. Minutes from last time
  3. Conditions for DC-1
    1. Some Decisions
    2. Keeping track of parentage
    3. Events per file
    4. Inclusion of out-of-time interactions
  4. JLab Farm Mini-Challenge Status
  5. Grid status
  6. CMU status
  7. start date
  8. New action items

Meeting Connections

To connect from the outside:

Videoconferencing

  1. ESNET:
    • Call ESNET Number 8542553 (this is the preferred connection method).
  2. EVO:
    • A conference has been booked under "GlueX" from 1:00pm until 3:30pm (EST).
    • Direct meeting link
    • To phone into an EVO meeting, from the U.S. call (626) 395-2112 and then enter the EVO meeting code, 13 9993
    • Skype Bridge to EVO

Telephone

  1. Phone: (should not be needed)
    • +1-866-740-1260 : US and Canada
    • +1-303-248-0285 : International
    • then use participant code: 3421244# (the # is needed when using the phone)
    • or www.readytalk.com
      • then type access code 3421244 into "join a meeting" (you need java plugin)

Minutes

Present:

  • CMU: Paul Mattione, Curtis Meyer
  • JLab: Mark Ito (chair), David Lawrence, Dmitry Romanov, Simon Taylor
  • UConn: Richard Jones

Conditions for DC-1

Last Monday Mark sent out a list of proposals/decisions about details of the data challenge. We revisited some of these items.

Keeping track of particle parentage

Richard pointed out that a recent change that Paul pulled from the trunk into the dc-1.1 branch did not track parent particle ID correctly as intended, rather it only identified parent particle type. Paul needs this capabiltiy for his Cerenkov studies. Richard has suggested a change to the code to accomplish this and volunteered to implement it. He will do so and check it in on branches/sim-recon-dc-1.1. Mark promised to merge this change onto the trunk at the appropriate point in the future.

Events per file

Richard told us that 50 k events per job was about optimum for grid sites. We adopted that number for all of the sites.

Inclusion of out-of-time interactions