SEARCH · Engineering Papers

Results for “software 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.

SourceResearch connectionFrom yearThrough year

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

At least 1,513 records · Page 84

All sources NASA NTRS DOE OSTI

NASA NTRSDate not supplied

X-57 Flight Systems Integration Path

The foundation for a safe and successful flight test of the National Aeronautics and Space Administration (NASA) X-57 Maxwell all-electric experimental airplane, or any X-Plane, is comprehensive system testing on the ground. This test campaign includes verification and validation (V&V) that the integrated system operates as designed and expected, as well as understanding how the system reacts and responds to failures that can occur during flight by performing failure modes and effects testing (FMET). The aircraft should be in the final flight configuration for these test activities because any modifications, even those that appear insignificant, could affect test outcomes. Although the plan was to perform V&V and FMET testing once the airplane was in the flight configuration, due to multiple component redesigns, concurrent software development, and other problems with on-aircraft testing, the X-57 Maxwell never made it into a full-flight configuration. As a result, a build-up approach was followed to test software and hardware as they became ready in order to continue making progress wherever possible. Using this approach revealed problems with the hardware and software faster than waiting for a full-flight configuration, allowing solutions to be found more quickly and in parallel with other project tasks. Other than unloaded motor testing in a lab setting, the only other test setup was on the airplane itself. On-aircraft testing was preferrable in order to test things as close to a flight configuration as possible but was time consuming due to the requirements for testing on the airplane. To overcome some of the on-aircraft barriers, off-aircraft test configurations, such as the Systems Integration Laboratory (SIL) and hardware-in-the-loop (HIL) setups, were used, but each of these setups had limitations to be considered. As a result, solutions found in the SIL or HIL configurations did not always work as expected on the airplane, resulting in an iterative process between on- and off-aircraft testing to find the final solution. Having a dedicated test platform such as an iron bird that closely represents the aircraft - without flight hardware - would have been the most effective off-aircraft test setup, which could have allowed the project to save time and money and potentially reach flight. This paper will highlight the V&V and FMET considerations and testing prerequisites, the build-up approaches to both software and system testing, the benefits and drawbacks to different test configurations, as well as battery testing and operations.

Kassidy McLaughlin↗

DOE OSTI2023

Modeling and Simulation of Fuel Burnup in Pebble Bed Reactors

Modeling and simulation of fuel burnup plays important roles in reactor design, operation, safety, and security as well as nuclear material control and accounting (MC&A) [1]. This task is uniquely challenging for pebble bed reactors (PBR) because the pebbles are continuously added and recycled into the reactor core, and their paths through the core are random. To address this problem, we present two simulation models in this paper. Brookhaven National Laboratory (BNL) developed a simple lattice model of a PBR in Serpent software to generate used pebble isotopic concentrations. The benefit of using Serpent software in this specific application is that it helps streamline the data generation process without having to use too many independent software codes in combination to achieve a simple task. For example, transport, burnup and zero power decay can be implemented in a single pass. Three-dimensional core models were developed using Serpent to simulate the burnup process of 5 subject pebbles starting from fresh till they reach nearly target burnup, with each pebble placed in one of the five artificially designated radial channels to capture the changing neutron spectra along the core radius. Equilibrium isotopic concentrations were assumed in all other pebbles in the core. To provide a verification for the Serpent isotope transmutation and decay results, Oak Ridge National Laboratory (ORNL) performed simple SCALE/ORIGEN calculations using the average neutron spectra calculated by Serpent for each of the 5 pebbles. The 252-group neutron spectra from Serpent were then used by ORIGEN to produce the one-group library for depletion and decay calculations. The isotopic concentrations of a few nuclides of interest and neutron and gamma source terms produced from the ORIGEN calculations were compared with the ones from the Serpent calculations. The model simulated in this work was based on the Pebble Bed Modular Reactor (PBMR)-400 design because many data needed for the simulation such as core power profiles, fuel and reflector temperatures, and equilibrium core composition are publicly available. In this paper, we will compare the results between these two approaches and benchmark the results against a set of well-established simulation results for PBMR-400.

