Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “control software”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 1,603 records · Page 89
All sourcesNASA NTRSDOE OSTI
DOE OSTI2013

Closeout of CRADA JSA 2012S004: Chapter 5, Integrated Control System, of the document of the ESS Conceptual Design Report, publicly available at https://europeanspallationsource.se/accelerator-documents

The integrated control system (ICS) is responsible for the whole ESS machine and facility: accelerator, target, neutron scattering instruments and conventional facilities. This unified approach keeps the costs of development, maintenance and support relatively low. ESS has selected a standardised, field-proven controls framework, the Experimental Physics and Industrial Control System (EPICS), which was originally developed jointly by Argonne and Los Alamos National Laboratories. Complementing this selection are best practices and experience from similar facilities regarding platform standardisation, control system development and device integration and commissioning. The components of ICS include the control system core, the control boxes, the BLED database management system, and the human machine interface. The control system core is a set of systems and tools that make it possible for the control system to provide required data, information and services to engineers, operators, physicists and the facility itself. The core components are the timing system that makes possible clock synchronisation across the facility, the machine protection system (MPS) and the personnel protection system (PPS) that prevent damage to the machine and personnel, and a set of control system services. Control boxes are servers that control a collection of equipment (for example a radio frequency cavity). The integrated control system will include many control boxes that can be assigned to one supplier, such as an internal team, a collaborating institute or a commercial vendor. This approach facilitates a clear division of responsibilities and makes integration much easier. A control box is composed of a standardised hardware platform, components, development tools and services. On the top level, it interfaces with the core control system components (timing, MPS, PPS) and with the human-machine interface. At the bottom, it interfaces with the equipment and parts of the facility through a set of analog and digital signals, real-time control loops and other communication buses. The ICS central data management system is named BLED (beam line element databases). BLED is a set of databases, tools and services that is used to store, manage and access data. It holds vital control system configuration and physics-related (lattice) information about the accelerator, target and instruments. It facilitates control system configuration by bringing together direct input-output controller (IOC) con guration and real-time data from proton and neutron beam line models. BLED also simplifies development and speeds up the code-test-debug cycle. The set of tools that access BLED will be tailored to the needs of different categories of users, such as ESS staff physicists, engineers, and operators; external partner laboratories; and visiting experimental instrument users. The human-machine interface is vital to providing a high-quality experience to ICS users. It encompasses a wide array of devices and software tools, from control room screens to engineer terminal windows; from beam physics data tools to post-mortem data analysis tools. It serves users with a wide range of skills from widely varied backgrounds. The Controls Group is developing a set of user profiles to accommodate this diverse range of use-cases and users.

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗
DOE OSTI2025

Standardizing UI/UX across accelerator labs

During February 26–28, 2025, the first-ever particle accelerator user interface/user experience (UI/UX) workshop was held at SLAC. Attendees had backgrounds ranging from software development to control systems management and human factors (HF) science. The workshop began with participants discussing the current state of UI/UX procedures and practices at their respective laboratories to share experiences and learn from one another. Additional discussions focused on how to effectively integrate UI/UX best practices into actionable goals for developers, managers, and operators when working on new or existing interfaces. The goal of the working group is to create a website that will guide developers, managers, scientists, and end users at accelerator laboratories in incorporating UI/UX best practices into software development. The working group continues to meet virtually toward this goal, and is planning a second workshop for next year.

Tran, Tiffany [SLAC]↗
DOE OSTI2025

Enabling Technology for Energy Sustainability: Power Electronic Converter Control for Renewables

To ensure high penetration of renewable energy sources into power grids, their interfacing inverters need to be designed to provide grid support functions. Important grid support functions include frequency and voltage support. To this end, the research community has recently invested heavily on grid-forming control pilot projects. Grid forming control aims to replace traditional grid following control, which is based on phase-locked loop and can achieve decoupled real and reactive power control. Here, in this article, we review the state-of-the-art grid following and forming technology and point out some deficiencies in dynamic performance in the widely adopted grid-forming control design. We also examine how to ensure that the vector control capable of decoupled real and reactive power regulation can also be achieved in the grid forming design. This type of design has been prototyped and shown great potential to enable retrofitting of large amounts of grid-following controllers through purely software algorithm update. The technology ensures reliable operation of power grids with high penetration of IBRs, thereby further reducing fossil fueled energy sources and cut down carbon emission.

