DaqMeetingJune2005ActionList

Available test systems

Short-term test systems

• Barrel5 - the afternoon and evening were spent testing the DAQ code on 24 modules on B5 (R4-updated). There is unlikely to be very much time for DAQ testing on B5 at SR1.
• There may also be an opportunity to test the DAQ on Barrel4 at Oxford if the mounting and testing goes quickly.

BarrelSector

The BarrelSector? needs a refurbished cooling loop, harnesses, and a selection of modules, including those with known problems taken off other barrels

• This requires:
  • Harnesses to come from Taiwan and/or repaired.
  • Someone (from RAL?) to do the repairs to the services
  • Oxford to maintain the correct robot + cooling, and 24 module testing ability
  • Brackets, screws, clips etc.
• Module mounting only to proceed after Barrel4 is completed
• Host institution tbd.
• Time-scale - target of end of August for fully populated sector

Janet Carter to coordinate this effort.

Spare Disk

• The endcap may encounter different problems, and so a separate endcap test system is desirable
• NIKHEF should make a spare disk, but not until after 9-disks are assembled
• time-scale - April 2006?

DAQ development effort

TDAQ

1. Chris will arrange with Dave and CERN experts to go to CERN as soon as possible to sort out:
   1. first the xml files for the new TDAQ release (-01-01)
   2. then the RodCrateDaq? implications

Error Counting

1. Alan to find out from Trevor what the pixel code does with errors
2. Peter and Alan to define what behaviour we actually want (dont re-send trigger?)
3. Alan to find out from Trevor timescale for implimenting changes

Redundancy

JohnHill? to:

1. ensure that y-junction in the Barrel TX fibres follow the redundancy loops
2. find out if there are particular endcap modules which need to be run in select 1 and so would benefit from a particular ROD mapping

1. Off-Rod redundancy
   1. "Written but not tested" - says Bruce
   2. Later in the day Bruce made some further changes to how this is handled in R4-updated at Oxford.
   3. Alan is to merge this into HEAD (done), and to fix for sendABCDModule (singular) and modifyABCDVarROD (single module)
   4. proper testing requires fix of SynchTrigs? (done)

1. Off-crate rudundancy
   1. Nothing exists yet.

Scan Options

1. Alan to add missing scan options to analysis stream (done AJB)
2. A more flexible system of tests is eventually desirable (progress made, AJB)

Other requirements for cosmics running

1. JohnHill? to work out if and what work needs to be done on the trigger chain.
2. Timing in. Full-mode histogramming needs to be tested - no name against this
   1. BJG SctApi and DSP code should work (did as of Feb 04)
   2. BJG Probably good idea to try and see what breaks
   3. BJG Scan option to analysis stream would help things
3. Passive histogramming setup for passive histogramming needs to be checked. no name against this

Other

• Multi-crate - further development to be driven by user's debugging requests
• Database issues were not discussed

• Dave to add pin current to GUI DCS display.

SynchTriggerNoiseDebugging