Dim, Odera↗

DOE OSTI2023

Modeling and Simulation of Fuel Burnup in Pebble Bed Reactors

Modeling and simulation of fuel burnup plays important roles in reactor design, operation, safety, and security as well as nuclear material control and accounting (MC&A) [1]. This task is uniquely challenging for pebble bed reactors (PBR) because the pebbles are continuously added and recycled into the reactor core, and their paths through the core are random. To address this problem, we present two simulation models in this paper. Brookhaven National Laboratory (BNL) developed a simple lattice model of a PBR in Serpent software to generate used pebble isotopic concentrations. The benefit of using Serpent software in this specific application is that it helps streamline the data generation process without having to use too many independent software codes in combination to achieve a simple task. For example, transport, burnup and zero power decay can be implemented in a single pass. Three-dimensional core models were developed using Serpent to simulate the burnup process of five subject pebbles starting from fresh till they reach nearly target burnup, with each pebble placed in one of the five artificially designated radial channels to capture the changing neutron spectra along the core radius. Equilibrium isotopic concentrations were assumed in all other pebbles in the core. To provide a verification for the Serpent isotope transmutation and decay results, Oak Ridge National Laboratory (ORNL) performed simple SCALE/ORIGEN calculations using the average neutron spectra calculated by Serpent for each of the five pebbles. The 252-group neutron spectra from Serpent were then used by ORIGEN to produce the one-group library for depletion and decay calculations. The isotopic concentrations of a few nuclides of interest and neutron and gamma source terms produced from the ORIGEN calculations were compared with the ones from the Serpent calculations. The model simulated in this work was based on the Pebble Bed Modular Reactor (PBMR)-400 design because many data needed for the simulation such as core power profiles, fuel and reflector temperatures, and equilibrium core composition are publicly available. In this paper, we will compare the results between these two approaches and benchmark the results against a set of well-established simulation results for PBMR-400.

98 NUCLEAR DISARMAMENT, SAFEGUARDS, AND PHYSICAL P↗

DOE OSTI2022

Development of a water source heat pump hardware-in-the-loop (HIL) testing facility for smart building applications

Over the last decade, the global fight against climate change through electrification has led to an increase in research on building heating, ventilation, and air conditioning (HVAC) systems that utilize intelligent control algorithms to provide demand-side grid service while maintaining the thermal comfort of building occupants. As the pivotalpoint between building electricity consumption and indoor thermal comfort, high-efficiency electrical heatpumps are at the center of these emerging studies, and various grid-interactive and occupant-comfort control algorithms have been developed for them. The impact of these algorithms on the heatpump operation andperformance under different weather, building load, and grid requests calls for investigation and verification via experimental tests with actual heat pumps integrated with real-time building and grid responses. This study presents a Water-Source Heat Pump Hardware-in-The-Loop (HIL) Test Facility developed with the capability to perform such tests. The hardware configuration for this testfacility introduces a hydronic system that emulates the conditions for the heat pump water-side, and a duct system that emulates conditions for the heat pump airside. Both data acquisition and emulator control are implemented through the National Instruments (NI) LabVIEW software running on an NI PXIplatform. The HIL mechanism based on the hardware-software integration that allows the testbed to communicate with a generic simulation environment is also discussed. Currently, the test facility setup includes a single heatpump and virtual building model in EnergyPlus coupled with an occupant behavioral model in MATLAB. Preliminary test results of the current setup demonstrate the building load emulator's ability to track the simulated gone temperature with a Root Mean Square Deviation (RSME) below 0.12°C (0.216°F). An uncertainty analysis based on sensor accuracies shows that the heat pump coefficient of performance (COP) can be measured with a relative uncertainty of 10.4% in cooling and 3.7% in heating. Apartfrom the current testing on a single heat pump, the test facility also provides the flexibility to include additional heat pumps to form a heat pump cluster, as well as coupling the heat pump with active thermal storage to provide enhanced demandflexibility.

Calfa, Caleb↗

NASA NTRS2021

