GlueX Data Challenge Meeting, July 16, 2012

Meeting Time and Place

The meeting will be on Monday July 16, 2012 at 1:30pm EDT. For those people at Jefferson Lab, the meeting will be in room F326.

Meeting Connections

To connect from the outside:

1.) ESNET:

   Call ESNET Number 8542553 (this is the preferred connection method).

2.) 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)

3.) EVO:

   A conference has been booked under "GlueX" from 1:00pm until 3:30pm (EST).

• To phone into an EVO meeting, from the U.S. call (626) 395-2112 and then enter the EVO meeting code, 13 9993. Instructions for the Phone Bridge to EVO.
• Skype Bridge to EVO

Agenda

1. announcements
   1. Computer Center has been warned: jobs, tapes
2. discussion of agenda for this meeting
   1. Mark's list of topics
3. review of minutes from previous offline meeting
4. scope of this challenge
   1. document of scope: Curtis's document, with on-going revision
   2. time-line
   3. grid vs. JLab
5. mini-data challenges?
   1. appropriate tools: WMS? Others?
   2. example of a minimal framework for job management: Mark
6. analysis system design plan
   1. ideas for analysis system: Paul M.
7. future challenges
8. organization
   1. meeting time confirmation (or change)
   2. subsequent meetings open to all interested collaborators?
9. finalization of REST format: record size and performance numbers
10. gridmake database entry

Minutes

Curtis agreed to convert document 2031 into a Wiki page. The page is now wvaiable asPlanning for The Next GlueX Data Challenge.

Data Challenge Meeting

Richard Curtis, Paul Matt Mark, Eugene, David

grid ftp tools, directly access to tape from off-site srm

grid and jlab

Matt: physics huge sample of phythia sufficient scale of physics signal small, not a DC issue

december january time frame

set-up milestones

revised rest format

gridmake

consensus on rest format dcth to dttb big cost associated, 30 hz re-swim a track 1.8 freeze on that

---