Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “software testing”

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 217 records · Page 12

Design and Test Plans for a Non-Nuclear Fission Power System Technology Demonstration Unit

A joint National Aeronautics and Space Administration (NASA) and Department of Energy (DOE) team is developing concepts and technologies for affordable nuclear Fission Power Systems (FPSs) to support future exploration missions. A key deliverable is the Technology Demonstration Unit (TDU). The TDU will assemble the major elements of a notional FPS with a non-nuclear reactor simulator (Rx Sim) and demonstrate system-level performance in thermal vacuum. The Rx Sim includes an electrical resistance heat source and a liquid metal heat transport loop that simulates the reactor thermal interface and expected dynamic response. A power conversion unit (PCU) generates electric power utilizing the liquid metal heat source and rejects waste heat to a heat rejection system (HRS). The HRS includes a pumped water heat removal loop coupled to radiator panels suspended in the thermal-vacuum facility. The basic test plan is to subject the system to realistic operating conditions and gather data to evaluate performance sensitivity, control stability, and response characteristics. Upon completion of the testing, the technology is expected to satisfy the requirements for Technology Readiness Level 6 (System Demonstration in an Operational and Relevant Environment) based on the use of high-fidelity hardware and prototypic software tested under realistic conditions and correlated with analytical predictions.

Mason, Lee↗

Autonomous Science Restart for the Planned Europa Mission with Lightweight Planning and Execution

In this paper we present MEXEC - a lightweight on-board planning and execution system that monitors spacecraft state to robustly respond to current conditions. In addition it projects the remaining plan forward in time to detect conflicts and revise the plan. Most current planetary missions use sequence based commanding from the ground,which limits the ability to respond to on-board state varying from planned for state. This results in planning for worst-case execution time, power utilization, data volume and other resources and leads to under utilization of the spacecraft capability. It also limits the ability to respond to faults. Due to the high radiation environment at Jupiter the probability of flight software resets is high. Therefore, of particular interest to the planned Europa Mission is the capability to restart the science plan after flight software resets. In this paper we present results from running Europa flyby scenarios with flight software resets in the Europa flight software test environment. Preliminary results with the prototype scenario show MEXEC takes less than a tenth of a second to respond to resets. The development was done as part of Europa-focused flight software, but MEXEC was designed to be applicable to landers and rovers as well.

Joshi, Rajeev↗

Advanced Stirling Convertor Control Unit Testing at NASA Glenn Research Center in the Radioisotope Power Systems System Integration Laboratory

Future NASA missions could include establishing Lunar or Martian base camps, exploring Jupiters moons and travelling beyond where generating power from sunlight may be limited. Radioisotope Power Systems (RPS) provide a dependable power source for missions where inadequate sunlight or operational requirements make other power systems impractical. Over the past decade, NASA Glenn Research Center (GRC) has been supporting the development of RPSs. The Advanced Stirling Radioisotope Generator (ASRG) utilized a pair of Advanced Stirling Convertors (ASC). While flight development of the ASRG has been cancelled, much of the technology and hardware continued development and testing to guide future activities. Specifically, a controller for the convertor(s) is an integral part of a Stirling-based RPS. For the ASRG design, the controller maintains stable operation of the convertors, regulates the alternating current produced by the linear alternator of the convertor, provides a specified direct current output voltage for the spacecraft, synchronizes the piston motion of the two convertors in order to minimize vibration as well as manage and maintain operation with a stable piston amplitude and hot end temperature. It not only provides power to the spacecraft but also must regulate convertor operation to avoid damage to internal components and maintain safe thermal conditions after fueling. Lockheed Martin Coherent Technologies has designed, developed and tested an Engineering Development Unit (EDU) Advanced Stirling Convertor Control Unit (ACU) to support this effort. GRC used the ACU EDU as part of its non-nuclear representation of a RPS which also consists of a pair of Dual Advanced Stirling Convertor Simulator (DASCS), and associated support equipment to perform a test in the Radioisotope Power Systems System Integration Laboratory (RSIL). The RSIL was designed and built to evaluate hardware utilizing RPS technology. The RSIL provides insight into the electrical interactions between as many as 3 radioisotope power generators, associated control strategies, and typical electric system loads. The first phase of testing included a DASCS which was developed by Johns Hopkins UniversityApplied Physics Laboratory and simulates the operation and electrical behavior of a pair of ASCs in real time via a combination of hardware and software. Testing included the following spacecraft electrical energy storage configurations: capacitive, battery, and supercapacitor. Testing of the DASCS and ACU in each energy storage configuration included simulation of a typical mission profile, and transient voltage and current data during load turn-on/turn-off. Testing for these devices also included the initiation of several system faults such as short circuits, electrical bus over-voltage, under-voltage and a dead bus recovery to restore normal power operations. The goal of this testing was to verify operation of the ACU(s) when connected to a spacecraft electrical bus.

