Many-module "test" system(s)
- Short-term:
- B5@Oxford
- B5@SR1
- Disk?
- Intermediate + long term:
- What scale of system do we want/need. What is possible?
- Intermediate:
- Barrel sector? Refurbished?
- Longer term:
- spare disk?
- Questions of
- module availability, harness availability
- cooling, power supplies
- host location, operational effort etc.
DAQ priority list
The following are not in order of priority, but are somewhere on the list:
- TDAQ issues, esp xml files
- RodCrateDaq? issues - what do we actually need to do?
- Multi-crate (still todo?) suitable for test with B5@CERN?
- Off-rod redundancy status
- Off-crate redundancy
- SctRodDaq Test programs for DSP programmers
- Extra information for tests (options like "Synch")
- Dual Triggers status
- Testing of existing DSP code with many modules (c and assemb)
- Error counting, reporting, reacting
- Applying testbeam changes for cosmics running?
- Data monitoring in cosmics/physics mode?
- Triggers for cosmic running?
- Extra information in TestData ("Synch")
- Bug: Raw/"Cooked" scan problem
- Bug: SynchTrigger?
- Database issues
- Configuration
- SctRodDaq data
Added during meeting
- Histogram 3 timebins for timing in
- passive histogramming for beam/cosmic running
- ability to run any test synchronously
- Timing in the opto electronics
- "Suspend and continue" (not abort)