24 POWER TRANSMISSION AND DISTRIBUTION↗
DOE OSTI2022

Autonomous Microgrid Restoration Using Grid-Forming Inverters and Smart Circuit Breakers: Preprint

The proliferation of distributed inverter-based resources (IBRs) raises the questions if these IBRs can be used to blackstart microgrids and distribution feeders after major outages. In this paper, we propose and evaluate an autonomous microgrid restoration concept using grid-forming (GFM) IBRs and smart circuit creakers (SCBs). The concept is first explored in simulation platform and then a hardware testbed containing actual GFM inverters is developed to demonstrate these functionalities. A combination of dispatchable virtual oscillator control (dVOC) and droop-based control schemes have been designed for GFM inverter controls in the software simulations and hardware testbed. Subsequently, operation of SCBs using two distinct principles have been demonstrated that can restore or connect portions of the network.

grid reconfiguration↗
DOE OSTI2022

Extension and Validation of NEMA-Style Dual-Ring Controller in SUMO

Until recently, SUMO users could not model the behavior of a ring-and-barrier traffic signal via existing signal types, which left North American SUMO users without the direct ability to capture traffic dynamics of their local networks. This work presents the methods, implementation overview, and validation of a 'dual-ring' NEMA style traffic controller which has recently been added to the main SUMO code base. A brief explanation of the 'dual-ring' implementation is also provided as context for those new to this type of traffic controller. The foundation for this work was presented at the SUMO User Conference 2021 by researchers at the US Department of Energy's National Renewable Energy Laboratory, but was not integrated into SUMO code base at the time. Following the initial inclusion of the controller to SUMO, the authors began validation of the SUMO controller against an Econolite software-in-the-loop (SIL) traffic signal controller configured with actual setup parameters from controllers in a real-world three-intersection corridor in Tuscaloosa, Alabama, USA. This paper documents the process of adding new features to the controller code as well as validating their implementation through simulation-based and automated grey-box testing is presented in this paper. Key features such as fully-actuated operation, various timing offset plans, proper next-phase fit algorithms and more, have been added and validated against this SIL system. Though not an exhaustive demonstration of features, this work is intended make more users aware of this extension of SUMO capabilities.

MATHEMATICS AND COMPUTING↗
NASA NTRS1987

Prototype space station automation system delivered and demonstrated at NASA

The Automated Subsystem Control for Life Support System (ASCLSS) program has successfully developed and demonstrated a generic approach to the automation and control of Space Station subsystems. The hierarchical and distributed real time controls system places the required controls authority at every level of the automation system architecture. As a demonstration of the automation technique, the ASCLSS system automated the Air Revitalization Group (ARG) of the Space Station regenerative Environmental Control and Life Support System (ECLSS) using real-time, high fidelity simulators of the ARG processess. This automation system represents an early flight prototype and an important test bed for evaluating Space Station controls technology including future application of ADA software in real-time control and the development and demonstration of embedded artificial intelligence and expert systems (AI/ES) in distributed automation and controls systems.

Block, Roger F.↗
NASA NTRS2011

S-Band POSIX Device Drivers for RTEMS

This is a set of POSIX device driver level abstractions in the RTEMS RTOS (Real-Time Executive for Multiprocessor Systems real-time operating system) to SBand radio hardware devices that have been instantiated in an FPGA (field-programmable gate array). These include A/D (analog-to-digital) sample capture, D/A (digital-to-analog) sample playback, PLL (phase-locked-loop) tuning, and PWM (pulse-width-modulation)-controlled gain. This software interfaces to Sband radio hardware in an attached Xilinx Virtex-2 FPGA. It uses plug-and-play device discovery to map memory to device IDs. Instead of interacting with hardware devices directly, using direct-memory mapped access at the application level, this driver provides an application programming interface (API) offering that easily uses standard POSIX function calls. This simplifies application programming, enables portability, and offers an additional level of protection to the hardware. There are three separate device drivers included in this package: sband_device (ADC capture and DAC playback), pll_device (RF front end PLL tuning), and pwm_device (RF front end AGC control).

Lux, James P.↗
NASA NTRS2016