Dugala, Gina M.↗

Advanced Stirling Convertor Control Unit Testing at NASA Glenn Research Center in the Radioisotope Power Systems System Integration Laboratory

Future NASA missions could include long-duration flyby, orbital, lander, or rover applications where generating power from sunlight may be limited. Radioisotope power systems (RPSs) provide a dependable power source for missions where inadequate sunlight or operational requirements make other power systems impractical. Over the past 16 years, NASA Glenn Research Center has been supporting the development of RPSs. The advanced Stirling radioisotope generator (ASRG) utilized a pair of advanced Stirling convertors (ASCs). Although flight development of the ASRG has been canceled, much of the technology and hardware continued development and testing to guide future activities. Specifically, a controller for the convertor(s) is an integral part of a Stirling-based RPS. For the ASRG design, the controller maintains stable operation of the convertors, regulates the alternating current produced by the linear alternator of the convertor, provides a specified direct-current output voltage for the spacecraft, and synchronizes the piston motion of the two convertors to minimize vibration as well as manage and maintain operation with a stable piston amplitude and hot-end temperature. It not only provides power to the spacecraft but also must regulate convertor operation to avoid damage to internal components and maintain safe thermal conditions after fueling. Lockheed Martin Coherent Technologies, Inc., has designed, developed, and tested an ASC control unit engineering development unit (ACU EDU) to support this effort. GRC used the ACU EDU as part of its nonnuclear representation of a RPS that also consists of a Dual advanced Stirling convertor simulator (DASCS), and associated support equipment to perform a test in the Radioisotope Power Systems System Integration Laboratory (RSIL). The RSIL was designed and built with flexibility to evaluate hardware utilizing RPS technology. The RSIL provides insight into the electrical interactions between as many as three radioisotope power generators, associated control strategies, and typical electric system loads. The first phase of testing included a DASCS that was developed by Johns Hopkins University Applied Physics Laboratory and simulates the operation and electrical behavior of a pair of ASCs in real time via a combination of hardware and software. Testing included the following spacecraft electrical energy storage configurations: capacitor, battery, and supercapacitor. Testing of the DASCS and ACU in each energy storage configuration included simulation of a typical mission profile and transient voltage and current data during load turnon and turnoff. Testing for these devices also included the initiation of several system faults such as short circuits, electrical bus overvoltage, undervoltage, and a "dead bus" recovery to restore normal power operations. The goal of this testing was to verify operation of the ACU(s) when connected to a spacecraft electrical bus. The results of these tests are presented here.

General↗

Improved Throughput and Analysis of Scratch Test Results via Automation and Machine Learning

A data analysis automation interface that incorporates machine learning (ML) has been developed to improve productivity, efficiency, and consistency in identifying and defining critical load values (or other values associated with optically identifiable characteristics) of a coating when a scratch test is performed. In this specific program, the machine learning component of the program has been trained to identify the Critical Load 2 (L C2 ) value by analyzing images of the scratch tracks created in each test. An optical examination of the scratch by a human operator is currently used to determine where this value occurs. However, the vagueness of the standard has led to varying interpretations and nonuniform usage by different operators at different laboratories where the test is implemented, resulting in multiple definitions of the desired parameter. Using a standard set of training and validation images to create the dataset, the critical load can be identified consistently amongst different laboratories using the automation interface without requiring the training of human operators. When the model was used in conjunction with an instrument manufacturer's scratch test software, the model produced accurate and repeatable results and defined L C2 values in as little as half of the time compared to a human operator. When combined with a program that automates other aspects of the scratch testing process usually conducted by a human operator, scratch testing and analysis can occur with little to no intervention from a human beyond initial setup and frees them to complete other work in the lab.

