Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “program verification”

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 919 records · Page 51

Lunar Natural Environment for use by the Constellation Program

The Lunar Environments used by the Constellation Program are embodied in two documents, the NEDD (Natural Environments Definition for Design) and the DSNE (Design Specification for Natural Environments). Recently, the lunar environments for the NEDD have been defined and incorporated in the document, as the result of contributions from experts in all areas of lunar environments. The purpose of the NEDD is to provide a uniform description of the natural environment to serve as a basic framework for both the crewed and robotic missions of the Exploration Systems Mission Directorate (ESMD). It is intended to support engineering and analysis, requirements development, and verification involved in the development of exploration concepts and architectures, flight hardware, and new technologies. (It does not support the operational phases of the Program since models and data with different properties are needed for those applications.) By presenting a single benchmark definition of natural environment parameters it provides an easily accessible and uniform baseline for competitive studies, independent analyses, and concept studies.

Ferguson, Dale C.↗

The Hyper-X Flight Systems Validation Program

For the Hyper-X/X-43A program, the development of a comprehensive validation test plan played an integral part in the success of the mission. The goal was to demonstrate hypersonic propulsion technologies by flight testing an airframe-integrated scramjet engine. Preparation for flight involved both verification and validation testing. By definition, verification is the process of assuring that the product meets design requirements; whereas validation is the process of assuring that the design meets mission requirements for the intended environment. This report presents an overview of the program with emphasis on the validation efforts. It includes topics such as hardware-in-the-loop, failure modes and effects, aircraft-in-the-loop, plugs-out, power characterization, antenna pattern, integration, combined systems, captive carry, and flight testing. Where applicable, test results are also discussed. The report provides a brief description of the flight systems onboard the X-43A research vehicle and an introduction to the ground support equipment required to execute the validation plan. The intent is to provide validation concepts that are applicable to current, follow-on, and next generation vehicles that share the hybrid spacecraft and aircraft characteristics of the Hyper-X vehicle.

Redifer, Matthew↗

Space Shuttle Day-of-Launch Trajectory Design and Verification

A top priority of any launch vehicle is to insert as much mass into the desired orbit as possible. This requirement must be traded against vehicle capability in terms of dynamic control, thermal constraints, and structural margins. The vehicle is certified to a specific structural envelope which will yield certain performance characteristics of mass to orbit. Some envelopes cannot be certified generically and must be checked with each mission design. The most sensitive envelopes require an assessment on the day-of-launch. To further minimize vehicle loads while maximizing vehicle performance, a day-of-launch trajectory can be designed. This design is optimized according to that day s wind and atmospheric conditions, which will increase the probability of launch. The day-of-launch trajectory verification is critical to the vehicle's safety. The Day-Of-Launch I-Load Uplink (DOLILU) is the process by which the Space Shuttle Program redesigns the vehicle steering commands to fit that day's environmental conditions and then rigorously verifies the integrated vehicle trajectory's loads, controls, and performance. The Shuttle methodology is very similar to other United States unmanned launch vehicles. By extension, this method would be similar to the methods employed for any future NASA launch vehicles. This presentation will provide an overview of the Shuttle's day-of-launch trajectory optimization and verification as an example of a more generic application of dayof- launch design and validation.

Harrington, Brian E.↗

Apollo experience report: Guidance and control systems. Engineering simulation program

The Apollo Program experience from early 1962 to July 1969 with respect to the engineering-simulation support and the problems encountered is summarized in this report. Engineering simulation in support of the Apollo guidance and control system is discussed in terms of design analysis and verification, certification of hardware in closed-loop operation, verification of hardware/software compatibility, and verification of both software and procedures for each mission. The magnitude, time, and cost of the engineering simulations are described with respect to hardware availability, NASA and contractor facilities (for verification of the command module, the lunar module, and the primary guidance, navigation, and control system), and scheduling and planning considerations. Recommendations are made regarding implementation of similar, large-scale simulations for future programs.

Gilbert, D. W.↗

Verification and Validation of High Explosive Reactive Burn Models Implemented in LANL's EAP and LAP Code Base (FY2020 L2 Milestone MRT 7129) [Slides]

