Second Installation and Commissioning Workshop DAQ and ECS FMD contribution

1
Second Installation and Commissioning
WorkshopDAQ and ECSFMD contribution

• Børge S. Nielsen, Niels Bohr Institute
• with invaluable contributions from
• C. Holm, K. Gulbrandsen, G. Renault and F.
  Roukoutakis
• 11 December 2006

2
Status of FMD readout
Test setup at NBI
DAQ computer
RCU
Inner and Outer Digitizer
VME crate for TTC and LTU
Chain working 2 digitizers, RCU, DDL, DATE To be
done TTC and LTU -- hardware is available
at NBI
3
Read-out cable problem solved
Unable to read out Digitizers to RCU with 3-4 m
standard cable Standard cable flat cable, 50
connections, 1 mm pitch New cable flat
twisted pairs, 40 pairs, 0.635 mm pitch
40 bit signal 10 grounds
40 bit signal 40 grounds
adaptor
Have tried this with all sorts of shielding,
termination etc, without success
This works up to at least 4 m cable
4
FMD specifics to remember

• DAQ readout using 3 standard RCUs
• Digitizer card (FMDD) is a modified TPC FEC
• DCS uses CAEN power supplies
• and interface to RCU-DCS card identical to TPC
• Receive L0, L1, L2 from LTU
• but we do not deliver trigger signal to CTP
• Will require ped. and gain calibration runs

5
DAQ Pre-commissioning (1)

• Installation of DAQ system for pre-commissioning
• PC installed with Linux and DATE V5 in home
  institute ? YesLinux SLC3/SLC4 ? DATE Version ?
  SLC3, DATE 5.14
• DDL SIU, RORC, and LTU modules available in home
  institute ? YesActel-based SIU ? RORC Version 4
  ? Don't know, RORC sw 4.4.4
• Final readout electronics data formatting
• Generation of the Common Data Header (CDH) with
  information from the trigger ? Presumably yes,
  but not tested (using RCU).

6
DAQ Pre-commissioning (1)

• Final electronics readout demonstrated via DDL
  DATE with final TRG/DAQ system
• Final readout electronics ? Yes
  (FMDDRCUSIUDIURORC)
• Configuration of electronics via DDL if used ?
• Will use for peds. Not tested.
• Trigger with LTU TTC system ? No.
• Detector busy to LTU ? yes. Not tested
• Readout with DDL DATE system ? Yes
• Raw data with CDH info from Trigger ? yes, not
  tested.
• CDH checking enabled in DATE ? No.
• Trigger busy and DDL XON/OFF have been exercised
  ?
• don't know what this is.
• Test performed with more than 1 DDL ? No

7
DAQ Pre-commissioning (2)

• Data Quality Monitoring (DQM)
• Raw data decoding code ready ? Almost
• Same code as in AliROOT ? Simplified version
• MOOD module written to display raw data ? In
  progress
• Metrics for automatic DQM ? Not yet
• Detector algorithm (DA)
• Online calibration procedures identified and
  specified ?
• Yes (peds. and gains).(Including
  information as required in the DA framework
  document)
• No
• Implementation of the procedures using the DA
  framework ?
• Not yet
• RAW data files ready to test them ? No

8
DAQ Pre-commissioning (2)

• Performance test in the lab
• Max bw of readout electronics over DDL ? Not
  measured.
• Max event rate ? 1kHz, apparently limited by
  RCU event buffer
• (internal limit is Digitizer-gtRCU serial readout
  1-3 kHz event rate)
• Range of event size ? 25 120kB
• Dead-time at nominal rate ? 1ms
• Stability (Full chain used since when ? Summer
  2006
• Stable run during several hours? Yes, even
  days.)
• Start Of Data (SOD), End Of Data (EOD) handling
• Readout electronics ready to receive software
  triggers ? ??
• Readout electronics able to generate SOD and EOD
  events fragments ? ??
• Definition of Equipment identification
• Detector identifier has been defined by offline.
  We think so
• DDL index (mapping of DDL to readout partition)
  defined by detector ? Not sure.