36 MATERIALS SCIENCE↗

Risk-Informed Safety Assurance and Probabilistic Assessment of Mission-Critical Software-Intensive Systems

This report validates and documents the detailed features and practical application of the framework for software intensive digital systems risk assessment and risk-informed safety assurance presented in the NASA PRA Procedures Guide for Managers and Practitioner. This framework, called herein the "Context-based Software Risk Model" (CSRM), enables the assessment of the contribution of software and software-intensive digital systems to overall system risk, in a manner which is entirely compatible and integrated with the format of a "standard" Probabilistic Risk Assessment (PRA), as currently documented and applied for NASA missions and applications. The CSRM also provides a risk-informed path and criteria for conducting organized and systematic digital system and software testing so that, within this risk-informed paradigm, the achievement of a quantitatively defined level of safety and mission success assurance may be targeted and demonstrated. The framework is based on the concept of context-dependent software risk scenarios and on the modeling of such scenarios via the use of traditional PRA techniques - i.e., event trees and fault trees - in combination with more advanced modeling devices such as the Dynamic Flowgraph Methodology (DFM) or other dynamic logic-modeling representations. The scenarios can be synthesized and quantified in a conditional logic and probabilistic formulation. The application of the CSRM method documented in this report refers to the MiniAERCam system designed and developed by the NASA Johnson Space Center.

Guarro, Sergio B.↗

The 2GCHAS: A high productivity software development environment

To the user, the most visible feature of the Transportable Applications Executive (TAE) is its very powerful user interface. To the programmer, TAE's user interface, proc concept, standardized interface definitions, and hierarchy search provide a set of tools for rapidly prototyping or developing production software. The 2GCHAS (Second Generation Comprehensive Helicopter Analysis System) project has extended and enhanced these mechanisms, creating a powerful and high productivity programming environment where the 2GCHAS development environment is 2GCHAS itself and where a sustained rate for certified, documented, and tested software above 30 delivered source instructions per programmer day has been achieved. The 2GCHAS environment is not limited to helicopter analysis, but is applicable to other disciplines where software development is important.

Babb, Larry↗

Verifying Diagnostic Software

Livingstone PathFinder (LPF) is a simulation-based computer program for verifying autonomous diagnostic software. LPF is designed especially to be applied to NASA s Livingstone computer program, which implements a qualitative-model-based algorithm that diagnoses faults in a complex automated system (e.g., an exploratory robot, spacecraft, or aircraft). LPF forms a software test bed containing a Livingstone diagnosis engine, embedded in a simulated operating environment consisting of a simulator of the system to be diagnosed by Livingstone and a driver program that issues commands and faults according to a nondeterministic scenario provided by the user. LPF runs the test bed through all executions allowed by the scenario, checking for various selectable error conditions after each step. All components of the test bed are instrumented, so that execution can be single-stepped both backward and forward. The architecture of LPF is modular and includes generic interfaces to facilitate substitution of alternative versions of its different parts. Altogether, LPF provides a flexible, extensible framework for simulation-based analysis of diagnostic software; these characteristics also render it amenable to application to diagnostic programs other than Livingstone.

Lindsey, Tony↗

Testing Mars 2020 Flight Software and Hardware in the Surface System Development Environment

The Mars 2020 (M2020) Perseverance Rover is NASA's most advanced planetary rover mission to date. It includes a novel Sample Caching Subsystem (SCS) which will collect rock cores for possible future return to Earth, as well as an improved mobility system with enhanced autonomous navigation which will enable it to traverse faster and farther than prior rovers. The development of both systems required extensive flight software and flight hardware testing. To support this testing, we developed the Surface System Development Environment (SSDEV) and used it for a wide variety of testing. SSDEV is a bundled subset of M2020 Flight Software which runs on commercially available Linux computers and can be combined with multiple backend options for simulation and hardware control. The SSDEV architecture enabled our teams to perform much more testing of flight software and flight hardware than would have otherwise been possible. As a secondary benefit, the SSDEV-based test campaigns also helped our teams enter the operations phase of the mission with greater readiness of operations products and tools. In this paper, we summarize the motivation for SSDEV, provide an overview of the SSDEV architecture, list several examples of how SSDEV was used, and summarize lessons learned. SSDEV is not a substitute for integrated testing with flight-like avionics, but it enabled substantially more testing than would have otherwise been possible and also provided some unique benefits. We recommend architectures like SSDEV to future projects that need to perform extensive hardware and software testing using a limited set of flight-like avionics.

