dataesr/scientific-paragraphs-categorization huggingface dataset:
Quality assurance and quality control The QA and QC programs for the FD are based on our experience with the ProtoDUNE-SP. Our design-phase quality management system is based upon that experience. Following completion of the 60-percent design review, we will develop a quality final assurance program focused on final specifications and drawings, and developing a formal set of fabrication procedures along with detailed QC and test plans. During fabrication, integration into the detector, and detector installation into the cryostat, our QC plan will be carefully followed, including incoming materials and other inspection reports, fabrication travelers, and formal test result reports entered into the DUNE QA/QC database. Particular steps in this process are detailed below. -296 --296 --296 -.
For products with a disposition of accept, as is, or repair, the nonconformance documentation shall be submitted to the design authority for approval. All QC data (from assembly and pre-and post-installation into the APA) will be directly stored to the DUNE database for ready access of all QC data. Monthly summaries of key performance metrics (to be defined) will be generated and inspected to check for quality trends. Based on the ProtoDUNE-SP model, we expect to conduct the following production testing. Prior to shipping from assembly site: • dimensional checks of critical components and completed assemblies to insure satisfactory system interfaces; • post-assembly cryogenic checkouts of SiPM mounting PCBs (prior to assembly into PD modules); • module dimensional tolerances using go/no-go gauge set; and • warm scan of complete module using motor-driven LED scanner (or UV LED array).
Installation quality control PD system pre-installation testing will follow the model established for ProtoDUNE-SP. Prior to installation in the APA, the PD modules will undergo a warm scan in a scanner identical to the one at the PD module assembly facility and the results compared. In addition, the module will undergo a complete visual inspection for defects and a set of photographs of selected critical optical surfaces taken and entered into the QC record database. Following installation into the APA and cabling, an immediate check for electrical continuity to the SiPMs will be conducted. Following the mounting of the TPC CE and the PDs, the entire APA will undergo a cold system test in a gaseous argon cold box, similar to that performed during ProtoDUNE-SP. During this test, the PD system system will undergo a final integrated system check prior to installation, checking dark and LED-stimulated SiPM performance for all channels, checking for electrical interference with the cold electronics, and confirming compliance with the detector grounding scheme.
The neutron capture cross-section and the γ spectrum have been measured and characterized by the Argon Capture Experiment at DANCE (ACED), where DANCE is the Detector for Advanced Neutron Capture Experiments. Recently, the ACED collaboration performed a neutron capture experiment using DANCE at the Los Alamos Neutron Science Center (LANSCE). The result of neutron capture cross-section was published  [119]  and will be used to prepare a database for the neutron capture studies. The data analysis of the energy spectrum of correlated γ cascades from neutron captures is underway and will be published soon. The γ energy spectrum and the branching ratios in the ENDF library will be updated with the ACED result. Figure  6. 16 shows an example of the energy spectra of individual γ clusters measured by ACED  [119].
Energy calibration techniques and related software tools are also being developed at various experiments (MicroBooNE, ICARUS, LArIAT, ProtoDUNE) that involve estimating and propagating uncertainties like E field distortions, recombination, and other effects into physics signals. Other calibration related developments include DAQ and calibration database design, all of which are being improved at SBN and ProtoDUNE. -348 --348 --348 -.
Interfaces with other consortia Interfaces between calibration and other consortia have been identified and appropriate documents have been developed. The documents are currently maintained in the CERN Engineering and Equipment Data Management Service (EDMS) database, with a TDR snapshot kept in the DUNE document database (DocDB). DUNE document database (DocDB). A brief summary is provided in this section. Table  6. 4 lists the interfaces and corresponding DocDB document numbers. The main systems calibration has interfaces with are HV, PD system, and DAQ, and the important issues that must be considered are listed below. HV Evaluate the effect of the calibration hardware on the E field due to laser system periscopes and FC penetration. Evaluate the effect of the incident laser beam on the CPA material (Kapton); integrate the hardware of the photoelectron laser system (targets) and the LBLS (diodes) within the HV system components.
Calibration data volume estimates The calibration systems must interface with the DUNE DAQ system, discussed in detail in chapter 7. Trigger decisions for physics events are made hierarchically: trigger primitives are generated from TPC and PD system "hits", and these trigger primitives are then used to create trigger candidates which are collections of trigger primitives satisfying selection criteria such as exceeding a threshold number of adjacent collection wire hits, or total collection wire charge recorded, etc. These trigger candidates are passed on to a module level trigger (MLT) which then makes decisions about whether a given trigger candidate is accepted as a detector-wide trigger. If so, the MLT sends trigger commands to the data flow orchestrator (DFO) which in turn passes them to an available event builder (EB) that then requests data from the FE readout of the DAQ (servers that host FELIX -349 --349 --349 - APA APA alignment studies using laser and impact on calibrations DocDB 7048  [17]  Physics tools to study impact of calibrations on physics DocDB 6865  [123]  Software and Computing Calibration database design and maintenance DocDB 6868  [124]  TC Facility Significant interfaces at multiple levels DocDB 6829  [125]  TC Installation Significant interfaces at multiple levels DocDB 6847  [126]  cards).
It provides results on mis-configurations and potential problems on configuration alignment and dependencies between components. -403 --403 --403 - • Persistency Engine -This component provides a single and uniform serialization module, which is strictly followed by every DAQ component. Also responsible for configuration schema evolution and communication with the configuration database. The storage engine privileges will be only read and write operations, not allowing updates and removal of configurations. It also provides a redundant session layer for high-availability and load distribution. The configuration system will mainly consist of standard configuration management components, with a high emphasis on the audit system, in order to verify that the global configuration of the CCM complies with the detector, physics and operational requirements.
It also provides an implementation for the most common communication protocols for the database back ends (SQL, REST, etc. ). • Notification System -It is a rule-based system of scheduled and aimed notifications that occur in the case of state combinations. It defines soft and hard states of events and grace periods of alarms. • User Interfaces -Provides graphical and command line user interfaces for monitoring configuration management and visualization of metric data. Monitoring being a key requirement in the industry for computer clusters and their applications, the proposed solution is the adaptation of mature, robust, and open-source third party tools, with the extension of DUNE CCM specific interface implementations and configurations of these monitoring systems.
The network connection from this data room to the fiber trunks going up the shaft will also be made, as will preparations to receive the multi-mode fiber connections from the WIB to the FELIX cards housed in servers in these racks. There is space for 60 racks racks, with four set aside for other consortia, 12 per module for upstream DAQ electronics, and the remaining space for networking and other DAQ computing needs. An initial engineering design of the computer room is shown in figure  7. 23, which meets all requirements for capacity, cooling, safety and installation schedule.
New TPC Installation Concept -418 --418 --418 - -419 --419 --419 - Starting in Q3 2023, the data room will be ready for the installation of the DAQ servers servicing the first module described in section 7. 2. 1. 2. This will proceed over the next year, with servers being installed, cabled up, and tested. As much configuring and commissioning work as possible will be done over the network from the surface (or home institutions), to limit the number of people underground. Note that this data room is sized for all four modules of DAQ computing, so one quarter will be installed at this point. If more computing power is needed for the commissioning of the first module (for example, to deal with unexpected noise levels), space and power will be borrowed from the provision for future modules until the problems are alleviated.
The following risks and mitigation strategies have been identified: Detector noise specs not met. Excessive noise will make it impossible for the DAQ DS to meet physics goals while generating reasonable data volumes. Prior (to construction) mitigation includes studying noise conditions at ProtoDUNE, and leaving provisions in the system for additional front-end filtering (in the form of the upstream DAQ upgradable processing resources) and/or post-event builder processing (in the form of the high level filter). Mitigation (post-construction) includes augmenting filtering resources using a larger computing system for the high level filter. Lack of expert personnel. A significant number of experts in hardware, software, firmware are needed, and must be sustained throughout the project. Lack of personnel will increase technical risks and cause delay.
Externally Power/space requirements exceed CUC capacity. The CUC has fixed space and power allocation for DAQ that cannot be exceeded. Prior mitigation includes allowing sufficient bandwidth up the shafts to move the upstream DAQ components for subsequent DUNE far detector modules (modules 3 and 4) to the surface, or moving some of the DAQ components to the detector caverns, and carrying out a feasibility study for doing so. Mitigation includes expending additional resources on an expanded surface facility. Excess fake trigger rate from instrumental effects. Instrumental effects (beyond excessive noise) can cause fake triggers. Prior mitigation includes studying ProtoDUNE performance in detail, and monitoring detector performance during installation. Mitigation includes substantially increasing data volume, and increasing processing resources in the high level filter.
Mitigation includes reducing performance or identifying additional funds. ProtoDUNE timing system fails to scale for DUNE requirements. The ProtoDUNE timing system concept may not scale to DUNE in scale or performance. Prior mitigation includes testing the system at realistic scale before the final design. Mitigation includes replacing the system with upgraded hardware. WAN network. The network connectivity to the experiment from remote locations may be proven unstable, making remote control and monitoring inefficient. Prior mitigation includes ensuring that minimal human intervention is needed on the system for steady data taking and that automated error recovery is well developed. Mitigation includes effort to further improve automated data taking, and increased cost for improving network connectivity.
The cold camera system enables detection and identification of bubbling sites, and the development of mitigation strategies such as lower HV operation for some period of time. A more subtle possibility is the formation of quasi-stable eddies in argon fluid flow that could prevent positive argon ions from being cleared from the TPC volume, resulting in space charge build up that would not otherwise be expected at the depth of the FD. The space charge could in turn produce distortions in the TPC drift field that degrade tracking and calorimetry performance. The high-performance thermometry of the DUNE CISC system creates input for well developed complex fluid flow models described in section 8. 1. 3 that should enable detection of conditions associated with these eddies. Finally, a high detector live-time fraction over multi-year operation cannot be achieved without an extensive system to monitor all aspects of detector performance, report this information in an intelligent fashion to detector operators, and archive the data for deeper offline studies.
Section 8. 1. 1. 2 details the DUNE slow controls system designed for this task. The baseline designs for all the CISC systems have been used in ProtoDUNE-SP, and most design parameters are extrapolated from these designs. The ProtoDUNE-SP data (and in some cases ProtoDUNE-DP data) will therefore be used to validate the instrumentation designs and to understand their performance.
Slow controls The slow controls portion of CISC consists of three main components: hardware, infrastructure, and software. The slow controls hardware and infrastructure comprises networking hardware, signal processing hardware, computing hardware, and associated rack infrastructure. The slow controls -430 --430 --430 -software provides, for every slow control quantity, the central slow controls processing architecture, databases, alarms, archiving, and control room displays. CISC provides software and infrastructure for controlling and monitoring all detector elements that provide data on the health of the detector module or conditions important to the experiment, as well as some related hardware. Slow controls base software and databases are the central tools needed to develop control and monitoring for various detector systems and interfaces.
These include: • base input/output software; • alarms, archiving, display panels, and similar operator interface tools; and • slow controls system documentation and operations guidelines. Slow controls for external systems collect data from systems external to the detector module and provide status monitoring for operators and archiving. They collect data on beam status, cryogenics status, DAQ status, facilities systems status, interlock status bit monitoring (but not the actual interlock mechanism), ground impedance monitoring, and possibly building and detector hall monitoring, as needed. The DUNE detector safety system (DDSS) can provide inputs to CISC on safety interlock status, and CISC will monitor and make that information available to the experiment operators and experts as needed.
Slow controls network hardware The slow controls data originates from the cryogenics instrumentation and from other systems as listed in table 8. 5. This data is collected by software running on servers (section 8. 3. 1. 3) housed in the underground data room in the CUC, where data is archived in a central CISC database. The instrumentation data is transported over conventional network hardware from any sensors located in the cryogenics plant. However, the readouts that are in the racks on top of the cryostats must be cautious about grounding and noise. Therefore, each rack on the cryostat has a small network switch that sends any network traffic from that rack to the CUC via a fiber transponder. This is the only network hardware specific to slow controls and will be provided by SURF's general computing infrastructure.
Slow controls computing hardware Two servers (a primary server and a replicated backup) suitable for the relational database discussed in section 8. 3. 3 are located in the CUC data room, with an additional two servers to service the FE monitoring interface. These additional servers would cover assembling dynamic CISC monitoring web pages from adjacent databases. Yet another server will be needed to run back-end I/O. Any special purpose software, such as iFix used by the cryogenics experts, would also run here. One or -467 --467 --467 -two additional servers should accommodate these programs. Replicating this setup on a per-module basis would make commissioning and independent operation easier, accommodate different module design (and the resulting differences in database tables), and ensure sufficient capacity.
Slow controls infrastructure The data rate will be in the range of tens of kilobytes per second, given the total number of slow controls quantities and the update rate (see section 8. 3. 4), placing minimal demands on local network infrastructure. Network traffic out of SURF to Fermilab will primarily be database calls to the central CISC database, either from monitoring applications or from database replication to the offline version of the CISC database. This traffic requires little bandwidth, so the proposed general purpose links both out of the underground area at SURF and back to Fermilab can accommodate the traffic. Up to two racks of space and appropriate power and cooling are available in the CUC's DAQ server room for CISC use. This is ample space as described in section 8. 3. 1. 3.
Slow controls software To provide complete monitoring and control of detector subsystems, the slow controls software includes • the control systems base for input and output operations and defining processing logic, scan conditions, and alarm conditions; • an alarm server to monitor all channels and send alarm messages to operators; • a data archiver for automatic sampling and storing values for history tracking; and • an integrated operator interface providing display panels for controls and monitoring. In addition, the software must be able to interface indirectly with external systems (e. g. , cryogenics control system) and databases (e. g. , beam database) to export data into slow controls process variables (or channels) for archiving and status displays. This allows us to integrate displays and warnings into one system for the experiment operators and provides integrated archiving for sampled data in the archived database.
As one possibility, an input output controller running on a central DAQ server could provide soft channels for these data. Figure  8. 30 shows a typical workflow of a slow controls system. The key features of the software require highly evolved software designed to manage real-time data exchange, scalable to hundreds of thousands of channels sampled at intervals of hours to seconds as needed. The software must be well documented, supported, and reliable. The base software must also allow easy access to any channel by name. The archiver software must allow data storage in a database with adjustable rates and thresholds so data for any channel can be easily retrieved using channel name and time range. Among other key features, the alarm server software must remember the state, support an arbitrary number of clients, and provide logic for delayed alarms and acknowledging alarms.
The actual data volume will be lower because values are stored only if they vary from previous values by more than an amount that is adjustable channel-by-channel. Database storage also allows data to be sparsified later. No slow controls data is planned to be written to the DAQ stream. With careful management of archiving thresholds for each quantity monitored and yearly reduction of stored sample time density, the retained data volume can be reduced to a few TB over the life of the experiment. The subsystems to be monitored include the cryogenics instrumentation described in this chapter, the other detector systems, and relevant infrastructure and external devices. Table  8. 5 lists the quantities expected from each system.
Local integration The local integration of the slow controls consists entirely of software and network interfaces with systems that are outside of the scope of the detector module. This includes the following: • readings from the LBNF-managed external cryogenics systems, for status of pumps, flow rates, inlet, and return temperature and pressure, which are implemented via OPC-UA or a similar SCADA interface; • beam status, such as protons-on-target, rate, target steering, and beam pulse timing, which are retrieved via IFbeam; and • near detector status, which can be retrieved from a common slow controls database. Integration occurs after both the slow controls and non-detector systems are in place. The LBNF-CISC interface is managed by the cryogenics systems working group in CISC (see section 8.
As noted in sections 8. 3. 3 and 8. 3. 4, the slow control archiver will gradually accumulate terabytes of data, requiring a sizable database to store the value history and allow efficient data retrieval. Individually adjustable rates and thresholds for each channel are key to keeping this database manageable. The ProtoDUNE-SP operations provided not only a test of these features as implemented in the ProtoDUNE slow control system, but also insight into reasonable values for these archiving parameters for each system.
Because of the complexity of the project and the different requirements for QC and logistics oversight, two different databases will be used. A commercial WMS will control the inventory process at both the SDWF (items both received and shipped) and at SURF (items received at the Ross Headframe). A separate database, the DUNE construction database (DCDB), will store test and other QC data, e. g. , shipping reports and any reported damage. The WMS will need to provide location and QC information to the DCDB, which will ultimately archive both sets of data. The DCDB has not yet been designed. Until materials arrive at the SDWF (or SURF if directly shipped), the contributors' freight forwarding system will control the logistics supply chain, which will depend on the contractual circumstances and the contributor's choice.
The wire is plucked to induce a vibration, and a photodiode under the wire records the frequency of vibration, which directly translates into the tension value. The measured values are stored in the wire DCDB database. While this method is robust and has been extensively used by LArTPC experiments, it is very time consuming and thus prohibits measuring every wire. Two people over three shifts will be able to measure approximately 350 wires, 10% of the total. In ProtoDUNE-SP 10% of the wires were measured prior to cold testing and no wires were found to be out of tolerance. An alternative method, using electrical signals, is currently under development and could replace the laser method, potentially allowing measurement of all the wires. With this electrical method, where adjacent wires under certain voltages induce the middle wire to vibrate, the resonance frequency vibration of the measured wire correlates directly to the wire tension.
Results of these tests at SURF are compared with the results of the tests performed during the qualification of ASICs and FEMBs to detect possible deviations that could signal damage in the boards or problems in the connections. All test results will be stored in the same database system used for results obtained during the qualification of components. The post-installation APA tests, performed at room temperature, involve connecting up to four FEMBs to a WIB that is connected directly to a laptop computer for readout over 1 Gbps Ethernet, with power provided by a portable 12 V supply. For the reception test, the FEMBs are attached to a capacitive load to simulate the presence of wires, which allows a test of connectivity, and measurement of the baseline and RMS of the noise for each channel.