T0TEM - T0 Test Evaluation Module Development and Verification

Transition temperature testing of ferritic steels evaluates the ductile to brittle transition temperature, where the behavior of the steel changes from controlled ductile tearing to uncontrollable brittle fracture. This testing is governed by ASTM (American Society of Testing and Materials) E1921 standard. The calculations and plots required by this standard are iterative in nature and require significant effort to produce by standard hand calculations. In addition to analysis of a complete data set, intermediate analysis during testing is beneficial to determine optimal test temperatures. Given the exhaustive nature of calculating the transition temperature, being able to quickly update target temperatures is a significant benefit to not only the quality of tests, but the number of required tests as well. T0 Test Evaluation Module (T0TEM) v1.5 is a software application created under the Layered Pressure Vessel (LPV) certification effort. To reduce the analysis time of transition temperature test data sets producedfor this effort, T0TEM was created to calculate the E1921 Master Curve along with all required data and validity checks. By creating this program, hundreds of hours of analysis time were saved. In addition, the creation of a standard program provided a significant improvement in the consistency with which results were reported. T0TEM also calculates the results and plots required for the E1921 inhomogeneity annex to determine whether a material behaves in a homogenous manner. This program was created by Levi Shelton and Cameron Bosley at NASA, with input and review from the E1921 committee. The results generated by T0TEM were compared to the validation data sets provided by ASTM with good concurrence. ASTM committee members have reviewed and applied T0TEM to other data sets with satisfactory results. T0TEM was originally released to the NASA Software Repository and publicly via SourceForge in May of 2020. Version 1.5 was released in April of 2021 with minor functionality updates and additional statistical analysis methods.

Levi Shelton↗

NASA NTRS1999

Synthetic Scene Generation of the Stennis V and V Target Range for the Calibration of Remote Sensing Systems

The verification and validation (V&V) target range developed at Stennis Space Center is a useful test site for the calibration of remote sensing systems. In this paper, we present a simple algorithm for generating synthetic radiance scenes or digital models of this target range. The radiation propagation for the target in the solar reflective and thermal infrared spectral regions is modeled using the atmospheric radiative transfer code MODTRAN 4. The at-sensor, in-band radiance and spectral radiance for a given sensor at a given altitude is predicted. Software is developed to generate scenes with different spatial and spectral resolutions using the simulated at-sensor radiance values. The radiometric accuracy of the simulation is evaluated by comparing simulated with AVIRIS acquired radiance values. The results show that in general there is a good match between AVIRIS sensor measured and MODTRAN predicted radiance values for the target despite the fact that some anomalies exist. Synthetic scenes provide a cost-effective way for in-flight validation of the spatial and radiometric accuracy of the data. Other applications include mission planning, sensor simulation, and trade-off analysis in sensor design.

Cao, Chang-Yong↗

NASA NTRS2004

Robust Requirements Tracing via Internet Search Technology: Improving an IV and V Technique

There are three major objectives to this phase of the work. (1) Improvement of Information Retrieval (IR) methods for Independent Verification and Validation (IV&V) requirements tracing. Information Retrieval methods are typically developed for very large (order of millions - tens of millions and more documents) document collections and therefore, most successfully used methods somewhat sacrifice precision and recall in order to achieve efficiency. At the same time typical IR systems treat all user queries as independent of each other and assume that relevance of documents to queries is subjective for each user. The IV&V requirements tracing problem has a much smaller data set to operate on, even for large software development projects; the set of queries is predetermined by the high-level specification document and individual requirements considered as query input to IR methods are not necessarily independent from each other. Namely, knowledge about the links for one requirement may be helpful in determining the links of another requirement. Finally, while the final decision on the exact form of the traceability matrix still belongs to the IV&V analyst, his/her decisions are much less arbitrary than those of an Internet search engine user. All this suggests that the information available to us in the framework of the IV&V tracing problem can be successfully leveraged to enhance standard IR techniques, which in turn would lead to increased recall and precision. We developed several new methods during Phase II; (2) IV&V requirements tracing IR toolkit. Based on the methods developed in Phase I and their improvements developed in Phase II, we built a toolkit of IR methods for IV&V requirements tracing. The toolkit has been integrated, at the data level, with SAIC's SuperTracePlus (STP) tool; (3) Toolkit testing. We tested the methods included in the IV&V requirements tracing IR toolkit on a number of projects.

