Author: Singh, P.K.
Paper Title Page
MO2BCO06 Embedded Controller Software Development Best Practices at the National Ignition Facility 54
 
  • V.K. Gopalan, A.I. Barnes, C.M. Estes, J.M. Fisher, V.J. Hernandez, P. Kale, A. Pao, P.K. Singh
    LLNL, Livermore, USA
 
  Funding: This work was performed under the auspices of the U.S. Department of Energy by Lawrence Livermore National Laboratory under Contract DE-AC52-07NA27344.
Software development practices such as continuous integration and continuous delivery (CI/CD) are widely adopted by the National Ignition Facility (NIF) which helps to automate the software development, build, test, and deployment processes. However, using CI/CD in an embedded controller project poses several challenges due to the limited computing resources such as processing power, memory capacity and storage availability in such systems. This paper will present how CI/CD best practices were tailored and used to develop and deploy software for one of the NIF Master Oscillator Room (MOR) embedded controllers, which is based on custom designed hardware consisting of a microcontroller and a variety of laser sensors and drivers. The approach included the use of automated testing frameworks, customized build scripts, simulation environments, and an optimized build and deployment pipeline, leading to quicker release cycles, improved quality assurance and quicker defect correction. The paper will also detail the challenges faced during the development and deployment phases and the strategies used to overcome them. The experience gained with this methodology on a pilot project demonstrated that using CI/CD in embedded controller projects can be challenging, yet feasible with the right tools and strategies, and has the potential to be scaled and applied to the vast number of embedded controllers in the NIF control system.
LLNL Release Number: LLNL-ABS-848418
 
slides icon Slides MO2BCO06 [1.346 MB]  
DOI • reference for this paper ※ doi:10.18429/JACoW-ICALEPCS2023-MO2BCO06  
About • Received ※ 29 September 2023 — Revised ※ 12 October 2023 — Accepted ※ 14 November 2023 — Issued ※ 30 November 2023
Cite • reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)  
 
MO3AO05 Path to Ignition at National Ignition Facility (NIF): The Role of the Automated Alignment System 138
 
  • B.P. Patel, A.A.S. Awwal, M. Fedorov, R.R. Leach Jr., R.R. Lowe-Webb, V.J. Miller Kamm, P.K. Singh
    LLNL, Livermore, USA
 
  Funding: This work was performed under the auspices of the U.S. Department of Energy by Lawrence Livermore National Laboratory under Contract DE-AC52-07NA27344
The historical breakthrough experiment at the National Ignition Facility (NIF) produced fusion ignition in a laboratory for the first time and made headlines around the world. This achievement was the result of decades of research, thousands of people, and hardware and software systems that rivaled the complexity of anything built before. The NIF laser Automatic Alignment (AA) system has played a major role in this accomplishment. Each high yield shot in the NIF laser system requires all 192 laser beams to arrive at the target within 30 picoseconds and be aligned within 50 microns-half the diameter of human hair-all with the correct wavelength and energy. AA makes it possible to align and fire the 192 NIF laser beams efficiently and reliably several times a day. AA is built on multiple layers of complex calculations and algorithms that implement data and image analysis to position optical devices in the beam path in a highly accurate and repeatable manner through the controlled movement of about 66,000 control points. The system was designed to have minimum or no human intervention. This paper will describe AA’s evolution, its role in ignition, and future modernization.
LLNL Release Number: LLNL-ABS-847783
 
slides icon Slides MO3AO05 [10.417 MB]  
DOI • reference for this paper ※ doi:10.18429/JACoW-ICALEPCS2023-MO3AO05  
About • Received ※ 22 September 2023 — Revised ※ 07 October 2023 — Accepted ※ 14 November 2023 — Issued ※ 05 December 2023
Cite • reference for this paper using ※ BibTeX, ※ LaTeX, ※ Text/Word, ※ RIS, ※ EndNote (xml)