160 likes | 315 Views
DAQ Status Report. GlueX Collaboration – Jan. 29-31, 2009 – Jefferson Lab David Abbott (In lieu of Graham). Introduction. Projects Hardware/Electronics Front end Back end - Event builder, EMU, etc… Experiment Control and messaging Administrative news etc…. Hardware/Electronics.
E N D
DAQ Status Report GlueX Collaboration – Jan. 29-31, 2009 – Jefferson Lab David Abbott (In lieu of Graham) GlueX Collaboration Meeting - Jan 2009 - Jefferson Lab
Introduction • Projects • Hardware/Electronics • Front end • Back end - Event builder, EMU, etc… • Experiment Control and messaging • Administrative news etc… GlueX Collaboration Meeting - Jan 2009 - Jefferson Lab
Hardware/Electronics • Reported on elsewhere • Highlights: • TI Prototype testing – proof of trigger/clock distribution design principle • Final TI (v3 this year) will be used with existing experimental program (2.6) as well as support 3.0 DAQ readout. • Trigger supervisor has preliminary design but main work not started yet (Note: 128 crate limit) • PCI Based TI board - Available with software library support • FADC tirgger/readout at 160 KHz. Both FADC, F1TDC revision 2 designs are underway. GlueX Collaboration Meeting - Jan 2009 - Jefferson Lab
Front end • Becoming clear that Intel/Linux isviablefor CODA front end. • Main effort is rewriting the PPC/VxWorks drivers to for Intel/linux. • Currentlyhavea CODA 2.6 ROC running on Linux with VME TI and PCI TI based readout. Can use 6 GeV program and development setups for a “testbed”. • Beginningon framework of the CODA 3 ROC and how it communicates with Run Control and Back end (EMU). • Increased data rate requirement (3 GB/s) should not be a showstopper. GlueX Collaboration Meeting - Jan 2009 - Jefferson Lab
CTP L1 Trigger (optional) SD Clock/Trigger Distribution Linux on the Front End CPU - GE 7865 Intel Core 2 Duo (2.1GHz) Dual GigE TI (ver 3) CODA 2 & 3 support FADC F1TDC VXS Crate 110 MB/s off the CPU on a single GigE link uses only 6% of a single CPU and minimal jitter on front-end response. Front End System GlueX Collaboration Meeting - Jan 2009 - Jefferson Lab
Back End • Prototype parallel EB using EMU framework. • Prototype parallel Event Recorder using EMU. • EMU control and monitoring now uses cMsg. • interface to Run Control (AFECS) started. • Start to convert prototypes into something that can be used in a real experiment. • Event format decoding/encoding (EVIO). • True event building. • Look at viable DAQ architectures for staged/parallel event building and future L3 farm. GlueX Collaboration Meeting - Jan 2009 - Jefferson Lab
Event Format • Event recorder (EMU) • Has to decode event blocks from EB. • has to write data files in EVIO format. • Event Builder (EMU) • must be able to decode events coming from ROCS or other stages of EB. • Must be able to encode headers for full/partial events. GlueX Collaboration Meeting - Jan 2009 - Jefferson Lab
CODA Event I/O DATA BLOCK ROC RAW DATA GlueX Collaboration Meeting - Jan 2009 - Jefferson Lab
GLUEX DAQ ACHITECTURE OPTIONS GlueX Collaboration Meeting - Jan 2009 - Jefferson Lab
ExperimentControl • AFECS - Java based framework for designing and implementing hierarchical, distributed control systems with intelligent agents. • Replaces classic Run Control in CODA 2.6 • AFECS now usescMsgforall internal communication (No JADE left). • New “plug-in” support for agent<->component communication (including EPICS-CA and SNMP). • Standardizing component data format for monitoring/display GlueX Collaboration Meeting - Jan 2009 - Jefferson Lab
AFECS Run Control GlueX Collaboration Meeting - Jan 2009 - Jefferson Lab
Wiener Crate Control/Monitoring DAQ component cMsg browser GlueX Collaboration Meeting - Jan 2009 - Jefferson Lab
Messaging • cMsgnow mature and being actively used (AFECS, CODA 2.6, Codalite). • Version 3.0 released. • Internal changes - Bugs being found and fixed • More robust handling of lost connections • New “payload” support • EMU using cMsgfor control, monitoring and message logging. GlueX Collaboration Meeting - Jan 2009 - Jefferson Lab
The good and the bad • CODA version 3 is now a BIA Activity: • CODA now “critical” to lab operations. • More work than people. • Downside - Much more paperwork. • Upside - Some of the paperwork is actually useful! • Have a budget that includes funding to increase DAQ staff – by two scientists. • We finally got approval to hire one!! GlueX Collaboration Meeting - Jan 2009 - Jefferson Lab
The ugly • Despite BIA status and full funding lab level management is not approving posting of new positions (“replacements” only). • Without extra help projects are slipping relative to the current baseline. • Should be further along on several projects, but dealing with 6 GeV operation issues and increasing administrative responsibilities have slowed progress. GlueX Collaboration Meeting - Jan 2009 - Jefferson Lab
Summary • DAQ group is hiring!! • BIA funding is a good thing. • More formal project management is good. • All projects ARE progressing… • Those that do not depend on new hires progressing well. • Not yet exhausted the “wiggle room” in the schedule • Interest outside the lab in CODA related projects could provide additional support/development. • E906 experiment at Fermilabplan to use CODA • PANDA, NuSTAR, CBM interest in AFECS as control system GlueX Collaboration Meeting - Jan 2009 - Jefferson Lab