Hayes, Jane↗

NASA NTRS2019

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.↗

NASA NTRS2005

Formal Safety Certification of Aerospace Software

In principle, formal methods offer many advantages for aerospace software development: they can help to achieve ultra-high reliability, and they can be used to provide evidence of the reliability claims which can then be subjected to external scrutiny. However, despite years of research and many advances in the underlying formalisms of specification, semantics, and logic, formal methods are not much used in practice. In our opinion this is related to three major shortcomings. First, the application of formal methods is still expensive because they are labor- and knowledge-intensive. Second, they are difficult to scale up to complex systems because they are based on deep mathematical insights about the behavior of the systems (t.e., they rely on the "heroic proof"). Third, the proofs can be difficult to interpret, and typically stand in isolation from the original code. In this paper, we describe a tool for formally demonstrating safety-relevant aspects of aerospace software, which largely circumvents these problems. We focus on safely properties because it has been observed that safety violations such as out-of-bounds memory accesses or use of uninitialized variables constitute the majority of the errors found in the aerospace domain. In our approach, safety means that the program will not violate a set of rules that can range for the simple memory access rules to high-level flight rules. These different safety properties are formalized as different safety policies in Hoare logic, which are then used by a verification condition generator along with the code and logical annotations in order to derive formal safety conditions; these are then proven using an automated theorem prover. Our certification system is currently integrated into a model-based code generation toolset that generates the annotations together with the code. However, this automated formal certification technology is not exclusively constrained to our code generator and could, in principle, also be integrated with other code generators such as RealTime Workshop or even applied to legacy code. Our approach circumvents the historical problems with formal methods by increasing the degree of automation on all levels. The restriction to safety policies (as opposed to arbitrary functional behavior) results in simpler proof problems that can generally be solved by fully automatic theorem proves. An automated linking mechanism between the safety conditions and the code provides some of the traceability mandated by process standards such as DO-178B. An automated explanation mechanism uses semantic markup added by the verification condition generator to produce natural-language explanations of the safety conditions and thus supports their interpretation in relation to the code. It shows an automatically generated certification browser that lets users inspect the (generated) code along with the safety conditions (including textual explanations), and uses hyperlinks to automate tracing between the two levels. Here, the explanations reflect the logical structure of the safety obligation but the mechanism can in principle be customized using different sets of domain concepts. The interface also provides some limited control over the certification process itself. Our long-term goal is a seamless integration of certification, code generation, and manual coding that results in a "certified pipeline" in which specifications are automatically transformed into executable code, together with the supporting artifacts necessary for achieving and demonstrating the high level of assurance needed in the aerospace domain.

Denney, Ewen↗

NASA NTRS2015

Flight Testing ALHAT Precision Landing Technologies Integrated Onboard the Morpheus Rocket Vehicle

A suite of prototype sensors, software, and avionics developed within the NASA Autonomous precision Landing and Hazard Avoidance Technology (ALHAT) project were terrestrially demonstrated onboard the NASA Morpheus rocket-propelled Vertical Testbed (VTB) in 2014. The sensors included a LIDAR-based Hazard Detection System (HDS), a Navigation Doppler LIDAR (NDL) velocimeter, and a long-range Laser Altimeter (LAlt) that enable autonomous and safe precision landing of robotic or human vehicles on solid solar system bodies under varying terrain lighting conditions. The flight test campaign with the Morpheus vehicle involved a detailed integration and functional verification process, followed by tether testing and six successful free flights, including one night flight. The ALHAT sensor measurements were integrated into a common navigation solution through a specialized ALHAT Navigation filter that was employed in closed-loop flight testing within the Morpheus Guidance, Navigation and Control (GN&C) subsystem. Flight testing on Morpheus utilized ALHAT for safe landing site identification and ranking, followed by precise surface-relative navigation to the selected landing site. The successful autonomous, closed-loop flight demonstrations of the prototype ALHAT system have laid the foundation for the infusion of safe, precision landing capabilities into future planetary exploration missions.

