21 september 2012 gretina swg 1 2012 gretina swg meeting carl lionberger lbnl gretina daq...
DESCRIPTION
21 September 2012 GRETINA SWG 3 Event Processing Crystal Event Builder Segment events Crystal events Signal Decomposition Interaction points Global Event Builder Tracking 37 segments per detector 1-28 crystals Global Events Data from Auxiliary Detectors Analysis & Archiving Data from Germanium Detectors Goal: Processing 20,000 Gamma rays /secTRANSCRIPT
21 September 2012
GRETINA SWG
2
Early View
Aux. Det. Trigger
Digitizers
28 Crystals
Data Storage
2.2 MB/s
Aux. Det. Data
66 MB/s
75 dual Processors
Workstations, Servers
6.9 MB/s
2.3 MB/s + Aux. Data
Network Switch
Processing Farm
Readout CPU
Crystal
Pre - amplifier
Trigger and Timing Modules
21 September 2012
GRETINA SWG
3
Event Processing
Crystal Event Builder
Segment events
Crystal events
Signal Decomposition
Interaction points
Global Event Builder
Tracking
37 segmentsper detector
1-28 crystals
Global Events
Data fromAuxiliaryDetectors
Analysis & Archiving
Data fromGermaniumDetectors
Goal:Processing 20,000Gamma rays /sec
21 September 2012
GRETINA SWG
4
GRETINA DAQ Processes Almost all DAQ programs both in the
IOCs and on the cluster are written, at the top level, in SNL
The main control structures are states and transition between states
syntax is C-like and C code can be embedded or called
interface to EPICS PVs is integral to language
a state program can have multiple state sets, each a separate thread.
Each program has <name>.st, <name>IF.c, and <name>IF.h
21 September 2012
GRETINA SWG
5
The Basic DAQ States
All the DAQ programs have these same two basic states
– Setup stateIn setup, it is allowable to change
hardware and run parameters– Run state
This is the state where data is acquired, runtime-processed, and saved
Transition between Setup and Run is controlled by PV Online_CS_StartStop
That PV is served by the soft ioc gretClust on dogs
21 September 2012
GRETINA SWG
6
Processes and Communications
21 September 2012
GRETINA SWG
7
Digitizer Readout
21 September 2012
GRETINA SWG
8
Signal Decomposition
21 September 2012
GRETINA SWG
9
Global Event Builder
21 September 2012
GRETINA SWG
10
Network
21 September 2012
GRETINA SWG
11
As-Designed Staging
21 September 2012
GRETINA SWG
12
Mode 2
21 September 2012
GRETINA SWG
13
Mode 3
21 September 2012
GRETINA SWG
14
Mode 2 and 3
21 September 2012
GRETINA SWG
15
3 to 2
21 September 2012
GRETINA SWG
16
EPICS CA Universes
It is possible to run several copies of an EPICS installation on the same network without the identically-named Pvs in each copy talking to each other.
This is done by setting two environment variables that control IP ports EPICS uses.
In GRETINA, this allows running half the cluster with a DAQ acquiring data, and the other half with a DAQ running 3to2.
21 September 2012
GRETINA SWG
17
GRETINA DAQ Code Layout
Code units are structured as EPICS applications directories
EPICS applications support multiple-architecture builds and straightforward linkage between multiple “apps”
Build system based on static Makefiles
<appname>/ configure <appname>App/ Db/ src/ iocBoot/ st.cmd include/ bin/ <arch1> <arch2> lib/ db/
21 September 2012
GRETINA SWG
18
Revision Control and releases
CVS is used for version control Releases are independent of version
control tags, and include several Apps Separate releases may be used for
IOC boots and for cluster; currently the former is in release 10-5 and the latter 11-1.
Essential Apps in a release: gretClust, Track, Decomp, gretVME, tcDig, tcDet
Releases are directories in the /global/devel/gretTop directory