Flight Test Assessments of Pilot Workload, System Usability, and Situation Awareness of TASAR

Traffic Aware Strategic Aircrew Requests (TASAR) is an onboard automation concept intended to identify trajectory optimizations, in terms of fuel and time saving objectives, clear of known traffic, weather, and airspace restrictions prior to the aircrew initiating a route-change request to Air Traffic Control (ATC). The software implementation of the TASAR concept is the Traffic Aware Planner (TAP). TASAR analysis and development is being executed by the NASA Langley Research Center's Crew Systems and Aviation Operations Branch (CSAOB) under the sponsorship of the Airspace Technology Demonstration (ATD) Project of the NASA Airspace Operations and Safety Program (AOSP). The TASAR Flight Trial-2 (FT-2) was conducted in June, 2015 out of the Newport News/Williamsburg International Airport. This flight trial was conducted using a Piaggio Avanti flight test aircraft and consisted of 12 Evaluation Flights with airline commercial pilots participating as the Evaluation Pilots, three destination airports in Atlanta and Jacksonville Air Route Traffic Control Centers, and one pair of flight plans associated with each destination airport. The primary goal of FT-2 was to reduce risk for upcoming operational trials with NASA partner airlines, Alaska Airlines and Virgin America. To accomplish this primary goal, six independent objectives were conducted during FT-2, however, this paper will report only the findings of Objective 5; the assessment of system usability, pilot perceived workload, and the degree of pilot acceptability of the TAP Human Machine Interface (HMI) during flight operations, via the administration of several subjective measures.

TASAR↗
NASA NTRS1991

Logic flowgraph methodology - A tool for modeling embedded systems

The logic flowgraph methodology (LFM), a method for modeling hardware in terms of its process parameters, has been extended to form an analytical tool for the analysis of integrated (hardware/software) embedded systems. In the software part of a given embedded system model, timing and the control flow among different software components are modeled by augmenting LFM with modified Petrinet structures. The objective of the use of such an augmented LFM model is to uncover possible errors and the potential for unanticipated software/hardware interactions. This is done by backtracking through the augmented LFM mode according to established procedures which allow the semiautomated construction of fault trees for any chosen state of the embedded system (top event). These fault trees, in turn, produce the possible combinations of lower-level states (events) that may lead to the top event.

Muthukumar, C. T.↗
NASA NTRS1994

SCOS 2: An object oriented software development approach

The Spacecraft Control and Operations System 2 (SCOS 2), is intended to provide the generic mission control system infrastructure for future ESA missions. It represents a bold step forward in order to take advantage of state-of-the-art technology and current practices in the area of software engineering. Key features include: (1) use of object oriented analysis and design techniques; (2) use of UNIX, C++ and a distributed architecture as the enabling implementation technology; (3) goal of re-use for development, maintenance and mission specific software implementation; and (4) introduction of the concept of a spacecraft control model. This paper touches upon some of the traditional beliefs surrounding Object Oriented development and describes their relevance to SCOS 2. It gives rationale for why particular approaches were adopted and others not, and describes the impact of these decisions. The development approach followed is discussed, highlighting the evolutionary nature of the overall process and the iterative nature of the various tasks carried out. The emphasis of this paper is on the process of the development with the following being covered: (1) the three phases of the SCOS 2 project - prototyping & analysis, design & implementation and configuration / delivery of mission specific systems; (2) the close cooperation and continual interaction with the users during the development; (3) the management approach - the split between client staff, industry and some of the required project management activities; (4) the lifecycle adopted being an enhancement of the ESA PSS-05 standard with SCOS 2 specific activities and approaches defined; and (5) an examination of some of the difficulties encountered and the solutions adopted. Finally, the lessons learned from the SCOS 2 experience are highlighted, identifying those issues to be used as feedback into future developments of this nature. This paper does not intend to describe the finished product and its operation, but focusing on the journey to arrive there, concentrating therefore on the process and not the products of the SCOS 2 software development.

Symonds, Martin↗
NASA NTRS2006

Solar Sails

