Difference between revisions of "May 2008 Subsystem Review"
m |
m |
||
| Line 19: | Line 19: | ||
| − | The scope of this review includes all aspects of the following Hall D systems and efforts: electronics, trigger, DAQ, event and hardware monitoring, experiment and detector controls, and detector integration, | + | The scope of this review includes all aspects of the following Hall D systems and efforts: electronics, trigger, DAQ, event and hardware monitoring, experiment and detector controls, and detector infrastructure, integration, installation, and maintenance. Performance requirements, development and construction schedules, costs, and ES&H issues may be reviewed for all systems, as well as any other considerations that may influence the construction and operation of the Hall D detector. |
In addition, for electronics systems the scope may include functional design, technology choice, fabrication considerations, testing and quality control, maintainability, and long-term viability. For computing systems the scope may include computing architecture, network design, data flow issues, protocol choices, and network and computing hardware choices. For software the scope may include functional design, complexity, coding and language concerns, testing and quality control, commissioning, operational concerns, and long-term maintainability. For hardware the scope may include design philosophy, material selection, fabrication choices, levels of redundancy, commissioning procedures, costs for materials and labor, quality control, and operational reliability and longevity. | In addition, for electronics systems the scope may include functional design, technology choice, fabrication considerations, testing and quality control, maintainability, and long-term viability. For computing systems the scope may include computing architecture, network design, data flow issues, protocol choices, and network and computing hardware choices. For software the scope may include functional design, complexity, coding and language concerns, testing and quality control, commissioning, operational concerns, and long-term maintainability. For hardware the scope may include design philosophy, material selection, fabrication choices, levels of redundancy, commissioning procedures, costs for materials and labor, quality control, and operational reliability and longevity. | ||
Revision as of 11:02, 21 March 2008
Contents
Introduction
The May 2008 Hall D Subsystem Review will cover all aspects of Hall D that have not been reviewed previously under the auspices of the 12 GeV project office. This includes electronics, trigger, DAQ, event and hardware monitoring, experiment and hardware controls, and detector integration, assembly, and maintainability. Milestones for the electronics/trigger/DAQ/monitoring/controls part of the review can be found in Online Major Milestones.
An open question is how to structure the review, and how long to make it. The review actually covers two quite distinct aspects of Hall D, electronics/trigger/DAQ/monitoring/controls and infrastructure/installation/maintenance. Normally these would each have their own review, as experts in one field probably know little about the other, but time is running out before the CD-3 review this summer.
Options include:
- joint review with serial presentations
- joint review with parallel presentations
- two separate reviews the same week.
This needs to be resolved ASAP!
Charge for the Review Committee
No charge for the committee has been established yet (Mar 2008). A potential charge, based on charges from previous reviews, might be:
The scope of this review includes all aspects of the following Hall D systems and efforts: electronics, trigger, DAQ, event and hardware monitoring, experiment and detector controls, and detector infrastructure, integration, installation, and maintenance. Performance requirements, development and construction schedules, costs, and ES&H issues may be reviewed for all systems, as well as any other considerations that may influence the construction and operation of the Hall D detector.
In addition, for electronics systems the scope may include functional design, technology choice, fabrication considerations, testing and quality control, maintainability, and long-term viability. For computing systems the scope may include computing architecture, network design, data flow issues, protocol choices, and network and computing hardware choices. For software the scope may include functional design, complexity, coding and language concerns, testing and quality control, commissioning, operational concerns, and long-term maintainability. For hardware the scope may include design philosophy, material selection, fabrication choices, levels of redundancy, commissioning procedures, costs for materials and labor, quality control, and operational reliability and longevity.
You are asked to address the following questions:
1. Are the technical performance requirements adequate, appropriate, and complete for each system?
2. Do the current designs and plans appear likely to achieve the performance specifications with a low risk of cost increases, schedule delays, and performance problems? Are there opportunities for improvements in cost or performance that the design teams should consider?
3. Are the R&D efforts appropriate, complete, and likely to reduce risks?
4. Have ES&H considerations been adequately incorporated into the designs and plans?
Agenda
Possible agenda topics and speakers, assuming the standard 1 1/2 day time frame:
- Describe review process and committee charge - Allison or Rolf
- Intro to 12 GeV project - Allison or Rolf
- Intro to Hall D physics and detector - Elliott or Elke or Elton or ???
- Front-end electronics - Fernando
- Trigger - Dave D
- DAQ - Graham or Dave A
- Controls and monitoring - Elliott
- Infrastructure, installation, assembly, maintenance - Tim et al.
- Safety engineering - Tim et al.
Preparation
Below I list topics the review committee might focus on. Clearly the committee cannot investigate all of these in depth, but we can expect they will want an overview of most of them, and may probe a few in depth.
Electronics
- preamps
- discriminators
- F1TDC, FADC250, FADC125
- CTP, SSP, GTP
- TI, TS, TF, TD
- cable choices
- HV systems
- LV systems
- C-W and other bases
- SiPM's and other PMT's
- crate and backplane choices (VXS, ATCA)
- development and test strategies
- etc.
Trigger
- L1 algorithm
- rates and backgrounds
- crate sum + global sum strategy
- overall trigger strategy
- crate and hardware choices
- trigger distribution strategy
DAQ
- event size
- data rate
- computer hardware choices
- network hardware choices and configuration
- cpu and network utilization
- software architecture
- software components (ROC, EMU, ER, etc)
- language choices
- run control
- farm architecture
- event tranfer to silo
- metadata recording
Event and Hardware Monitoring
- event display
- event monitoring system
- alarm system
- archive/display system
Experiment and Detector Controls
- overall controls architecture (ECS/SCADA/DCS hierarchy)
- DCS strategy (PLC usage, control loops, etc)
- SCADA strategy (tentatively EPICS + perhaps MonAlisa)
- ECS strategy (AFECS)
- alarm system
- archive/restore system
- magnet and cryo control systems
- interoperability with accelerator controls system
- redundancy, failure modes, safety issues
Detector Integration
- tolerances, keep-away zones
- cable strategy and layout
- crate layout
- power, heat, cooling
- grounding/shielding/EMC
- mechanical drawing database
- sign-off procedures
Detector Construction
- strategy
- assembly procedures
- special tooling and equipment needed
- personnel and equipment safety, other EH&S, etc.
Detector Maintenance
- ease and expected frequency of access
- access/disassembly/reassembly procedures
- routine maintenance
- expected component lifetimes
- personnel and equipment safety, other EH&S, etc.
