The National Ignition Facility (NIF) Software Engineering Efforts Presentation to SIR Computers and Technology Group March 17, 2016

Transcription

1 The National Ignition Facility (NIF) Software Engineering Efforts Presentation to SIR Computers and Technology Group March 17, 2016 Eric Stout NIF Controls Software Architect

2 The NIF mission is to study high-energy-density physics and fusion ignition NIF is the world's largest and most energetic laser NIF s goal is to demonstrate nuclear fusion with energy gain for the first time in the laboratory NIF explores extreme conditions in a laboratory setting 100 million degrees K 100 billion times atmospheric pressure 2

3 The mission of NIF is to produce high-energy-density conditions and, ultimately, fusion ignition High Energy Density Physics Fusion Ignition Basic Science Helping ensure the nation's security without nuclear weapons testing Research for a safe, virtually unlimited, carbon-free energy future Achieving breakthroughs in a wide variety of scientific disciplines, including astrophysics, materials science, radioactive and hazardous waste treatment, particle physics, and x-ray and neutron science 3

4 Inertial confinement fusion will be used to produce ignition and energy gain NIF s 192 energetic laser beams will be used to compress very small deuterium-tritium fusion targets the size of a BB 4

5 Target chamber hanging

6

7 The NIF is all about the data The NIF has just one product data The NIF is a very dynamic environment and the management of data is essential in order to meet it s scientific goals There are several different categories of data used on the NIF Setup data Configuration data Calibration data Analysis data A large number of tools have been implemented to handle this ever growing amount of data The purpose of the support tools is to facilitate taking high quality shots on the NIF

8 Three dozen diagnostic systems were deployed by 2010 for the National Ignition Campaign SPIDER Target Alignment Sensor Positioner Static x-ray Imager POLAR DIM DANT E CRYO-Target Positioner MRS Chamber Center Reference System DIM Final Optics Damage Inspection Neutron Time of Flight 20m Target Positioner Neutron Time of Flight 20m Full Aperture Backscatter Station 8

9 Data is at the heart of the NIF Input Campaign Management & Shot Setup Shot Planning & Loop Analysis Output (NIF Archive) (Oracle DB) Shot Setup Reports Configuration of Installed Parts Automated Analysis Automated Shot Data Analysis IDL Cluster Conduct Experiment Integrated Computer Control System (ICCS) Calibration Values Shot Data & Analysis Results Manual Analysis Downloads Visualization Laser Performance Operations Model The NIF archive is the foundation of the support tools

10 The NIF project has five teams developing the support tools Shot Planning & Loop Analysis Tools Lane Mgr Damage Calculator Optics Loop Viewers HIF Estimated Exposure Tool Campaign Management Campaign Management Tool Target diagnostic Template Mgr Approval Mgr Configuration Checker Enterprise Configuration Management Work Permits Data Analysis & Visualization Analysis Archive (CMS) Laser Performance Operations Model Physics model interface Logs Analysis Analysis engine Calibration Archive (CDMS) Site Registry (Glovia) Facility Calendar Pulse Shape Editor Maintenance Tracking (SMART) Data Loader (ETL) Beam Pointing Assistant Target Selection Manager Parts List Manager Radiological Tracking System Configurator Document Control (ECMS) Visualization Archive Exporter Experimenter Website Data Loader (ETL) Data source management Reports Verification These toolsets constitute over 40 integrated applications

11 A significant effort has been needed in order to implement the support tools Code count by support tool Languages used Shot Planning & Loop Tools, 181,433 Data Analysis & Visualization, 656,908 Laser Performance Operations Model, 287,598 Campaign Management, 948,211 C/C++ 6% HTML 8% IDL 5% Other 7% Java 50% Configuration Management, 2,550,690 SQL 11% XML 13% 4.3M lines of code in order to implement the current capabilities

12 The CMT shot setup allows users to configure the Dante Diagnostic CMT allows the specification of over 18,000 setup parameters of which over 500 are applicable to Dante

13 The Lane Manager is used to schedule experiments based on Dante availability Lane Manager is the primary means of communicating the shot schedule

14 The Shot Report page indicates the success of each diagnostic analysis Automated analysis supports over a dozen diagnostics

