Difference between revisions of "OWG meeting 19-Jul-2007"
m |
|||
| Line 32: | Line 32: | ||
Attendees: Elliott W, Fernando B, Vardan G, Carl T, David L, Dave A, Elke A, Simon T, Elton S, Graham H, Dave D. | Attendees: Elliott W, Fernando B, Vardan G, Carl T, David L, Dave A, Elke A, Simon T, Elton S, Graham H, Dave D. | ||
| + | |||
| + | Elliott went over minor changes to the Wiki pages, including the beginnings of an online task list, a list of potential future | ||
| + | meeting topics, and a page listing the status and disposition of all action items. | ||
| + | |||
| + | Next up was a discussion of the need for a one-page document listing online design goals and requirements (thanks to Elton for pushing this). It would list the basic rate and other performance requirements, and would form the basis for understanding the roles of the various groups involved and how the work would be divided. This document would evolve as new personnel arrive, roles got modified, etc. Elliott agreed to get a first version out by the end of next week. | ||
| + | |||
| + | Graham next described his vision of the role of the JLab DAQ group in the Hall D online. This led to a long, open discussion covering many topics and points: | ||
| + | |||
| + | * History of JLab DAQ group. | ||
| + | * Development of the CODA toolkit from the early 1990's (vsn 1) until now (vsn 2, and soon vsn 3). | ||
| + | * DAQ group provides software toolkit, some DAQ-specific hardware, hardware recommendations, front-end drivers, etc. | ||
| + | * Experiments must supply an online group to adapt CODA to their experiment. | ||
| + | * DAQ group provides support, consultation, helps with trouble shooting, etc, but experiment experts usually are the first responders when problems arise. | ||
| + | * DAQ group is effectively on call 24 x 7 x 52 | ||
| + | * Hall B made major mods to their version of CODA, but this is discouraged. Some H-B mods will be integrated into CODA. | ||
| + | * Current CODA development is very strongly motivated/directed by Hall D requirements. | ||
| + | * Broadly speaking: Graham is working on the multiple-parallel event-builder. Vardan is responsible for run control system. Carl and Elliott work on many parts involving data/message transfer and I/O. Dave A handles front-end hardware and drivers. Ed works on trigger distribution, timing, designs special hardware, etc. | ||
Revision as of 16:50, 19 July 2007
Contents
Agenda
- Review minutes from the 15-Jun-2007 meeting
- Online Action Items
- Additions to DAQ/Online/Controls main page
- Need for online design goals document (200kHz trigger, 1 GB/sec, 100 Mb/sec, etc)
- Role of JLab DAQ group in Hall D online - Graham Heyes
- Preliminary Online Work Breakdown
Time/Location
10:00am Thu 17-Jul-2007 Cebaf Center F326
Announcments
- Please look at Online Work Breakdown and send me comments
- Please add topics to Possible Meeting Topics
Next Meeting
- Thurs 9-Aug-2007 10am CC F326
New Action Items from this Meeting
- Design document listing basic requirements and design goals (EJW)
- Milestones from JLab DAQ group perspective (Graham H)
- Milestones from Hall D perspective (EJW)
Minutes
Attendees: Elliott W, Fernando B, Vardan G, Carl T, David L, Dave A, Elke A, Simon T, Elton S, Graham H, Dave D.
Elliott went over minor changes to the Wiki pages, including the beginnings of an online task list, a list of potential future meeting topics, and a page listing the status and disposition of all action items.
Next up was a discussion of the need for a one-page document listing online design goals and requirements (thanks to Elton for pushing this). It would list the basic rate and other performance requirements, and would form the basis for understanding the roles of the various groups involved and how the work would be divided. This document would evolve as new personnel arrive, roles got modified, etc. Elliott agreed to get a first version out by the end of next week.
Graham next described his vision of the role of the JLab DAQ group in the Hall D online. This led to a long, open discussion covering many topics and points:
- History of JLab DAQ group.
- Development of the CODA toolkit from the early 1990's (vsn 1) until now (vsn 2, and soon vsn 3).
- DAQ group provides software toolkit, some DAQ-specific hardware, hardware recommendations, front-end drivers, etc.
- Experiments must supply an online group to adapt CODA to their experiment.
- DAQ group provides support, consultation, helps with trouble shooting, etc, but experiment experts usually are the first responders when problems arise.
- DAQ group is effectively on call 24 x 7 x 52
- Hall B made major mods to their version of CODA, but this is discouraged. Some H-B mods will be integrated into CODA.
- Current CODA development is very strongly motivated/directed by Hall D requirements.
- Broadly speaking: Graham is working on the multiple-parallel event-builder. Vardan is responsible for run control system. Carl and Elliott work on many parts involving data/message transfer and I/O. Dave A handles front-end hardware and drivers. Ed works on trigger distribution, timing, designs special hardware, etc.
