Difference between revisions of "OWG meeting 4-Apr-2008"
From GlueXWiki
m |
m |
||
Line 14: | Line 14: | ||
==Announcements== | ==Announcements== | ||
+ | |||
+ | Subsystem review likely early in May, perhaps the week of 7-May-2008! | ||
Line 26: | Line 28: | ||
==Minutes== | ==Minutes== | ||
− | Attendees: | + | Attendees: E.Wolin, Simon T, Dave A, David L, Alex S, Carl T, Ben R, Graham H, Elke A, Dave D, Chris C, Fernando B, Jim S, Elton S. |
+ | |||
+ | |||
+ | '''DAQ Report''' | ||
+ | |||
+ | Graham gave a brief update on the status of DAQ projects and writing assignements. He will give a full report on the EMU next meeting. | ||
+ | |||
+ | * EMU (Event Management Unit) is basic CODA3 building block that accepts input data, transforms it, then sends the result out. | ||
+ | * Many utilities can be built from EMU: EB, ER, etc. | ||
+ | * EMU framework, XML config, and diagnostic interface completed. | ||
+ | * Code for moving data ready, but needs integration into EMU framework. | ||
+ | * EB part not ready, butsome testing using earlier prototypes successful. | ||
+ | * EMU build thread parallelizable for multi-core environment. | ||
+ | * DAQ group has organized writing assignments for subsystem review docs. | ||
+ | * Doc for each component plus top-level doc planned. | ||
+ | * Dave D asked if a "hardware switch architecture" is preferable to a "divide-and-conquer" strategy, i.e. do all rocs talk to all EB's, or are the rocs divided up among the EB's. DAQ group consensus was to divide-and-conquer at the roc level, although the other strategy could work. | ||
+ | |||
+ | |||
+ | '''250 MHz L1 Trigger Test and 200 kHz Front End Triggering Test''' | ||
+ | |||
+ | * TI may not be ready by review, so no 200 kHz crate triggering test, but can present design and architecture. | ||
+ | * Libs for board readout done, so some tests can be performed. | ||
+ | * No new 250 MHz testing planned, what we have now is what will be presented. More tests by end of this fiscal year. | ||
+ | * Plans for additional prototyping and testing by Sep, but not for May review. | ||
+ | |||
+ | |||
+ | '''May Subsystem Review''' | ||
+ | |||
+ | Elke gave an overview of what to expect at the review, and showed a preliminary agenda. | ||
+ | |||
+ | * Final pre-brief material will be placed on Elke's official subsystem review page. | ||
+ | * Preliminary pre-brief and other material will be place in [[May 2008 Subsystem Review]] |
Revision as of 09:45, 8 April 2008
Contents
Agenda
- Announcements
- Review of minutes from 28-Mar-2008 meeting
- Progress on EMU and other DAQ components - Graham H
- Status of 200 kHz front-end triggering test and 250 MHz trigger system test - various
- Preparation for May 2008 Subsystem Review, Online Major Milestones, etc. - all
Time/Location
2pm Fri 4-Apr-2008 CC F326
Announcements
Subsystem review likely early in May, perhaps the week of 7-May-2008!
Next Meeting
2pm Fri 11-Apr-2008 CC F326
New Action Items from this Meeting
Minutes
Attendees: E.Wolin, Simon T, Dave A, David L, Alex S, Carl T, Ben R, Graham H, Elke A, Dave D, Chris C, Fernando B, Jim S, Elton S.
DAQ Report
Graham gave a brief update on the status of DAQ projects and writing assignements. He will give a full report on the EMU next meeting.
- EMU (Event Management Unit) is basic CODA3 building block that accepts input data, transforms it, then sends the result out.
- Many utilities can be built from EMU: EB, ER, etc.
- EMU framework, XML config, and diagnostic interface completed.
- Code for moving data ready, but needs integration into EMU framework.
- EB part not ready, butsome testing using earlier prototypes successful.
- EMU build thread parallelizable for multi-core environment.
- DAQ group has organized writing assignments for subsystem review docs.
- Doc for each component plus top-level doc planned.
- Dave D asked if a "hardware switch architecture" is preferable to a "divide-and-conquer" strategy, i.e. do all rocs talk to all EB's, or are the rocs divided up among the EB's. DAQ group consensus was to divide-and-conquer at the roc level, although the other strategy could work.
250 MHz L1 Trigger Test and 200 kHz Front End Triggering Test
- TI may not be ready by review, so no 200 kHz crate triggering test, but can present design and architecture.
- Libs for board readout done, so some tests can be performed.
- No new 250 MHz testing planned, what we have now is what will be presented. More tests by end of this fiscal year.
- Plans for additional prototyping and testing by Sep, but not for May review.
May Subsystem Review
Elke gave an overview of what to expect at the review, and showed a preliminary agenda.
- Final pre-brief material will be placed on Elke's official subsystem review page.
- Preliminary pre-brief and other material will be place in May 2008 Subsystem Review