Advanced reactive burn models enable phenomena to be modeled that aren’t possible with programmed burn. Programmed burn propagates a burn front at a prescribed speed from a prescribed initiation point. Reactive burn uses the hydro variables (pressure, temperature, etc.) to determine when, how rapidly, and to what extent a zone detonates. This enables a completely new set of problems to be simulated. Our goal in this milestone has been to improve the usability of reactive burn modes. Thus, the closure criteria are: 1. Perform code and solution verification of the reactive burn models using appropriate solutions and simplified HE setups. 2. Perform validation assessments using small-scale experiments. 3. Evaluate sensitivities and quantify uncertainties due to model form variations and mesh dependencies.

45 MILITARY TECHNOLOGY, WEAPONRY, AND NATIONAL DEF↗

Requirements Description of EvaluateFlux

This report presents the modeling and simulation capabilities of Argonne National Laboratory’s EvaluateFlux code [1] that is used in present reactor analysis activities. These capabilities will then be used to establish the set of EvaluateFlux verification tasks necessary to verify EvaluateFlux for usage on commercial projects. A similar approach was taken for the PERSENT, REBUS and DIF3D software packages. The EvaluateFlux program is a post-processing utility program for DIF3D, specifically DIF3D-VARIANT. As covered in [1], the EvaluateFlux program was built to allow users to obtain flux and power traverses through the domain. Its primary purpose was to facilitate foil analysis by evaluating the flux solution from DIF3D-VARIANT and combining it with foil cross section data. The outputs from EvaluateFlux are contained in four possible output files: FluxAndRegionRR.out, IsotopeMicroRR.out, LabeledRegionRR.out, and IsotopeMacroRR.out. Each file is focused on using the flux evaluate and cross section data in a different manner and all are covered in this verification process.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

Baseline Characterization Database Verification Report - NBG-18 Billet 635-14

The purpose of this Engineering Calculations and Analysis Report is to present the data being collected in the Baseline Graphite Characterization program, which is directly tasked with supporting the Idaho National Laboratory’s (INL’s) research and development efforts on the Next Generation Nuclear Plant (NGNP)/Very High Temperature Reactor (VHTR)/Advanced Reactor Technology (ART). This program is populating a comprehensive database that will reflect the baseline properties of nuclear-grade graphite regarding individual grade, billet, and position within individual billets. The physical and mechanical property information being collected will be transferred to the NGNP Data Management and Analysis System (NDMAS), and from that database will help populate handbook of property data available to member nations of the Generation IV International Forum (GIF).

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

ECAR-1930 BASELINE CHARACTERIZATION DATABASE VERIFICATION REPORT - NBG-18 BILLET 635-14

The purpose of this Engineering Calculations and Analysis Report is to present the data being collected in the Baseline Graphite Characterization program, which is directly tasked with supporting the Idaho National Laboratory’s (INL’s) research and development efforts on the Next Generation Nuclear Plant (NGNP)/Very High Temperature Reactor (VHTR). This program is populating a comprehensive database that will reflect the baseline properties of nuclear-grade graphite with regard to individual grade, billet, and position within individual billets. The physical and mechanical property information being collected will be transferred to the NGNP Data Management and Analysis System (NDMAS), and from that database will help populate handbook of property data available to member nations of the Generation IV International Forum (GIF). The transfer of this data from the applicable technical lead to the dissemination databases available to other end users requires a full review of the test procedures and data collection efforts through an analysis of the multiple summary spreadsheets and values being collected. This report represents that analysis for a single billet of nuclear grade graphite (NBG-18 billet 635-14) and facilitates the release of the associated data to the NDMAS custodians.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

Apollo experience report: Thermal protection subsystem

The Apollo command module was the first manned spacecraft to be designed to enter the atmosphere of the earth at lunar-return velocity, and the design of the thermal protection subsystem for the resulting entry environment presented a major technological challenge. Brief descriptions of the Apollo command module thermal design requirements and thermal protection configuration, and some highlights of the ground and flight testing used for design verification of the system are presented. Some of the significant events that occurred and decisions that were made during the program concerning the thermal protection subsystem are discussed.

Pavlosky, J. E.↗

Space station prototype Sabatier reactor design verification testing

