detector daq and trigger status

CM22 October 2008 Jean-Sebastien Graulich Slide 1

Detector DAQ And Trigger StatusDetector DAQ And Trigger Status

o Achievements Since CM21

o Detector DAQ Status

o Trigger Status

o Online Software

o Front End Electronics

o Schedule Milestones

o Summary

Jean-Sebastien Graulich, Geneva

ReminderReminder DAQ related activitiesDAQ related activities

Front End Electronics Transmission and digitization of analog data,

Readout hardware VME crates and boards, network in LCR

Readout Software Data transfer from FEE to disk

DAQ Human Interface Start and stop run, change configuration

Trigger Logic and Electronics Synchronize DAQ with target, generate and distribute trigger signals to

FEE. Data unpacking and interface with Analysis software (G4MICE)

Contribute to Online Reconstruction by hardware (CPU) and software Online monitoring

Produce histograms relevant for data quality checks, provide graphical interface to display them

Permanent data storage Produce software to archive data from Online disk buffer to Atlas center

Running the Human Interface is left to the user…Running the Human Interface is left to the user…


Achievements since Achievements since CM21CM21

CKOV, KL, TOF0 are included in the DAQCKOV, KL, TOF0 are included in the DAQ Scalars counting relevant rates are included in the Scalars counting relevant rates are included in the

DAQDAQ DAQ, Trigger and Online Monitoring systems have DAQ, Trigger and Online Monitoring systems have

been used successfullybeen used successfully Commissioning is well advanced but the systems are still

evolving Interesting data has been taken (see tonight)

Consolidation of the hardwareConsolidation of the hardware Major revision of the hardware installation and cabling

DAQ and Particle TriggerDAQ and Particle Trigger DAQ trigger scheme implemented according to final design TOF0 included in Particle Trigger

Documentation has been improvedDocumentation has been improved


Detector DAQ StatusDetector DAQ Status

Readout Code for TDC V1290, flash Readout Code for TDC V1290, flash ADC V1724 and Scalar V830ADC V1724 and Scalar V830

Now fully commissioned. Several bugs have been corrected in July

Readout Code for Tracker VLSBReadout Code for Tracker VLSB See Hideyuki’s talk

No progress yet on the interface with No progress yet on the interface with EPICSEPICS

One major change in the designOne major change in the design It is proposed to include the target data

(digitized target position and Beam loss signals) in the system like any other data source



Target DAQTarget DAQ

Progress in Integration of the Target Data into the Progress in Integration of the Target Data into the DAQDAQ

A technical solution has been agreed on together with the target group

No additional cost No risk of failure involved

Basic idea:

The target group will provide readout code for the new I/O card

The DAQ group will provide unpacking and online monitoring code

Discussion with the software group on how to include this data in G4MICE (Spill based data ≠ particle based data) took place. Implementation is under way.

The targe DAQ PC will be fully integrated in the Detector DAQ


Target DAQ PlanTarget DAQ Plan

Milestones for Integration of the Target Data into the DAQMilestones for Integration of the Target Data into the DAQ The new NI I/O Card is installed into mice2, and tested Done A VME-PCi interface CAEN V2718 is inserted into mice2 Done

and the driver is installed ISIS signals and analog Target Position signal are plugged Done

into the NI/IO card DATE is installed and running on mice2 (not connected to DDAQ) Sept

22 Installed but not running yet

The target group delivers the software for the stand alone Done readout and monitoring

Stand alone monitoring of ISIS signals and Target Position ~Done is demonstrated

DAQ group delivers the software for the DATE readout and Oct 13 online monitoring

mice2 is included in the DDAQ system and the target data is readout Oct 20

Online Monitoring of ISIS signals and Target Position inside Oct 27

DDAQ is demonstrated New target date is Nov 4

Trigger StatusTrigger Status

New Crate LayoutNew Crate Layout


DAQ Trigger distribution

Scalars and particle trigger NIM Logic

TOF discriminators and trigger CAMAC Logic

Interfacew/Target &Spill Gate

ShapersGVA Discri,KL cosmics trgTOF & CKOV

KL

DAQ TriggerDAQ Trigger


Four types of DAQ Four types of DAQ triggerstriggers

- PHYSICS- PHYSICS