15 Multiple views of the Dante data are visualized not just the final result The tools can visualize data across many shots and compare them to simulated data

16 The Laser Performance Operations Model allows scientists to verify that the laser met it goals Key data items: Laser Use Laser Energy Laser Timing Laser Pulse Shape Laser Power Balance LPOM data is used in Dante analysis to adjust the timing of the results based upon the actual laser timing

17 ICCS software provides software controls automation across all NIF laser subsystems Master Oscillator Beam Control Cryogenic Amplifier & Power Conditioning Optics Inspection Target Area Positioners Optical Switch (PEPC) Injection Laser Laser Diagnostics 17

18 NIF is a 192 beam laser organized into clusters, bundles, and quads

19 Requirements of the NIF Integrated Computer Control System (ICCS) Core duties Configure facility for an experiment Execute experiment Store experimental results Implementation challenges Control of 50,000 device points Beam alignment to <50 microns on target Beam timing within <30 psec Flexible automation with oversight by 14 operators Shot-to-shot goal of <4 hours Assure Situational awareness Machine protection A highly data-driven, modular, automated, and distributed controls architecture was needed for a system the size of NIF 19

20 The Integrated Computer Control System (ICCS) robustly operates NIF Highly data-driven Device configuration Experiment definitions Experiment model Experiment results NIF Control Room Highly distributed 35 Framework & Supervisory servers 3 compute clusters (110 nodes) 950 Front-End Processors 950 embedded controllers 2,400 processes Industry-standard software design Object-oriented design patterns CORBA as a communication middleware Automatic control of 192-beam shots is overseen by 14 operator stations Early key design decisions have proven successful and are now the foundation for controlling the NIF 20

21 ICCS consists of 3.5 million lines of software running on 1,900 distributed computers throughout NIF ICCS computer and control hardware 21

22 A segmented and layered architecture implements ICCS control system Oracle Database Framework Services Experiment Automation System Safety (Allen-Bradley, Rockwell) PLC/IO PLC/IO Utilities (Allen-Bradley, Rockwell) Vacuum PLC Cooling PLC NIF, Target, and Bundle Supervisory Systems Software Distribution Bus (CORBA over network) FEP (VxWorks, Ada) Devices Embedded Controller FEP (Solaris, Ada) Devices Embedded Controller FEP (Windows, Ada/Java) Devices Embedded Controller Graphical User Interfaces Argon PLC Local PC 16k Points 50k Points 22

23 Common frameworks in all processes simplify maintenance and operation of ICCS C Connection Objects Application Objects T C O R Object Factory System Manager Status Monitor Message Log Alerts Events Reservations Shot Archive Machine History Config/ Name Service P B A Framework Agents Heartbeat Startup/Shutdown All ICCS processes have the same core behaviors Consistency provides flexibility in software development staff assignments 23

24 Object-oriented, data-driven design abstracted 50,000 control points to 300 discrete control classes Motor Example Control Points Quantity Stepping motors 10,500 Mirror surface actuators 7,500 Binary actuators 2,200 Precision timing triggers 1,600 Cameras 1,000 Photodiodes 900 Resulting reduction in code base has significantly improved the maintainability 24

25 ICCS primary requirement is to automatically align, fire and diagnose laser shots with a goal of <4 hours Fire pre-amplifier Fire main amplifiers S h o t Amplifier cooling Archive Shot Preparation S h o t Verify S h o t Archive 30-m 20-m 2-s <4 hours Automated Shot Cycle Acquire campaign shot goals from laser physics model Perform automatic alignment and wavefront correction Configure diagnostics and laser performance settings Conduct countdown (software:4-min and timing:2-sec) Assess shot outcome and archive shot data 25

26 Automation software execute NIF experiments with data driven workflow and re-useable macro steps Shot Director Layer Shot Cycle States Implement_Plan Collaboration Layer Shot Model With Macro Step Sequences Laser Diagnostics Laser Alignment Shot Supervisor Layer Macro Step Phases Align Main Laser (Perform Phase) Steps Align PABTS (step) Substeps Set Filter 30% Open Shutter Status & Control Layer Setpoints Filter Shutter Goto 30% Transmission Goto Open 26

