Difference between revisions of "35t Test"
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
= Run Modes (per DocDB 9677) = | = Run Modes (per DocDB 9677) = | ||
{| class="wikitable" width="100%" | {| class="wikitable" width="100%" | ||
| − | |1||Continuous main DAQ mode||Similar to final 'triggerless' far detector running mode, i.e. parallel trigger farm looks for nice muons in real time. Needs ZS of TPC d | + | !No. |
| + | !Mode | ||
| + | !Comment | ||
| + | |1||Continuous main DAQ mode||Similar to final 'triggerless' far detector running mode, i.e. parallel trigger farm looks for nice muons in real time. | ||
| + | Needs ZS of TPC d | ||
data to work | data to work | ||
|- | |- | ||
Revision as of 20:07, 9 October 2014
Recent documents
- DocDB 9677, Proposed Run Modes for the 35t test
- DocDB 9785, Report from RCE-Backend Mini-workshop
- DocDB 9591, 35t Phase-II Testing for August Readiness Review
- DocDB 9823, summary for plans in mid-Fall 2014
Run Modes (per DocDB 9677)
| No. | Mode | Comment | 1 | Continuous main DAQ mode | Similar to final 'triggerless' far detector running mode, i.e. parallel trigger farm looks for nice muons in real time.
Needs ZS of TPC d data to work |
|---|---|---|---|---|---|
| 2 | Continuous main DAQ mode | Similar to final 'triggerless' far detector running mode, i.e. parallel trigger farm looks for nice muons in real time. Needs ZS of TPC d
data to work |
Issues that need to be clarified
- Purposes and architecture of the proposed online farm
- Design of the metadata
- Handling TPC stream data within the framework which is trigger-oriented, issues of timing and multiple interaction in temporally close slices
- Possible necessity to duplicate parts of raw data to create overlaps, in order to make practical operation of the online farm