A six-man, flight prototype carbon dioxide reduction subsystem for the SSP ETC/LSS (Space Station Prototype Environmental/Thermal Control and Life Support System) was developed and fabricated for the NASA-Johnson Space Center between February 1971 and October 1973. Component design verification testing was conducted on the Sabatier reactor covering design and off-design conditions as part of this development program. The reactor was designed to convert a minimum of 98 per cent hydrogen to water and methane for both six-man and two-man reactant flow conditions. Important design features of the reactor and test conditions are described. Reactor test results are presented that show design goals were achieved and off-design performance was stable.

Cusick, R. J.↗

Real time telemetry and data compression

The generation of telemetry and data compression by the flight program was verified. The adequacy of flight program telemetry control and timing is proven by the analysis of simulation laboratory runs of past programs through the use of telemetry. The telemetry data are correctly issued using specific tags called process input/output (P10) tags. Verification is accomplished by ensuring that a specific P10 tag and mode register setting identifies the correct parameter and that the data are properly scaled for subsequent ground station reduction. It was checked that the LVDC telemetry correctly adheres to the general requirements specified by the EDD. Data compression specifications are verified using compressed data from nominal flight simulations and from a series of perturbations designed to test data table overflows, data dump rates, and compression of data for occurrence events.

Source record↗

Large liquid rocket engine transient performance simulation system

Phase 1 of the Rocket Engine Transient Simulation (ROCETS) program consists of seven technical tasks: architecture; system requirements; component and submodel requirements; submodel implementation; component implementation; submodel testing and verification; and subsystem testing and verification. These tasks were completed. Phase 2 of ROCETS consists of two technical tasks: Technology Test Bed Engine (TTBE) model data generation; and system testing verification. During this period specific coding of the system processors was begun and the engineering representations of Phase 1 were expanded to produce a simple model of the TTBE. As the code was completed, some minor modifications to the system architecture centering on the global variable common, GLOBVAR, were necessary to increase processor efficiency. The engineering modules completed during Phase 2 are listed: INJTOO - main injector; MCHBOO - main chamber; NOZLOO - nozzle thrust calculations; PBRNOO - preburner; PIPE02 - compressible flow without inertia; PUMPOO - polytropic pump; ROTROO - rotor torque balance/speed derivative; and TURBOO - turbine. Detailed documentation of these modules is in the Appendix. In addition to the engineering modules, several submodules were also completed. These submodules include combustion properties, component performance characteristics (maps), and specific utilities. Specific coding was begun on the system configuration processor. All functions necessary for multiple module operation were completed but the SOLVER implementation is still under development. This system, the Verification Checkout Facility (VCF) allows interactive comparison of module results to store data as well as provides an intermediate checkout of the processor code. After validation using the VCF, the engineering modules and submodules were used to build a simple TTBE.

Mason, J. R.↗

1958 NASA/USAF Space Probes (ABLE-1): Payload and Experiments - Volume 2

The three NASA/USAF lunar probes of August 17, October 13, and November 8, 1958 are described. Details of the program, the vehicles, the payloads, the firings, the tracking, and the results are presented. Principal result was the first experimental verification of a confined radiation zone of the type postulated by Van Allen and others.

Source record↗

Evaluation of MPLM Design and Mission 6A Coupled Loads Analyses

Through the development of a space shuttle payload, there are usually several coupled loads analyses (CLA) performed: preliminary design, critical design, final design and verification loads analysis (VLA). A final design CLA is the last analysis conducted prior to model delivery to the shuttle program for the VLA. The finite element models used in the final design CLA and the VLA are test verified dynamic math models. Mission 6A is the first of many flights of the Multi-Purpose Logistics Module (MPLM). The MPLM was developed by Alenia Spazio S.p.A. (an Italian aerospace company) and houses the International Standard Payload Racks (ISPR) for transportation to the space station in the shuttle. Marshall Space Flight Center (MSFC), the payload integrator of the MPLM for Mission 6A, performed the final design CLA using the M6.OZC shuttle data for liftoff and landing conditions using the proper shuttle cargo manifest. Alenia performed the preliminary and critical design CLAs for the development of the MPLM. However, these CLAs did not use the current Mission 6A cargo manifest. An evaluation of the preliminary and critical design performed by Alenia and the final design performed by MSFC is presented.

Bookout, Paul S.↗

Ground Based Microgravity Emissions Testing Of Flight Hardware