Wai, Dennis↗

Integrated Application of Active Controls (IAAC) technology to an advanced subsonic transport project: Program review

This report summarizes the Integrated Application of Active Controls (IAAC) Technology to an Advanced Subsonic Transport Project, established as one element of the NASA/Boeing Energy Efficient Transport Technology Program. The performance assessment showed that incorporating ACT into an airplane designed to fly approximately 200 passengers approximately 2,000 nmi could yield block fuel savings from 6 to 10 percent at the design range. The principal risks associated with incorporating these active control functions into a commercial airplane are those involved with the ACT system implementation. The Test and Evaluation phase of the IAAC Project focused on the design, fabrication, and test of a system that implemented pitch axis fly-by-wire, pitch axis augmentation, and wing load alleviation. The system was built to be flight worthy, and was planned to be experimentally flown on the 757. The system was installed in the Boeing Digital Avionics Flight Controls Laboratory (DAFCL), where open loop hardware and software tests, and a brief examination of a direct drive valve (DDV) actuation concept were accomplished. The IAAC Project has shown that ACT can be beneficially incorporated into a commercial transport airplane. Based on the results achieved during the testing phase, there appears to be no fundamental reason(s) that would preclude the commercial application of ACT, assuming an appropriate development effort is included.

Source record↗

Adaptations of guidance, navigation, and control verification and validation philosophies for small spacecraft

Decades of experience developing increasingly capable and more complex space-craft have resulted in a set of accepted practices and philosophies to verify and validate (V&V) guidance, navigation, and control (GN&C) subsystems. Until recently, small, low-cost spacecraft have had very simple or non-existent GN&C subsystems requiring minimal or no subsystem testing. As the next generation of small spacecraft take on more challenging GN&C requirements, the GN&C community is struggling with how to scale the subsystem V&V effort to produce spacecraft approaching the reliability of flagship-class missions while staying within the reduced resources of a small satellite project.For this paper, we will examine five aspects of GN&C V&V (requirements definition, software testing and analysis, hardware component testing, integrated vehicle testing, and in-flight V&V) and compare the V&V campaign of a flagship-class mission (Mars 2020) to that of two recent, successful CubeSat missions: ASTERIA and MarCO. Experiences from the development of these CubeSats yield valuable lessons learned and guidelines for future small spacecraft designers.

Chen, George T.↗

Adaptations of Guidance, Navigation and Control Verification and Validation Philosophies for Small Spacecraft

Decades of experience developing increasingly capable and more complex space-craft have resulted in a set of accepted practices and philosophies to verify and validate (V&V) guidance, navigation, and control (GN&C) subsystems. Until recently, small, low-cost spacecraft have had very simple or non-existent GN&C subsystems requiring minimal or no subsystem testing. As the next generation of small spacecraft take on more challenging GN&C requirements, the GN&C community is struggling with how to scale the subsystem V&V effort to produce spacecraft approaching the reliability of flagship-class missions while staying within the reduced resources of a small satellite project. For this paper, we will examine five aspects of GN&C V&V (requirements definition, software testing and analysis, hardware component testing, integrated vehicle testing, and in-flight V&V) and compare the V&V campaign of a flagship-class mission (Mars 2020) to that of two recent, successful CubeSat missions: ASTERIA and MarCO. Experiences from the development of these CubeSats yield valuable lessons learned and guidelines for future small spacecraft designers.

Pong, Christopher M.↗

Flight problem evaluation for Space Shuttle Orbiter