The Solar Sail Propulsion investment area has been one of the three highest priorities within the In-Space Propulsion Technology (ISPT) Project. In the fall of 2003, the NASA Headquarters' Science Mission Directorate provided funding and direction to mature the technology as far as possible through ground research and development from TRL 3 to 6 in three years. A group of experts from government, industry, and academia convened in Huntsville, Alabama to define technology gaps between what was needed for science missions to the inner solar system and the current state of the art in ultra1ightweight materials and gossamer structure design. This activity set the roadmap for development. The centerpiece of the development would be the ground demonstration of scalable solar sail systems including masts, sails, deployment mechanisms, and attitude control hardware and software. In addition, new materials would be subjected to anticipated space environments to quantify effects and assure mission life. Also, because solar sails are huge structures, and it is not feasible to validate the technology by ground test at full scale, a multi-discipline effort was established to develop highly reliable analytical models to serve as mission assurance evidence in future flight program decision-making. Two separate contractor teams were chosen to develop the SSP System Ground Demonstrator (SGD). After a three month conceptual mission/system design phase, the teams developed a ten meter diameter pathfinder set of hardware and subjected it to thermal vacuum tests to compare analytically predicted structural behavior with measured characteristics. This process developed manufacturing and handling techniques and refined the basic design. In 2005, both contractor teams delivered 20 meter, four quadrant sail systems to the largest thermal vacuum chamber in the world in Plum Brook, Ohio, and repeated the tests. Also demonstrated was the deployment and articulation of attitude control mechanisms. In conjunction with these tests, the stowed sails were subjected to launch vibration and ascent vent tests. Other investments studied radiation effects on the solar sail materials, investigated spacecraft charging issues, developed shape measuring techniques and instruments, produced advanced trajectory modeling capabilities, and identified and resolved gossamer structure dynamics issues. Technology validation flight and application to a He1iophysics science mission is on the horizon.

Young, Roy↗
DOE OSTI2015

A modular and compact portable mini-endstation for high-precision, high-speed fixed target serial crystallography at FEL and synchrotron sources

The design and implementation of a compact and portable sample alignment system suitable for use at both synchrotron and free-electron laser (FEL) sources and its performance are described. The system provides the ability to quickly and reliably deliver large numbers of samples using the minimum amount of sample possible, through positioning of fixed target arrays into the X-ray beam. The combination of high-precision stages, high-quality sample viewing, a fast controller and a software layer overcome many of the challenges associated with sample alignment. A straightforward interface that minimizes setup and sample changeover time as well as simplifying communication with the stages during the experiment is also described, together with an intuitive naming convention for defining, tracking and locating sample positions. Lastly, the setup allows the precise delivery of samples in predefined locations to a specific position in space and time, reliably and simply.

07 ISOTOPE AND RADIATION SOURCES↗
NASA NTRS2015

Orion Launch Abort System Performance on Exploration Flight Test 1

