Online task list for 2011
Contents
- 1 FY2011 Activity Schedule for Online Computing
- 2 Descriptions of Scheduled Activities
- 2.1 Plan Front-End Software
- 2.2 Plan DAQ Software Event Unblocking
- 2.3 Plan DAQ Software Scripts
- 2.4 Plan DAQ Software Run Control
- 2.5 Plan DAQ Software Code Management
- 2.6 Plan Monitoring Framework
- 2.7 Plan Monitoring Scalers
- 2.8 Plan Monitoring Histograms
- 2.9 Plan Monitoring Remote
- 2.10 Plan Monitoring Hardware Status
- 2.11 Plan Monitoring Process Status
- 2.12 Plan Monitoring Trigger
- 2.13 Plan Alarm Sys
- 2.14 Plan Archiving DAQ Configuration
- 2.15 Plan Archiving Run Info
- 2.16 Plan Archiving Controls
- 2.17 Plan Event Display
- 2.18 Plan Storage Mngmnt
- 2.19 Plan Experiment Controls Framework
- 2.20 Plan Experiment Controls Display management
- 2.21 Plan Experiment Controls Backup/Restore
- 2.22 Plan Experiment Controls Magnet PS
- 2.23 Plan Experiment Controls HV
- 2.24 Plan Experiment Controls LV
- 2.25 Plan Experiment Controls Motors
- 2.26 Plan Experiment Controls Gas Systems
- 2.27 Plan Experiment Controls Temperature
- 2.28 Plan Experiment Controls Target
- 2.29 Plan Experiment Controls Interface with DAQ
FY2011 Activity Schedule for Online Computing
The table below contains activities from the 12GeV project schedule in the Online Computing section which have work scheduled for FY2011. Detailed descriptions for the activities are kept at the bottom of the page and can be jumped to by clicking the short description in the table.
A breakdown of each activity into smaller tasks is maintained in an Excel file on the group disk here:
/group/halld/Individual-Schedules/Online_Computing
| Activity Line | Activity Name | Man-weeks | Names of people | Comments |
|---|---|---|---|---|
| 1532025 | Plan Front-End Software | 16.5 | D. Lawrence, D. Abbott, B. Moffit | |
| 1532030 | Plan DAQ Software Event Unblocking | 9 | D. Lawrence, D. Abbott, B. Moffit | |
| 1532030a | Plan DAQ Software Scripts | 6 | ||
| 1532030b | Plan DAQ Run Control | 5 | ? + V. Gyurjyan | Mostly Vardan |
| 1532030c | Plan DAQ Code Management | 4 | ||
| 1532035 | Plan Monitoring Framework | 6 | ? + V. Gyurjyan | |
| 1532035a | Plan Monitoring Scalers | 3 | ||
| 1532035b | Plan Monitoring Histograms | 4 | D. Lawrence | |
| 1532035c | Plan Remote Monitoring | 3 | ? + V. Gyurjyan | |
| 1532035d | Plan Monitoring Hardware | 4 | ? + V. Gyurjyan | |
| 1532035f | Plan Monitoring Processes | 3 | ? + V. Gyurjyan | |
| 1532035g | Plan Monitoring Trigger | 2 | S. Somov + V. Gyurjyan | |
| 1532040 | Plan Alarm Systems | 6 | Universities are expected to contribute more | |
| 1532045 | Plan Archiving DAQ Configuration | 3 | ||
| 1532045a | Plan Archiving Run Info | 5 | ||
| 1532045b | Plan Archiving Controls | 5 | ||
| 1532050 | Plan Event Display | 2 | Universities are expected to contribute more | |
| 1532055 | Plan Storage Management | 11.3 | Computer Center can help | |
| 1532060 | Plan Controls Framework | 4 | ? + V. Gyurjyan | |
| 1532060a | Plan Display Management | 3 | ||
| 1532060b | Plan Controls Backup/Restore | 3 | ||
| 1532060c | Plan Controls Magnet PS | 4 | ||
| 1532060d | Plan Controls HV | 3 | ||
| 1532060f | Plan Controls LV | 4 | ||
| 1532060g | Plan Controls Motors | 4 | ||
| 1532060h | Plan Controls Gas Systems | 4 | ||
| 1532060j | Plan Controls Temperature | 4 | ||
| 1532060k | Plan Controls Target | 5 | ||
| 1532060n | Plan Controls/DAQ interface | 3 | ? + V. Gyurjyan | Mostly Vardan |
| 1532065 | Trigger Board Initialization | 27 | S. Somov + Electronics Group | Two-year duration |
| 1532035 | Level 1 Verification | 24 | S. Somov + Electronics Group | Two-year+ duration |
Descriptions of Scheduled Activities
Plan Front-End Software
This will plan the Hall-D specific details of configuring and maintaining the software used in the front-end electronics in the hall. This includes where the CODA 3 configurations will be kept (disk resident XML files, database, ...?), and how we will revert to previous configurations or implement new ones.
This will also include plans for how the translation table needed for the offline will be interfaced with the online. Specifically, if the DAQ system detects module types automatically, how/where it will record these for use in parsing by both the online monitoring system and the offline systems.
Because the online systems can be very sensitive to configuration details, access to changes should probably limited to certain individuals. This plan should address how access to deployed system configurations will be limited to ensure integrity of the DAQ system.
Plan DAQ Software Event Unblocking
In production running the events will arrive entangled meaning all of the fragments of a single event will not appear in a single, contiguous memory section. Rather, the fragments will be mixed with fragments from other events and must be disentangled (or unblocked) to get a single event that may be analyzed. This will have to be done for monitoring as well as for L3 event filtering where the ability to save or discard a single event will be required.
This activity will provide a plan for how and where the events will be disentangled (EB, L3/monitoring farm, offline code base, ...?) This will include how the single events will be passed on to the CODA 3 Event Recorder for writing to disk/tape.
Estimates of CPU/memory/bandwidth resources required will be included so they may be added into the overall requirements for the Hall-D online computing resources.