- CALIBRATION- CALIBRATION

- Start of Spill- Start of Spill

- End of Spill- End of Spill

Event Type is tagged in Event Type is tagged in the data headerthe data header

Used to impose a well-Used to impose a well-defined sequence of defined sequence of events and online events and online check of check of synchronisationsynchronisation


DAQ Spill GateDAQ Spill Gate

Detailed documentation of the procedure to adjust Detailed documentation of the procedure to adjust the DAQ Spill Gate has been produced and tested the DAQ Spill Gate has been produced and tested with MOMwith MOM MSD

R1-N1-M3-P1 End Mkr

Particle TriggerRequests

Acceleration

DAQ Spill Gate

Target DepthInjection

Extraction

R1-N1-M4-P1 End Mkr

Adjust to tune the DAQ Spill Gate width

Normaly constant delay (DAQ Spill timing)

Machine start after delay in the target system

Spill Gate is always aligned to extraction


Machine

StartDAQ Gate ~ 3.5ms

Hits in GVA1

DAQ Spill GateDAQ Spill Gate


Particle TriggerParticle Trigger

Particle trigger has been upgraded to allow Particle trigger has been upgraded to allow easy selection of trigger condition easy selection of trigger condition

Now a press button operation, no cable swapping

Detailed documentation written and tested with Detailed documentation written and tested with MOMMOM

Available Trigger ConditionsAvailable Trigger Conditions1) Any logical OR combination of the GVA counters:

[GVA1] [OR GVA2] [OR GVA3]

2) Any logical AND combination of the GVA counters:

[GVA1] [AND GVA2] [AND GVA3]

3) TOF0

4) The logical AND combination of 1) or 2) with TOF0

The particle trigger signal is sent to channel 0 in The particle trigger signal is sent to channel 0 in each TDCeach TDC

TOF0 LogicTOF0 Logic

TOF0 has 40 TOF0 has 40 channelschannels

10 horizontal slabs 10 vertical slabs 2 PMts per slab


Because of hardware constraints,We also defineTOF0_H: OR over 8 central H slabsTOF0_V : OR over 8 central V slabsTOF0_EXT: OR over the 4 frame slabs

TOF0 signal is the OR over all the slabs of the AND of the two pmts of each slab

TOF0 Logic TOF0 Logic implementationimplementation


TOF1 will be included in the trigger in a similar way


Burst GateBurst Gate

ReminderReminder The burst corresponds to the micro structure of the beam Proton bunches crossing passing throght the target ~100 ns repeating every 324 ns (at the end of the accelration

cycle)

The ISIS beam position monitors can be used to The ISIS beam position monitors can be used to materialize the burst structurematerialize the burst structure

Envelope of Beam Position monitor inSector 7 (sum)



GVA1 hit

~Beam Loss

Spill Gate

Burst Gate

Burst Gate Burst Gate CorrelationCorrelation


GVA1 hit

Burst Gate made narrow

Online SoftwareOnline Software

Unpacking libraries have been Unpacking libraries have been extensively tested and work fineextensively tested and work fine

Upgrade for Tracker will be needed soon

Online Monitoring is now working Online Monitoring is now working really onlinereally online

A list of available histograms with description exists

Recent developments focused on the Recent developments focused on the interface with G4MICE (see Software interface with G4MICE (see Software session for more details)session for more details)

Basic architecture is now in place First task is to reproduce online histograms


Scalar in DAQScalar in DAQ

Scalars count hits inside the DAQ Scalars count hits inside the DAQ Spill Gate (independently from Spill Gate (independently from trigger conditions) trigger conditions)


Par

t. T

rig

ger

Par

t. T

rg R

eq.

GV

A1

GV

A2

GV

A3

CKOVA/B

Clo

ck 1

MH

zT

OF

0

Cumulative, average and Last Spill Available

Scalar HistogramsScalar Histograms



Front End ElectronicsFront End Electronics

CKOVCKOV It has been recognized that CKOV FEE should sustain a much higher

instantaneous rate than other detectors (no segmentation) Shaper + 100 MHz fADC not appropriate New 500 MHz fADC have been ordered and is at RAL. Will be installed this

week. There will be no more TDC data for CKOV

TOFTOF TOF TDCs are not properly synchronized. Internal clock has to be distributed.

