DAQ WS03 Sept 2006Jean-Sébastien GraulichSlide 1 Wrap Up o Control and Monitoring o DDAQ o Interface between DDAQ and MCM o Infrastructure Jean-Sebastien Graulich, Geneva

DAQ WS03 Sept 2006Jean-Sébastien GraulichSlide 2 Control and Monitoring  Peter Owens presented General Architecture, Subsystem Integration and User Interface  Subsystem integration: Recommendations Use File System convention Use standard hardware (Hytec 9010 IOC) Use Simulation Name Convention

DDDD-TT-CCCCC-NN:SSS:RRRRRR Max 3 char Max 5 char Max 3 digits Max 10 char Agreed

DAQ WS03 Sept 2006Jean-Sébastien GraulichSlide 4  Actions: Prepare the list of Technical Area codes (Equipment codes are under the responsibility of the subsystem developer). Names should be approved by Peter Owens Set up a DAQ web site web master: Vassil Verguilov

DAQ WS03 Sept 2006Jean-Sébastien GraulichSlide 5

Colour Scheme * Grey - background * Blue - control * Green – monitor/on/open/OK * Yellow – * Red – alarm/off/closed * White – * Brown - Clickable invalid warning

DAQ WS03 Sept 2006Jean-Sébastien GraulichSlide 7 RF Control System  Andy Moss introduced the Direct Digital Synthesizers as very flexible way to produce RF Can be programmed via serial ports Exists in 4 channel version: Allows independent control of 4 RF channels synchronised to the same clock, with excellent isolation between channels Can be interfaced with Epics  Digital timing system with 5 outputs Can EPICS provide the timing signal? ->Triggered Discussion on RF phase measurement RF amplitude measurement

Basic Layout of LLRF system

DAQ WS03 Sept 2006Jean-Sébastien GraulichSlide 9 RF  Decision RF phase: A logic pulse with precise constant phase w.r.t the RF should be sent to the TOF TDC We’ll use the locking signal and not zero crossing of the probed RF field A signal should be sent to the DDAQ when the cavities are locked  Action Investigate the possibility of using ~GHz waveform digitizer (oscilloscope) to measure the RF amplitude Contact MTA people for tests

DAQ WS03 Sept 2006Jean-Sébastien GraulichSlide 10  Fritz Bartlett presented D0 EPICS Extensions for MICE Significant Event System Replaces the standard Alarm handler Fritz is willing to make SES “D0 independent” COMICS (Experiment Control System) GUI  The possibility to use SES will be seriously considered  The need for an Experiment Configuration System is recognized

DAQ WS03 Sept 2006Jean-Sébastien GraulichSlide 11 Subnets  Fritz strongly recommended to set up a subnet for the C&M (IOC are not protected)  A separate subnet is needed for DDAQ

DAQ WS03 Sept 2006Jean-Sébastien GraulichSlide 12 Tracker C&M  Alan Bross has shown that  Alan Bross has shown that the basic infrastructure for the MICE tracker C&M can be copied from D0 GUI Python Code EPICS implementation  To do Customization to MICE (considerable weight loss) Develop a stand-alone VLPC cryostat C&M application

DAQ WS03 Sept 2006Jean-Sébastien GraulichSlide 13 PID Control Naming convention TOF EMC CKV Station 01, 02, 03 Part # (01 for KL, 02 for SW) Part # (01 or 02) MICE-DDD-HVPS-##:###:HVSP Channel #

DAQ WS03 Sept 2006Jean-Sébastien GraulichSlide 14 TOF0 TOF1 TOF2 USCDSC Tracker 1 Tracker 2 EMCAL  The Ideal GUI  Each Detector has a color:  Each Detector has a color: Green= FULL_READY Yellow= OUT_OF_RANGE_L2 Red= OUT_OF_RANGE_L3 or TRIPPED or NOT_READY White= INACTIVE  Each Detector is clickable, a panel pops up with the status of each individual channel  The same panel can be used to edit the settings, providing a password

DAQ WS03 Sept 2006Jean-Sébastien GraulichSlide 15  DDAQ & MCM Interface 1) MCM should know and archive the status of DDAQ 2) DDAQ should not run when MICE is not ready In particular the run should be stopped when something goes wrong in one subsystem 3) DDAQ should incorporate some data under the control of MCM which have a physical meaning: e.g. Hall Temperature, Pressure and Temperature in the Absorber, Current in the magnets, etc At some point we will need a list… This data will be collected asynchronously during the run, written in file and included in the data stream at the end of the run Control Interface Data Interface

DAQ WS03 Sept 2006Jean-Sébastien GraulichSlide 16 Data base  Discussion initiated Some Data Base is needed Detector Configuration Calibration and Geometry DATE is using MySQL C&M archive should allow random access  Action ORACLE cost estimation – Paul Kyberd Find other options - All

DAQ WS03 Sept 2006Jean-Sébastien GraulichSlide 17 Trigger  4 Particle Trigger Conditions for Normal Events Burst: All ISIS bunch crossing with the target can produce a particle trigger, providing the FEE is not busy Beam: Burst x TOF0 Timing given by Burst Upstream: Beam x TOF1 Timing given by TOF1 Traversing: Upstream x TOF2 Timing given by TOF1  Trigger Receiver: CAEN V Ch I/O

DAQ WS03 Sept 2006Jean-Sébastien GraulichSlide 18