9
FMD FSM
Node
DCS FMD
CU
DU
details
HV
LV
RCU
RCU
HV A1512
LV A3009
0-3
0-5
Channel
Channel
Channel
Channel
Channel
Channel
6 bd x 12 ch 72 ch
4 bd x 12 ch 48 ch
10
ECS Pre-commissioning

• Detector DCS
• Top-level DCS Finite State Machines (FSM) defined
  and implemented ?
• CAEN LV and HV progressing well
• RCU Not yet
• Standard set of STATES and COMMANDS ? Yes
• Front-end and readout electronics integration
  with the Trigger
• Raw data generation controlled by LTU ? ??
• Need to control detector-specific LTU sequences ?
  Maybe for gain calibration?
• Detector readout with DAQ system based on
  DDLDATE ? Yes
• Sequences of operation (pedestal runs,
  calibration runs, etc) to be controlled by the
  ECS
• Sequences defined and communicated to the ECS
  team ? More or less
• Detector-dependent programs to implement the
  above sequences
• Programs defined ? Yes
• Programs developed and tested ? No

11
Detector installation commissioning

• Check location of DDL SIUs and optical patch
  panels
• Detector installation
• When ? 19 March 2007 (FMD3)
• Will the detector DAQ contact be present during
  commissioning ? Yes
• DAQ ECS needed during commissioning
• When ? February 2007 in clean room
• Operation from upstairs starting on ? In clean
  room Feb 2007
• In P2 early March

12
DCS questions

• DCS status today

Yes
Yes
Yes
lt Feb 07
Yes
Yes
Yes
lt Feb 07
ROOT panels
InterCom
No

• DCS needs at clean room P2 for pre- and final
  installation

Feb 07
Quartus needed
Yep.
ditto
Feb 07
YES !!
Feb 07
13
Questions for Detectors providing Trigger Inputs

• FMD does not provide trigger inputs to CTP

14
Detector Readout I

• Does the detector respond correctly to trigger
  sequences with errors?
• Has this been checked using the list of sample
  error-sequences
• Not explicitly, but we are using standard RCU
• Can the detector operate continuously with a high
  rate of triggers (i.e. up to a raw rate of 40
  MHz, however respecting BUSY) without
  generating errors? Using standard RCU
• Does the detector transfer L1 and L2a messages in
  an appropriate way to the event header?
• Using standard RCU
• Can the detector, using an LTU, maintain stable
  running conditions for a period of at least 12
  hours. (i.e. more than the longest run.)
• We haven't had an LTU running yet.

15
Detector Readout I

• Some detectors require calibration triggers.
  These require a message to be sent to the CTP via
  a DIM server giving the details of the request.
  The details of the exact format for the request
  have not yet been released. However, does the
  detector foresee from where (which computer) the
  requests will be sent? Such a computer must be
  able to communicate with the CTP, which implies
  access to the DCS network. If the calibration
  trigger requires a pre-pulse, does the detector
  delay the pulse as required, e.g. by use of the
  TTCvi?
• We think this is not relevant
• Some detectors have expressed an interest in
  using the Region-of-Interest (RoI)
• We will not do RoI's
• Can the detector drive the required LVDS signals
  over a distance equivalent to that for the cables
  connecting it to the CTP and maintain an
  acceptable BER (say lt10-11)?
• Yes, but we only return BUSY, not trigger
  signals

16
Detector Readout 2 (Reminders)

• Can the detector make adequate individual
  adjustments to each final destination so as to
  obtain required time alignments for L0 and L1
  output signals?
• If we understand the question, the answer is
  Yes.
• Does the detector provide its own counters for
  all signals coming from the trigger system (i.e.
  L0, L1, L2a, L2r, BUSY) and in addition for any
  trigger inputs sent to the CTP?
• Yes

17
Conclusions

• Lots of progress with FMD detector hardware
• (final assembly to start imminently)
• Electronics and read-out problems solved
• (relating to Digitizer boards and cables)
• DAQ and DCS under control - more work needed
• (still worried about CAEN deliveries)
• Still need to test with LTU and TTC
• Planning 1 month testing in Silicon Facility
  clean room
• (February 2007)
• Very short installation period with testing in
  P2
• We need cables in P2 !!