Carson, John M. III↗

NASA NTRS2004

Design and Experimental Verification of Deployable/Inflatable Ultra-Lightweight Structures

Because launch cost of a space structural system is often proportional to the launch volume and mass and there is no significant gravity in space, NASA's space exploration programs and various science missions have stimulated extensive use of ultra-lightweight deployable/inflatable structures. These structures are named here as Highly Flexible Structures (HFSs) because they are designed to undergo large displacements, rotations, and/or buckling without plastic deformation under normal operation conditions. Except recent applications to space structural systems, HFSs have been used in many mechanical systems, civil structures, aerospace vehicles, home appliances, and medical devices to satisfy space limitations, provide special mechanisms, and/or reduce structural weight. The extensive use of HFSs in today's structural engineering reveals the need of a design and analysis software and a database system with design guidelines for practicing engineers to perform computer-aided design and rapid prototyping of HFSs. Also to prepare engineering students for future structural engineering requires a new and easy-to- understand method of presenting the complex mathematics of the modeling and analysis of HFSs. However, because of the high flexibility of HFSs, many unique challenging problems in the modeling, design and analysis of HFSs need to be studied. The current state of research on HFSs needs advances in the following areas: (1) modeling of large rotations using appropriate strain measures, (2) modeling of cross-section warpings of structures, (3) how to account for both large rotations and cross- section warpings in 2D (two-dimensional) and 1D structural theories, (4) modeling of thickness thinning of membranes due to inflation pressure, pretension, and temperature change, (5) prediction of inflated shapes and wrinkles of inflatable structures, (6) development of efficient numerical methods for nonlinear static and dynamic analyses, and (7) filling the gap between geometrically exact elastic analysis and elastoplastic analysis. The objectives of this research project were: (1) to study the modeling, design, and analysis of deployable/inflatable ultra-lightweight structures, (2) to perform numerical and experimental studies on the static and dynamic characteristics and deployability of HFSs, (3) to derive guidelines for designing HFSs, (4) to develop a MATLAB toolbox for the design, analysis, and dynamic animation of HFSs, and (5) to perform experiments and establish an adequate database of post-buckling characteristics of HFSs.

Pai, P. Frank↗

NASA NTRS2019

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.↗

DOE OSTI2021

DAKOTA (Design Analysis Kit for Optimization and Terascale) v.6.14

Sandia's Dakota software supports science and engineering transformation through advanced exploration of simulations. Specifically, Dakota manages and analyzes ensembles of simulations to provide broader and deeper perspective for analysts and decision makers. This enables them to: (1) enhance understanding of risk, (2) improve products, and (3) assess simulation credibility. In its simplest mode, Dakota can automate typical parameter variation studies through a generic interface to a computational model. Dakota also delivers advanced parametric analysis techniques enabling design exploration, optimization, model calibration, risk analysis, and quantification of margins and uncertainty with such models. It directly supports verification and validation activities. The algorithms implemented in Dakota aim to address challenges in performing these analyses with complex science and engineering models from desktop to high performance computers. Sandia National Laboratories is a multimission laboratory managed and operated by National Technology & Engineering Solutions of Sandia, LLC, a wholly owned subsidiary of Honeywell International Inc., for the U.S. Department of Energy’s National Nuclear Security Administration under contract DE-NA0003525 SAND2021-10468 O

Adams, BrianM.↗

DOE OSTI2021

DAKOTA (Design Analysis Kit for Optimization and Terascale) v.6.16

Adams, BrianM.↗

DOE OSTI2015

Status Report on NEAMS System Analysis Module Development