To control microgravity environment on the International Space Station (ISS), NASA developed payloads have to meet the payload integration requirements of the Space Station Program, specifically a microgravity allocation plan. The Microgravity Emissions Laboratory (MEL) was developed at NASA Glenn Research Center (GRC) for verification of the payloads compliance with payload integration requirements. MEL is a 6 degree of freedom inertial measurement system capable of characterizing the microgravity emissions, generated by a disturber, down to a micro g. Microgravity Emissions tests provide a payload developer with a tool to assess payload's compliance with the requirements, i.e. forces and moments, generated by the payload at its center of gravity. Forces and moments are presented in time domain for both stationary and transient signals, and in frequency domain for the stationary signals. To date, MEL conducted over thirty tests of ISS hardware. The test results are being successfully used by the payload developers for design verification and improvement.

Samorezov, Sergey↗

Gas Flow Detection System

This system provides a portable means to detect gas flow through a thin-walled tube without breaking into the tubing system. The flow detection system was specifically designed to detect flow through two parallel branches of a manifold with only one inlet and outlet, and is a means for verifying a space shuttle program requirement that saves time and reduces the risk of flight hardware damage compared to the current means of requirement verification. The prototype Purge Vent and Drain Window Cavity Conditioning System (PVD WCCS) Flow Detection System consists of a heater and a temperature-sensing thermistor attached to a piece of Velcro to be attached to each branch of a WCCS manifold for the duration of the requirement verification test. The heaters and thermistors are connected to a shielded cable and then to an electronics enclosure, which contains the power supplies, relays, and circuit board to provide power, signal conditioning, and control. The electronics enclosure is then connected to a commercial data acquisition box to provide analog to digital conversion as well as digital control. This data acquisition box is then connected to a commercial laptop running a custom application created using National Instruments LabVIEW. The operation of the PVD WCCS Flow Detection System consists of first attaching a heater/thermistor assembly to each of the two branches of one manifold while there is no flow through the manifold. Next, the software application running on the laptop is used to turn on the heaters and to monitor the manifold branch temperatures. When the system has reached thermal equilibrium, the software application s graphical user interface (GUI) will indicate that the branch temperatures are stable. The operator can then physically open the flow control valve to initiate the test flow of gaseous nitrogen (GN2) through the manifold. Next, the software user interface will be monitored for stable temperature indications when the system is again at thermal equilibrium with the test flow of GN2. The temperature drop of each branch from its "no flow" stable temperature peak to its stable "with flow" temperature will allow the operator to determine whether a minimum level of flow exists. An alternative operation has the operator turning on the software only long enough to record the ambient temperature of the tubing before turning on the heaters and initiating GN2 flow. The stable temperature of the heated tubing with GN2 flow is then compared with the ambient tubing temperature to determine if flow is present in each branch. To help quantify the level of flow in the manifolds, each branch will be bench calibrated to establish its thermal properties using the flow detection system and different flow rates. These calibration values can then be incorporated into the software application to provide more detailed flow rate information.

Moss, Thomas↗

Application of a Density Law via Python for Aqueous Plutonium Nitrate

A predictive density tool has been developed in Python to reduce bias and uncertainty in nuclear criticality safety calculations for plutonium nitrate systems. The Pitzer Method and an empirical method were implemented into the tool, allowing for plutonium nitrate density calculations. Additionally, the Python tool can generate atom densities for a MCNP6.2 material card using the density from the selected method and directly the densities into a prepared MCNP6 input text file. The material card and density are calculated based on customizable user inputs of plutonium content, nitric acid content, temperature, plutonium isotope weight percentages and impurity concentrations. The Python tool has been validated and verified against the International Handbook of Evaluated Criticality Safety Benchmark Experiments to predict densities within a root mean square error of 1.0% for the Pitzer method and 1.8% for the empirical method. These errors in density were shown to lead to a ±0.5% error in MCNP6.2 calculated k effective for the Pitzer method and a ±1.7% error for the Empirical method. Simultaneous work is also being done at the University of New Mexico and Los Alamos National Laboratory to create a similar tool for plutonium chloride solutions, which aims to provide the accreditation of the chlorine absorption. These capabilities will not only provide more accurate models but also lead the way towards a better understanding of solution systems and potential relaxation in the conservatism of the current aqueous plutonium processing limits.

97 MATHEMATICS AND COMPUTING↗