This paper will present an overview of the flight test objectives and performance of the Orion Launch Abort System during Exploration Flight Test-1. Exploration Flight Test-1, the first flight test of the Orion spacecraft, was managed and led by the Orion prime contractor, Lockheed Martin, and launched atop a United Launch Alliance Delta IV Heavy rocket. This flight test was a two-orbit, high-apogee, high-energy entry, low-inclination test mission used to validate and test systems critical to crew safety. This test included the first flight test of the Launch Abort System preforming Orion nominal flight mission critical objectives. NASA is currently designing and testing the Orion Multi-Purpose Crew Vehicle (MPCV). Orion will serve as NASA's new exploration vehicle to carry astronauts to deep space destinations and safely return them to earth. The Orion spacecraft is composed of four main elements: the Launch Abort System, the Crew Module, the Service Module, and the Spacecraft Adapter (Fig. 1). The Launch Abort System (LAS) provides two functions; during nominal launches, the LAS provides protection for the Crew Module from atmospheric loads and heating during first stage flight and during emergencies provides a reliable abort capability for aborts that occur within the atmosphere. The Orion Launch Abort System (LAS) consists of an Abort Motor to provide the abort separation from the Launch Vehicle, an Attitude Control Motor to provide attitude and rate control, and a Jettison Motor for crew module to LAS separation (Fig. 2). The jettison motor is used during a nominal launch to separate the LAS from the Launch Vehicle (LV) early in the flight of the second stage when it is no longer needed for aborts and at the end of an LAS abort sequence to enable deployment of the crew module's Landing Recovery System. The LAS also provides a Boost Protective Cover fairing that shields the crew module from debris and the aero-thermal environment during ascent. Although the Orion Program has tested a number of the critical systems of the Orion spacecraft on the ground, the launch environment cannot be replicated completely on Earth. A number of flight tests have been conducted and are planned to demonstrate the performance and enable certification of the Orion Spacecraft. Exploration Flight Test 1, the first flight test of the Orion spacecraft, was successfully flown on December 5, 2014 from Cape Canaveral Air Force Station's Space Launch Complex 37. Orion's first flight was a two-orbit, high-apogee, high-energy entry, low-inclination test mission used to validate and test systems critical to crew safety, such as heat shield performance, separation events, avionics and software performance, attitude control and guidance, parachute deployment and recovery operations. One of the key separation events tested during this flight was the nominal jettison of the LAS. Data from this flight will be used to verify the function of the jettison motor to separate the Launch Abort System from the crew module so it can continue on with the mission. The LAS nominal jettison event on Exploration Flight Test 1 occurred at six minutes and twenty seconds after liftoff (See Fig. 3). The abort motor and attitude control motors were inert for Exploration Flight Test 1, since the mission did not require abort capabilities. A suite of developmental flight instrumentation was included on the flight test to provide data on spacecraft subsystems and separation events. This paper will focus on the flight test objectives and performance of the LAS during ascent and nominal jettison. Selected LAS subsystem flight test data will be presented and discussed in the paper. Exploration Flight Test -1 will provide critical data that will enable engineering to improve Orion's design and reduce risk for the astronauts it will protect as NASA continues to move forward on its human journey to Mars. The lessons learned from Exploration Flight Test 1 and the other Flight Test Vehicles will certainly contribute to the vehicle architecture of a human-rated space launch vehicle.

McCauley, R.↗
DOE OSTI2019

Future SDN-HPON Control Plane Architecture and Protocol for On-Demand Terabit End-to-End Extreme-Scale Science Applications

The UC Davis team conducted architecture, algorithm and experimental studies for next generation ultra-high-bandwidth optical networks in support of extreme-scale science applications. In particular, over the course of this 3-year project, the UC Davis team achieved the following main accomplishments: Designed a network architecture for automated multi-domain service provisioning: Designed information exchange schemes between autonomous systems (domains) Designed application programming interfaces to orchestrate resource reservation in data centers, high performance computation facilities, and communication networks belonging to different autonomous systems Experimentally assessed the multi-domain network architecture in a distributed field trial set-up connecting premises in three continents Designed a broker-based orchestrated multi-domain optical networking framework supporting observe-analyze-act cycle based cognitive inter-domain service provisioning: Designed an inter-domain operation mechanism, e.g., topology abstraction, for the broker plane and domain managers to collaboratively accomplish inter-domain service provisioning while respecting the autonomy of each administrative domain Designed an alien wavelength monitoring scheme and an artificial neural network based optical signal-to-noise ratio estimator for quality-of-transmission aware inter-domain service provisioning Developed a deep neural network based multi-domain traffic predictor and a cognitive routing and spectrum assignment algorithm to realize knowledge-based autonomous traffic engineering in multi-domain networks Implemented an optical signal-to-noise ratio estimator and traffic predictor with Google’s Tensor flow and assessed their performance using experimental and synthetic data Demonstrated the benefits of the proposed cognitive schemes with experiments ona two-domain elastic optical network testbed and evaluations on a six-domain simulation framework Built a two-domain software-defined networking control plane testbed using the ONOS platform and demonstrated the workflow of broker and domain manager cooperation, including hierarchical performance monitoring, topology abstraction and cognitive resource allocation. Designed self-learning cognitive service provisioning schemes using advanced machine learning technologies: Designed a self-taught anomaly detection framework for optical networks, including an unsupervised data clustering module for pattern recognition, a supervised data regression and classification module for online anomaly detection, and the system operation principle Experimentally validated the effectiveness of the self-taught anomaly detection framework with various failure/anomaly scenarios. Designed a self-learning autonomic routing, modulation and spectrum assignment (RMSA) provisioning framework for elastic optical networks with deep reinforcement learning. Designed effective modeling and training mechanisms for the self-learning RMSA framework Conducted extensive numerical simulations with various traffic patterns and topologies to verify the advantage of the self-learning RMSA framework.