Under the Reactor Product Line (RPL) of DOE-NE’s Nuclear Energy Advanced Modeling and Simulation (NEAMS) program, an advanced SFR System Analysis Module (SAM) is being developed at Argonne National Laboratory. The goal of the SAM development is to provide fast-running, improved-fidelity, whole-plant transient analyses capabilities. SAM utilizes an object-oriented application framework MOOSE), and its underlying meshing and finite-element library libMesh, as well as linear and non-linear solvers PETSc, to leverage modern advanced software environments and numerical methods. It also incorporates advances in physical and empirical models and seeks closure models based on information from high-fidelity simulations and experiments. This report provides an update on the SAM development, and summarizes the activities performed in FY15 and the first quarter of FY16. The tasks include: (1) implement the support of 2nd-order finite elements in SAM components for improved accuracy and computational efficiency; (2) improve the conjugate heat transfer modeling and develop pseudo 3-D full-core reactor heat transfer capabilities; (3) perform verification and validation tests as well as demonstration simulations; (4) develop the coupling requirements for SAS4A/SASSYS-1 and SAM integration.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗

NASA NTRS2010

Ares I-X Range Safety Simulation Verification and Analysis IV and V

NASA s ARES I-X vehicle launched on a suborbital test flight from the Eastern Range in Florida on October 28, 2009. NASA generated a Range Safety (RS) flight data package to meet the RS trajectory data requirements defined in the Air Force Space Command Manual 91-710. Some products included in the flight data package were a nominal ascent trajectory, ascent flight envelope trajectories, and malfunction turn trajectories. These data are used by the Air Force s 45th Space Wing (45SW) to ensure Eastern Range public safety and to make flight termination decisions on launch day. Due to the criticality of the RS data in regards to public safety and mission success, an independent validation and verification (IV&V) effort was undertaken to accompany the data generation analyses to ensure utmost data quality and correct adherence to requirements. Multiple NASA centers and contractor organizations were assigned specific products to IV&V. The data generation and IV&V work was coordinated through the Launch Constellation Range Safety Panel s Trajectory Working Group, which included members from the prime and IV&V organizations as well as the 45SW. As a result of the IV&V efforts, the RS product package was delivered with confidence that two independent organizations using separate simulation software generated data to meet the range requirements and yielded similar results. This document captures ARES I-X RS product IV&V analysis, including the methodology used to verify inputs, simulation, and output data for an RS product. Additionally a discussion of lessons learned is presented to capture advantages and disadvantages to the IV&V processes used.

Tarpley, Ashley↗

NASA NTRS2011

Ares I-X Range Safety Analyses Overview

Ares I-X was the first test flight of NASA's Constellation Program's Ares I Crew Launch Vehicle designed to provide manned access to low Earth orbit. As a one-time test flight, the Air Force's 45th Space Wing required a series of Range Safety analysis data products to be developed for the specified launch date and mission trajectory prior to granting flight approval on the Eastern Range. The range safety data package is required to ensure that the public, launch area, and launch complex personnel and resources are provided with an acceptable level of safety and that all aspects of prelaunch and launch operations adhere to applicable public laws. The analysis data products, defined in the Air Force Space Command Manual 91-710, Volume 2, consisted of a nominal trajectory, three sigma trajectory envelopes, stage impact footprints, acoustic intensity contours, trajectory turn angles resulting from potential vehicle malfunctions (including flight software failures), characterization of potential debris, and debris impact footprints. These data products were developed under the auspices of the Constellation's Program Launch Constellation Range Safety Panel and its Range Safety Trajectory Working Group with the intent of beginning the framework for the operational vehicle data products and providing programmatic review and oversight. A multi-center NASA team in conjunction with the 45th Space Wing, collaborated within the Trajectory Working Group forum to define the data product development processes, performed the analyses necessary to generate the data products, and performed independent verification and validation of the data products. This paper outlines the Range Safety data requirements and provides an overview of the processes established to develop both the data products and the individual analyses used to develop the data products, and it summarizes the results of the analyses required for the Ares I-X launch.

Starr, Brett R.↗

NASA NTRS2011

Ares I-X Range Safety Flight Envelope Analysis

Starr, Brett R.↗