Online Major Milestones

From GlueXWiki
Jump to: navigation, search


Below we outline our strategy to develop an online system that meets the design goals listed in Online_Design_Goals and Elton's Hall D Design Goal document (GlueX-doc-866 in the DocDB). Here we only list major milestones along this development path. Detailed milestones and assignment of names can be found in Elke's Action Item Tracker and other documents. As decided in the 14-Dec-2008 OWG meeting, major electronics milestones relevant to the online effort are also included here. See the Electronics pages for complete information.

Basic Considerations

The complete DAQ (approximately 80 full crates) must be ready for commissioning the complete detector with cosmic or pulser triggers by 1Q FY 2014. First beam to the hall is expected in 4Q FY 2014, with low-rate production data taking expected to start in 4Q FY 2015. High-rate production data taking may start as early as 4Q FY 2016, assuming funds are available to upgrade the detector. Beneficial occupancy of Hall D is expected in summer 2010, counting house in fall 2011. Trigger, DAQ, monitoring, and control systems will be needed starting in early 2011 to check out detector subsystems as they are being installed and commissioned.

Note that the 12 GeV project specifies a beam rate of 10**7 photons/sec, but that we plan an eventual upgrade to 10**8. All components must be designed to be capable of, or upgradable or expandable to, 10**8 running.

Needed for Subsystem Review May 2008 and for CD-3 Review Summer 2008

N.B. All designs must satisfy the design goals described in Online_Design_Goals.

  • Overall electronics diagram (crates, modules, HV and LV distribution, trigger system, clock/trigger distribution, DAQ, networking, etc) - Mar 2008 - done May 2008.
  • Interface document from Electronics group defining front-end modules and trigger system - Apr 2008 - done May 2008.
  • Interface document from DAQ group defining clock/trigger distribution system and CODA 3 major components and functionality - Apr 2008 - done May 2008.
  • Interface document with IT division defining networking strategy, plan for moving data from counting house to storage silo, etc. - Apr 2008.
  • Conceptual design of trigger/DAQ/monitoring system based on the above three documents - Apr 2008 - done May 2008.
  • Conceptual design of controls and monitoring systems - Apr 2008 - done May 2008.


  • An "interface document" defines major system components and their functionality, as well as fundamental agreements between two parties.
  • A "circuit specification" describes circuits at a level such that an electronics design firm could produce the devices. E.g. I/O signal levels and circuit functionality are described in detail, but IC choice is not specified.

Trigger/DAQ Milestones

Note: many electronics R&D and PED deliverables are not listed below


  • Production event transfer system - done Aug 2006
  • Production event I/O package - done Aug 2006


  • DAQ test farm by 28-Sep-2007 (PED deliverable) - done Jan 2007
  • Prototype software component framework - done Jun 2007
  • Prototype run control system - done Jun 2007
  • Production inter-process communication package - done Nov 2007


  • Subsystem review May 2008 and CD-3 review July 2008, see milestones above - most done May 2008
  • Electronics
    • Preliminary energy-sum and master trigger design by Sep 2008 (PED deliverable)
    • Prototype FADC125 by Aug 2008
    • Prototype TI board by Nov 2008 - done June 2008
    • Prototype SD and CTP boards by Nov 2008
    • Prototype single crate timing and trigger distribution by Nov 2008
  • Trigger
    • Demonstrate crate-sum trigger components operating at 250 MHz by Nov 2008.
    • Demonstrate 200 kHz triggering and high-speed readout (> 300 MB/s effective) of multiple F1/FADC boards in a single crate by Nov 2008.
    • Revisit and verify event size, and backplane and network bandwidth requirements by Nov 2008
  • DAQ
    • Prototype staged/parallel event builder by Sep 2008 (PED deliverable)
    • Preliminary libraries for reading out F1TDC, FADC250 and FADC125 by Nov 2008 - F1TDC and FADC250 done June 2008
    • Simulation of full system at low rate (run control, ET, multiple EB's, ER, etc) by Nov 2008
    • Demonstrate 200 kHz staged parallel event building by Nov 2008
    • Demonstrate 200 kHz block event readout and transfer by Nov 2008
    • Prototypes of major CODA 3 components: readout controller, staged/parallel event builder, event recorder, and run control system by Nov 2008.


  • Prototype TD board by Apr 2009
  • Prototype SSP board by May 2009
  • Prototype TS board by Jun 2009
  • Prototype GTP board by Jul 2009
  • Develop CODA-based multi-crate electronics test stand by Jul 2009
  • Master trigger design by Aug 2009 (PED deliverable)
  • Prototype L3 farm management software by Sep 2009
  • Prototype F1TDC V2 by Sep 2009
  • Prototype multi-crate timing and trigger distribution by Oct 2009
  • Overall trigger design by Oct 2009
  • Revisit energy-sum trigger algorithm by Nov 2009.
  • FADC250 V2 by Nov 2009


  • Demonstrate multi-crate high-speed readout
  • Simulation of full system at high rate
  • Production front-end driver software
  • Production timing distribution system
  • Production trigger distribution system
  • Production component framework
  • Production software components
  • Production TI board
  • Production TS board
  • Production energy-sum and master trigger boards
  • Production silo data transfer system
  • Production event monitoring system
  • Production run management system


  • Integration and test of all final Trigger/DAQ system components by Sep 2011
  • Install trigger and DAQ in Hall D as electronics and detector components begin to arrive
  • Design silo data transfer system


  • Trigger/DAQ ready for testing hardware being installed in Hall D

Trigger/DAQ Detector Needs

DAQ systems of various sorts will be needed during detector development, construction, and checkout. Below, "parallel" means that parallel or staged event building is needed. "Small" means four crates or less, and "large" means more than four crates. In general, parallel readout is only needed at very high rates, where a single network connection cannot handle all the data.

  • Single-crate DAQ systems are needed now (Jul-2007).
  • Small systems will be needed by Oct 2008.
  • Single-crate with trigger/timing needed for FCAL test Summer 2008
  • Large systems will be needed by Oct 2010.
  • Parallel, large systems will be needed by Oct 2011.

In all cases the readout crates may be full.

(Elton suggests creating a table of configurations needed...ejw, 14-Aug-2007)

Monitoring/Controls Milestones


  • Choose inter-process communication package - done Jan 2007


  • Choose controls framework by May 2008 - done Feb 2008
  • Design monitoring system by Jul 2008 (PED milestone)
  • Design alarm system by Sep 2008 (PED milestone)
  • Design experiment control system by Sep 2008 (PED milestone)
  • Choose request tracking system by Nov 2008
  • Choose code management framework by Nov 2008 (in conjunction with offline)
  • Choose build framework by Nov 2008 (in conjunction with offline)
  • Choose elog system by Nov 2008
  • Choose time history system by Nov 2008
  • Interface document with Accelerator division defining strategy for hall/accelerator inter-operation by Nov 2008.


  • Design event display by Mar 2009 (PED milestone)
  • Develop/test all monitoring/controls software components


  • Production event display by Nov 2010
  • Production elog system by Nov 2010
  • Production time history system by Nov 2010
  • Production alarm system by Nov 2010
  • Production monitoring system by Nov 2010
  • Production experiment control system by Nov 2010
  • Complete writing and testing of all other online monitoring/control components by Nov 2010


  • Install/debug all monitoring and controls systems in preparation for hardware installation in Hall D
  • Perform integrated system tests of all components


  • Monitoring/controls ready for testing hardware being installed in Hall D