42 ENGINEERING↗
NASA NTRS2003

Use of Soft Computing Technologies For Rocket Engine Control

The problem to be addressed in this paper is to explore how the use of Soft Computing Technologies (SCT) could be employed to further improve overall engine system reliability and performance. Specifically, this will be presented by enhancing rocket engine control and engine health management (EHM) using SCT coupled with conventional control technologies, and sound software engineering practices used in Marshall s Flight Software Group. The principle goals are to improve software management, software development time and maintenance, processor execution, fault tolerance and mitigation, and nonlinear control in power level transitions. The intent is not to discuss any shortcomings of existing engine control and EHM methodologies, but to provide alternative design choices for control, EHM, implementation, performance, and sustaining engineering. The approaches outlined in this paper will require knowledge in the fields of rocket engine propulsion, software engineering for embedded systems, and soft computing technologies (i.e., neural networks, fuzzy logic, and Bayesian belief networks), much of which is presented in this paper. The first targeted demonstration rocket engine platform is the MC-1 (formerly FASTRAC Engine) which is simulated with hardware and software in the Marshall Avionics & Software Testbed laboratory that

Trevino, Luis C.↗
NASA NTRSDate not supplied

Eye Glance Behaviors of Ground Control Station Operators in a Simulated Urban Air Mobility Environment

Research into concepts such as advanced air mobility (AAM) and urban air mobility (UAM) offers an opportunity for successfully and safely adding new classes of vehicles into the National Airspace System. However, a need exists for research into the human factors associated with these concepts. In this paper, we evaluate the gaze behaviors of three remote ground control station operators (GCSOs) conducting simulated UAM operations. The participants monitored and controlled an unmanned aircraft system (UAS) from pre-flight to landing using ground control station (GCS) software across nine scenarios within a remote UAS operations center at NASA Langley Research Center (LaRC). As this work was exploratory, descriptive statistics were calculated to provide some initial insight into GCSO gaze patterns associated with the GCS display. Scenarios that required the operator to directly interact with an airspace scheduling system off-screen resulted in fewer on-screen glances than scenarios that did not include direct interactions with the off-screen system. After investigating several areas of interest (AOIs) within the GCS display, participants primarily viewed three AOIs: the map, vehicle status, and operations checklist. The results yielded several GCS design and operational improvement recommendations to include: (a) adding altitude information to the vehicle icon, (b) adding additional traffic information, and (c) including additional GCS training, to reduce the need to scan an operations checklist, which would allow allocation of visual attention towards other AOIs.

Urban Air Mobility↗
NASA NTRS1992

Toward full life cycle control: Adding maintenance measurement to the SEL

Organization-wide measurement of software products and processes is needed to establish full life cycle control over software products. The Software Engineering Laboratory (SEL)--a joint venture between NASA GSFC, the University of Maryland, and Computer Sciences Corporation--started measurement of software development more than 15 years ago. Recently, the measurement of maintenance was added to the scope of the SEL. In this article, the maintenance measurement program is presented as an addition to the already existing and well-established SEL development measurement program and evaluated in terms of its immediate benefits and long-term improvement potential. Immediate benefits of this program for the SEL include an increased understanding of the maintenance domain, the differences and commonalities between development and maintenance, and the cause-effect relationships between development and maintenance. Initial results from a sample maintenance study are presented to substantiate these benefits. The long-term potential of this program includes the use of maintenance baselines to better plan and manage future projects and to improve development and maintenance practices for future projects wherever warranted.

Rombach, H. Dieter↗
DOE OSTI2021

Upgrade of hardware controls for the STAR experiment at RHIC

The STAR experiment has been delivering significant physics results for more than 20 years. Stable operation of the experiment was achieved by using a robust controls system based on the Experimental Physics and Industrial Control System (EPICS). Now an object-oriented approach with Python libraries, adapted for EPICS software, is going to replace the procedural-based EPICS C libraries previously used at STAR. Advantages of the new approach include stability of operation, code reduction and straightforward project documentation. The first two sections of this paper introduce the STAR experiment, give an overview of the EPICS architecture, and present the use of Python for controls software. Therefore, specific examples, as well as upgrades of user interfaces, are outlined in the following sections.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