27 Setpoints simplify verification and management of device control settings A device setpoint consists of A unique, device-specific name One or more configuration settings Setpoints can be Pre-defined in the database Created on demand Experiment Automation System uses setpoints to configure, verify, and lock devices in shot position Outside shots, operators can view, change, and command devices to known setpoints Over 100,000 device setpoint reconfigurations are performed on each shot cycle The setpoint abstraction provides a system-wide language for device state management 27

28 A user interface framework ensures consistent presentation layer and simplifies development Navigator Starting point for operators Provides database-driven table of contents for traversing GUI hierarchy Broadviews Scalable schematic diagrams for a subsystem Live control and status updates for collections of devices Control Panels Specialized interface for a single device type Detailed status and control All user interfaces: Update automatically when device state changes Alert users of connectivity problems 28

29 Drilldown Load Inventory Drilldown Database 29

30 ICCS Cornerstone: Rigorous software engineering practices Documented governance plan for Software Quality Assurance IEEE standards used as best practice guidelines Peer reviews for designs and code changes Integrated product testing Independent Verification and Validation team Dedicated Configuration Management team The ICCS software engineering process is a key component of NIF equipment protection 30

31 Rigorous quality controls at every development phase assure delivery of reliable software Development Team Quality Control Team Operations Team Release Plan Test Procedures Acceptance Test Software Development Software Integration Off-line Test & Training NIF Install On-line Test Commissioning Software Change Requests Software Change Control Board Stakeholder Steering Committee Work Authorization Point System Ready 31

32 Incremental deployment strategy delivers functionality, while iteratively managing risk Target high-level project milestones Bi-monthly software releases (previously 3-6 months) Flexibility for interim software patches and data changes as required Release content driven by Enhanced capabilities and operational improvements Defect corrections Framework and code migration Overlapped 2-month development, test and deployment lifecycle Stakeholders prioritize release content SW Leads collect detailed requirements Developers design, code, unit test and integrate Independent test team performs offline and online qualification tests 13.2 Feb Mar Apr May Jun Jul 2M 1M Aug Sept Oct Nov Dec Jan M 2M 1M Legend M 2M 1M Development M 2M 1M Integration M 2M 1M QA 32

33 Issues Software schedules are planned and tracked to ensure successful releases Scope Coded Reviewed Integration Tested Qualification Tested Progress Release Scope Closure Rates 0 Using historical rate projections to manage release content has greatly increased success in meeting deployment schedule 33

34 Future work activities continue to focus on increasing controls availability to NIF operations Availability NIF operational support (20-30%) Laser preparation shots (concurrent shot cycles) Maintenance operations automation (AMT & Loop1 commissioning shots) Reduce backlog of RAM software change requests Predictive monitoring for off-normal system states Maintainability Continued multi-year code base migration to Java Controls Enhancements Beamline pulse delays up to 1 micro second (Long Delays) Short Pulse backlighter capability commissioning (ARC) 34

35 Technology refresh is an active effort Software and hardware options are constantly improving Industry trend is toward open source software Migrating codebase from Ada to Java Hardware platform independence Large inventory of vendor and open-source libraries Significantly better debugging, profiling, monitoring tools Easier to find industry expertise when staffing Migrating processes to Linux x86 commodity hardware Virtual machines Developing strategy for FEP technology refresh ICCS software architecture was designed for evolutionary change with minimal impact 35

36 Port all ICCS software to a single language platform Now Future AccuRev, Apex Code Repository Rational Ada, GNAT Ada OrbExpress, Java, Jacorb Operating Systems VxWorks, Linux, Solaris, Windows Technology Refresh Accurev Code Repository Java, Jacorb Operating Systems Linux, Windows, Virtual Machines Platforms Sun, X86, PPC, VME, field buses Platforms x86, VME, field buses 36

37 ICCS is successfully operating at full scale A distributed architecture Supports continual evolutionary change with minimal impacts A data-driven architecture Allows modification of run-time behavior without new software releases Model-driven Experiment Automation System Provides the flexibility and parallelism required to meet all NIF program missions Actively leverage new technologies Fewer and more mainstream tools Runtime diagnostics for evaluating system performance A versatile, data-driven software architecture using client/server distribution will support NIF operation for decades 37

38 38