The flight problems experienced with the reusable Space Shuttle Orbiter have decreased during subsequent flights of each vehicle. By comparison to first flights of previous vehicles, the problems encountered on the initial flight of each new vehicle entering the fleet decreased. This improvement in turn has reduced the turnaround time between flights significantly and thus greatly enhanced the increased Space Shuttle launch frequency. The reusable manned space vehicle concept necessitated the development of a flight problem recognition and resolution system which would enable a thorough and timely vehicle turnaround flow. Flight evaluation, testing, and repair of manned spacecraft to enhance reliability and to ensure mission success is a unique activity. Real-time recognition of the flight problem, prompt isolation of the cause, and timely implementation of the corrective action are the keys to maintaining an operational fleet. Examples of flight problems that have been encountered as well as the corrective actions implemented during the first 24 Space Shuttle missions are presented. The corrective actions taken to preclude problem recurrence include modifications of hardware designs, manufacturing processes, flight software, test methods, and operational procedures.

Mechelay, Joseph E.↗

SU-F-I-11: Software Development for 4D-CBCT Research of Real-Time-Image Gated Spot Scanning Proton Therapy

Purpose: To acquire correct information for inside the body in patient positioning of Real-time-image Gated spot scanning Proton Therapy (RGPT), utilization of tomographic image at exhale phase of patient respiration obtained from 4-dimensional Cone beam CT (4D-CBCT) has been desired. We developed software named “Image Analysis Platform” for 4D-CBCT researches which has technique to segment projection-images based on 3D marker position in the body. The 3D marker position can be obtained by using two axes CBCT system at Hokkaido University Hospital Proton Therapy Center. Performance verification of the software was implemented. Methods: The software calculates 3D marker position retrospectively by using matching positions on pair projection-images obtained by two axes fluoroscopy mode of CBCT system. Log data of 3D marker tracking are outputted after the tracking. By linking the Log data and gantry-angle file of projection-image, all projection-images are equally segmented to spatial five-phases according to marker 3D position of SI direction and saved to specified phase folder. Segmented projection-images are used for CBCT reconstruction of each phase. As performance verification of the software, test of segmented projection-images was implemented for sample CT phantom (Catphan) image acquired by two axes fluoroscopy mode of CBCT. Dummy marker was added on the images. Motion of the marker was modeled to move in 3D space. Motion type of marker is sin4 wave function has amplitude 10.0 mm/5.0 mm/0 mm, cycle 4 s/4 s/0 s for SI/AP/RL direction. Results: The marker was tracked within 0.58 mm accuracy in 3D for all images, and it was confirmed that all projection-images were segmented and saved to each phase folder correctly. Conclusion: We developed software for 4D-CBCT research which can segment projection-image based on 3D marker position. It will be helpful to create high quality of 4D-CBCT reconstruction image for RGPT.

60 APPLIED LIFE SCIENCES↗

Impact Damage and Strain Rate Effects for Toughened Epoxy Composite Structures

Structural integrity of composite systems under dynamic impact loading is investigated herein. The GENOA virtual testing software environment is used to implement the effects of dynamic loading on fracture progression and damage tolerance. Combinations of graphite and glass fibers with a toughened epoxy matrix are investigated. The effect of a ceramic coating for the absorption of impact energy is also included. Impact and post impact simulations include verification and prediction of (1) Load and Impact Energy, (2) Impact Damage Size, (3) Maximum Impact Peak Load, (4) Residual Strength, (5) Maximum Displacement, (6) Contribution of Failure Modes to Failure Mechanisms, (7) Prediction of Impact Load Versus Time, and (8) Damage, and Fracture Pattern. A computer model is utilized for the assessment of structural response, progressive fracture, and defect/damage tolerance characteristics. Results show the damage progression sequence and the changes in the structural response characteristics due to dynamic impact. The fundamental premise of computational simulation is that the complete evaluation of composite fracture requires an assessment of ply and subply level damage/fracture processes as the structure is subjected to loads. Simulation results for the graphite/epoxy composite were compared with the impact and tension failure test data, correlation and verification was obtained that included: (1) impact energy, (2) damage size, (3) maximum impact peak load, (4) residual strength, (5) maximum displacement, and (6) failure mechanisms of the composite structure.

Chamis, Christos C.↗

Improving system reliability through formal analysis and use of checks in software