For the moment, we use the common Part. Trigger signal in ch0 of each TDC

TOF1: Electronics is hand TOF2: We miss some electronics

Shapers: In production; expected for December 2008 TDC: One board missing FADC: 3 boards missing

SWSW Was discussed in PID session


FEE IssuesFEE Issues

Cross Talk IssueCross Talk Issue The Splitters introduce cross talk between TOF channels Splitter prototype did show this effect We understand this is caused by the additional grounding plane

we have added to suppress pick-up noise We need to understand the effect on TOF and CKOV

performances (KL is not affected) New design is under study

FADC firmware upgradeFADC firmware upgrade Needed to allow significant reduction of data volume

Less samples per Particle event (currently 512 whereas only 60 are necessary Zero suppression (to be tested)

Delicate operation

MICE CM June 08 Jean-Sébastien Graulich Slide 24

Schedule MilestonesSchedule Milestones From CM21From CM21 DAQ reviewDAQ review January 2008January 2008

Joined review with the Software Project

DAQ Trigger ImplementationDAQ Trigger Implementation Passed in JulyPassed in July Upgrade Depending on TrackerDepending on Tracker

Particle Trigger ImplementationParticle Trigger Implementation Passed in July Passed in July Upgrade Depending on TOF1Depending on TOF1

Shipment of remaining LDC PCsShipment of remaining LDC PCs 11stst half in July half in July Second half NovemberNovember

Standalone DATE readout for tracker in R8Standalone DATE readout for tracker in R8 Really Online MonitoringReally Online Monitoring Passed in July Passed in July Scalars in DAQ readout Scalars in DAQ readout Passed in July Passed in July TOF0 & KL readoutTOF0 & KL readout Passed in July Passed in July Upgrade of fADC firmwareUpgrade of fADC firmware July 15July 15 CAM data in Online Data StreamCAM data in Online Data Stream July 31July 31 Burst Gate Signal in MLCRBurst Gate Signal in MLCR was August 1 was August 1 Passed in Sept 15Passed in Sept 15 TOF1 readoutTOF1 readout Depending on TOF1Depending on TOF1 TDC repairTDC repair Passed in JulyPassed in July


Schedule MilestonesSchedule Milestones

New MilestonesNew Milestones DAQ reviewDAQ review December December

20092009 Upgrade of fADC firmwareUpgrade of fADC firmware November 4November 4 CAM data in Online Data StreamCAM data in Online Data Stream PostponedPostponed DAQ migration to the DAQ/Control networkDAQ migration to the DAQ/Control network October 30October 30 Target DAQ included in Detector DAQTarget DAQ included in Detector DAQ November 4November 4 Tracker integrated in DAQTracker integrated in DAQ ?? Tracker integrated in Online MonitoringTracker integrated in Online Monitoring ?? TOF2 Shaper ProductionTOF2 Shaper Production Started – Dec Started – Dec

1515 TOF TDC Clock SynchronizationTOF TDC Clock Synchronization December 10December 10 TOF1 in trigger systemTOF1 in trigger system December 10December 10 Burst Gate Signal in the Trigger SystemBurst Gate Signal in the Trigger System December 13December 13 Approval of SW/EMR Front End ElectronicsApproval of SW/EMR Front End Electronics Early Early

NovemberNovember Production of SW/EMR Front End ElectronicsProduction of SW/EMR Front End Electronics ? June 2009 ? ? June 2009 ? Installation of the Online Reconstruction FarmInstallation of the Online Reconstruction Farm November-November-

DecemberDecember


SummarySummary

DAQ and Trigger system have been successfully DAQ and Trigger system have been successfully commissionedcommissioned

The system is still in constant evolution User Instructions Documentation is available and up to date

Online Monitoring is operational and has been Online Monitoring is operational and has been used for early analysisused for early analysis

Efforts moving towards online reconstruction

Target DAQ will be integrated to Detector DAQTarget DAQ will be integrated to Detector DAQ Work in progress

FEE for SW/EMR is now a priority taskFEE for SW/EMR is now a priority task

detector daq and trigger status

Documents

jeansebastien graulichslide

data particle

data unpacking

jeansebastien graulichcm22

data sourcecm22

evolvinginteresting

target daq planmilestones

target daqprogress