MVD slow control and DAQ status

20/06/02 MVD SC and DAQ status 1

MVD slow control and DAQ status

Slow control Shift operation DAQ and Trigger status Software Conclusions

Items highlighted are known problems and where changes are planned.


Slow control sub-system status since last meeting Detector bias voltage

OK .. 412 channels, 30 modules, 4 crates .. 1 channel failed, module replaced.

Hybrid low voltage OK .. 206 channels, 48 modules, 6 crates ..

Hybrid temperature sensors OK .. 96 channels, 3 cards ..

Patch box power supply OK .. Alberto‘s summer student will program Torino PS >1/7/02

Auxilliary VME helix driver power supply OK ..

Interlock SPS OK ..

BBL3 interface OK ..


Slow control sub-system status since last meeting Radmon diode bias voltage

OK .. 16 channels, 1 module .. Spontaneous tripping of channels on power on after single or multiple channel trips. Needs investigating, but safe as shiftcrew notified through SCO.

Hybrid cooling OK .. Failed compressor replaced 9/4/02. Freon leaks finally fixed 15/05/02. 150W heater installed to stablelize no load switching. Hybrid load ca. 1kW.

Laser alignment Laser control VME CPU now network booted like all other VME machines. ZEUS shiftcrew RCO controlled laser runs now available. DDL definitions in latest software release. Safety Interlock to prevent laser operation during access not yet connected.


Injection diasabled + MVD off

Shift operation

MVD SC software & BBL3 interface & MVD hardware interlock If no SC (deadmans handle) or MVD on then HERA inj. disabled If cooling off then hv and lv off If lv not fully on then patchbox power supply off If SC not in correct state then GFLT trigger disabled

Lumi in + MVD standbyInjection diasabled + MVD on

Injection enabled + MVD standbyInjection diasabled + MVD on

Physics Calibration


Shift operation

MVD SC states MVD off = cooling off MVD standby = cooling on & hv and lv off MVD on = cooling on & hv and lv on

MVD SC transitions started by RCO, MVD RC or BBL3, but If ON requested and HERA inj enabled then SC waits for inj disabled before

starting transition without additional request If ON or in transition and HERA inj is disabled then SC sets MVD standby

RCO calibration runs: time, SC requirements, runtype, trgtype Pedestal, 10 mins, MVD on, DAQRUN, MVD_PEDESTAL Test pulse, 15 mins, MVD on, DAQRUN, MVD_TEST_PULSE_SCAN Laser, < 3 mins, none, DAQRUN, MVD_TRG_LASER 3 point IV curve, 10 mins, MVD on, DAQRUN, MVD_TRG_IV

MVD operator calibration runs Full IV, 40 mins, MVD on Timing, N mins, MVD on

Now possible to specify what the shiftcrew has to do for us, if documented


DAQ and Trigger status

DAQ front-end systems and software running reliably Front end Problems

Problems seen with specific helix and token readout chains. More details in DQM section. More sytstematic approach to the problem required: classification of, solutions to, etc.

MVD RC known problems Transition fails, 1-2 a week, as process death not caught by daemon on Lynxos.

Fix made does not work correctly needs checking. Soln. Needs expert. MVD BOR not received , 1 in 20 runs, by EVB. Soln. ABORT and retry. CTD SLT trigger handshake fails 1-2 per week. Soln. ABORT and cold start CTD.

Trigger status STT SLT integrated at the hardware level. Handshake works and data seen. Severe latency problems seen in Physics runs due massive data sizes


DAQ and Trigger status Look at two ep luminosity runs, 41184 and 41188, from 21/6/02 with

Ie 4 mA, Ip 20 mA, CTD on full voltage, and STD_020621_2_HIGH

MVD standard setup plus 41184 strip data not transferred to EVB on GSLT accept + cluster threshold 64 41188 strip data transferred to EVB on GSLT accept + cluster threshold 32

Measure


DAQ and Trigger status run 41188

MVD crate 0, CTD SLT and STT data: Top row latency of readout finished Bottom row size in kB



CTD, STT, GTT cluster+decision, MVD strip, and to EVB: Top row data size in kB – log10 plot Bottom row data size of last 250 events



Data sent to GTT, gslt accept received, and data sent to EVB: Top row latency in ms per event Bottom row latency for last 250 events



data



MVD crate 0, CTD SLT and STT data: Top row latency of readout finished Bottom row size in kB



CTD, STT, GTT cluster+decision, MVD strip, and to EVB: Top row data size in kB – log10 plot Bottom row data size of last 250 events



Data sent to GTT, gslt accept received, and data sent to EVB: Top row latency in ms per event Bottom row latency for last 250 events


DAQ and Trigger status Observation

Data size Size of MVD cluster data, per crate, to big 20kB (design 2-3 kB) Size of MVD strip data, per crate, to big 25kB (design ca. 5 kB) Size of CTD SLT data hits cutoff at 13 kB (design 4-5 kB) Size of STT SLT data OK but detector was off. (design 4-5 kB)

Latency MVD cluster readout latency is acceptable at 1-2 ms CTD SLT latency big 6-7 ms due to large data size STT SLT latency is OK 1ms as detector off GSLT decision latency unacceptable >80 ms (design was not to be worse than existing CTD

latency) EVB event data latency bad >80 ms (design < 50 ms)

Conclusion Latency is too large and driven by the unacceptably large data sizes. Reducing it

artificially (remove strip data) moves it in right direction. The backgound problem must be resolved. Even options like using the GTT for CTD

and STT SLT processing without the MVD are not currently possible.


Software changes planned

Message definition changed see http://mvddaq.desy.de

Field inserted into message jacket requires update, recompile, software SC updated 1/6/02 DAQ will be updated, and not available, during access 2-3/7/02

Multi-threaded message hub now available from A.Ivanov Running on SC since 7/6/02, some bugs found and fixed Install in DAQ system during access 2-3/7/02 Should solve process hangups and lockouts Software also used by C5

Green new version Improved functionality, ie clearing remote histograms etc. Should be more responsive, receives on histograms look at rather than all Install for DAQ 2-3/7/02, needs new message definitions


Conclusions

Finish, document, technical publication and head for the hills.

Documents

MVD slow control and DAQ status