Software is playing increasingly important roles in avionics systems. It is widely used in navigation and, in some cases, in control loops that maintain aircraft stability. To guarantee the safety of flight systems, the FAA requires that critical components have a probability of failure no greater than 10(exp -9) per hour of flight. Software is being used to diagnose system components for failure. SIFT (Software Implemented Fault Tolerance) was a computer system developed to study the use of software to check for failure and manage processor reconfiguration. To guarantee that software satisfies its specifications, formal verification can be used. With this a program and its specification are viewed as mathematical objects, and a mathematical proof is used to show that the program and its specification are equivalent. In previous research, a theory of checking was developed to offer assistance in analyzing specifications and designing run-time checks. In the theory, checking is considered abstractly in terms of n-ary relations much like those of relational database theory. Within the theory check are categorized, checks on input and checks on results are considered, and formal attention is given to the minimization and logical combination of checks. The focus is upon input checks and the obstacles in checking input to critical systems. A central concern is with a property referred to as independence. The concern is with circumstances under which it is possible to apply isolated, independent checks to separate sensor inputs and be assure that all illegal input will be properly detected. Presently, independence is being investigated and checked in the context of the GCS (Guidance and Control System). The GCS simulator is intended for testing software that implements control laws for landing spacecraft. The large number of inputs and their complex interrelationships provide an exciting context in which to investigate independence and the difficulties of supplying input checks.

Staknis, Mark E.↗

Development and Demonstration of an Ada Test Generation System

In this project we have built a prototype system that performs Feasible Path Analysis on Ada programs: given a description of a set of control flow paths through a procedure, and a predicate at a program point feasible path analysis determines if there is input data which causes execution to flow down some path in the collection reaching the point so that tile predicate is true. Feasible path analysis can be applied to program testing, program slicing, array bounds checking, and other forms of anomaly checking. FPA is central to most applications of program analysis. But, because this problem is formally unsolvable, syntactic-based approximations are used in its place. For example, in dead-code analysis the problem is to determine if there are any input values which cause execution to reach a specified program point. Instead an approximation to this problem is computed: determine whether there is a control flow path from the start of the program to the point. This syntactic approximation is efficiently computable and conservative: if there is no such path the program point is clearly unreachable, but if there is such a path, the analysis is inconclusive, and the code is assumed to be live. Such conservative analysis too often yields unsatisfactory results because the approximation is too weak. As another example, consider data flow analysis. A du-pair is a pair of program points such that the first point is a definition of a variable and the second point a use and for which there exists a definition-free path from the definition to the use. The sharper, semantic definition of a du-pair requires that there be a feasible definition-free path from the definition to the use. A compiler using du-pairs for detecting dead variables may miss optimizations by not considering feasibility. Similarly, a program analyzer computing program slices to merge parallel versions may report conflicts where none exist. In the context of software testing, feasibility analysis plays an important role in identifying testing requirements which are infeasible. This is especially true for data flow testing and modified condition/decision coverage. Our system uses in an essential way symbolic analysis and theorem proving technology, and we believe this work represents one of the few successful uses of a theorem prover working in a completely automatic fashion to solve a problem of practical interest. We believe this work anticipates an important trend away from purely syntactic-based methods for program analysis to semantic methods based on symbolic processing and inference technology. Other results demonstrating the practical use of automatic inference is being reported in hardware verification, although there are significant differences between the hardware work and ours. However, what is common and important is that general purpose theorem provers are being integrated with more special-purpose decision procedures to solve problems in analysis and verification. We are pursuina commercial opportunities for this work, and will use and extend the work in other projects we are engaged in. Ultimately we would like to rework the system to analyze C, C++, or Java as a key step toward commercialization.

Source record↗

A new fuel modeling capability, CTFFuel, with a case study on the fuel thermal conductivity degradation

Here, a new fuel modeling capability, CTFFuel, is developed from the subchannel code, CTF. This code is a standalone interface to the CTF fuel rod models, allowing for fuel rod simulations to be run independently from the fluid. This paper provides an overview of the code with a case study on the thermal conductivity degradation of LWR fuels to demonstrate its capabilities. The modeling of fuel thermal conductivity degradation in the code is improved through the addition of new modeling options to account for the irradiation effects via globally defined parameters. After the initial implementation, a variety of order-of-accuracy tests and code comparisons are performed to test software quality. A controlled analysis is allowed by CTFFuel to verify the numerical scheme of CTF’s conduction solution and to benchmark its fuel temperature predictions against FRAPCON-4.0’s. Overall, the software quality and verification procedure ensures that the new model is coded correctly, that it properly interacts with the rest of the code.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