RCC-DAQ/EF Interface Requirements

Draft 0.2

11 November 1998

J.C.Hill (hill@hep.phy.cam.ac.uk)

This is a VERY preliminary document.

Introduction

Requirements

1. RCC requires read/write access to the Calibration database.

   When a calibration is done, the events will stop at the ROD - hence the calibration information has to be removed from the ROD by the RCC and written into the calibration database.

2. RCC will communicate error counts/flags to status display and/or Run Control.

   Error counts and/or flags will be stored in RODs. RCC will need to be able to send this error information to the appropriate location - the status display in cases where errors are less critical but need flagging to the operator, and Run Control where immediate action is needed.

3. RCC will receive Run Control Instructions that pertain to RODs and TIM.

   Though I say "will" here, this is not yet written in tablets of stone. My own view is that will it prove to be a necessary requirement. Many Fast Commands will be sent via the TTC, and it may be that the RCC is not involved during normal running in handling Run Control instructions and acting on them. However, the RCC needs to know the run state at least (see requirment 4 for example). Note that this section has been rewritten after a more careful study of the Trigger/DAQ Interface document.

4. RCC needs read/write access to the configuration database.

   The configuration database will contain setup details for the RODs and TIM (eg. if an input channel should be disabled). Certainly in local running the RCC will have to read this database and set up the RODs appropriately. It will also have to update the database, eg. if a channel goes bad and has to be disabled during a run. I also see this functionality being required in global running.

5. Summary histograms on RCC sent to higher level.

   The whole of the histogram space is too large to be systematically made available. However, summaries will be generated on the RCC for routine monitoring, and these will be passed up to higher levels for overall SCT monitoring, and for the operator for checking for gross errors.