Search NASA⌕ Search

SEARCH · Search NASA

Results for “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 199 records · Page 11

Europa Clipper Payload Verification and Validation: Early Architecture and Implementation

NASA’s Europa Clipper mission will investigate the Jovian icy moon Europa with a sophisticated payload consisting of a suite of nine instruments. Clipper’s observations will help provide answers to a broad range of scientific objectives related to Europa’s habitability. As the project proceeds through Phase C, we are building confidence in the system’s ability to achieve these science goals by implementing a rigorous payload verification and validation (V&V) program. This paper details the planned structure and implementation of the Europa Clipper payload V&V program as it exists leading up to the project critical design review (CDR), before the bulk of instrument- or payload- level V&V activities have begun. We first explain the context for payload V&V on Europa Clipper, including its interfaces with other parts of the project system. We then describe the taxonomy of V&V concepts and their interrelationships, followed by a discussion on how this framework allows us to codify interfaces, processes, and ideas that are key to a successful V&V program. We focus on key aspects of the planning phases of V&V, especially establishing a complete set of verification items and accurately mapping them into appropriate verification activities. The second half of the paper describes the logistics of implementing this framework onto our actual payload system, including the processes and tools we use to manage and communicate agreements, changes, and risks across the project. We conclude with a reflection on the unique drivers and challenges of the V&V program concept development so far and the work that is planned for phase D implementation.

Srivastava, Priyanka↗

Verification Testing and Veg-05 Tomato Crop Production on the International Space Station

Production of fresh, nutritious, and tasty produce for astronauts during spaceflight may provide health-promoting, bioavailable nutrients and enhance the dietary experience as we move into longer-duration missions. Growing and caring for plants may also reduce the psychological stresses associated with spaceflight and enhance connections to Earth. Requirements to consistently grow a diversity of crops under spaceflight environmental conditions remain poorly defined. The VEG-05 experiment is part of a series of experiments with pick-and-eat salad crops to better define best practices for crop production and handling in space. VEG-05 and predecessor experiments VEG-04A and VEG-04B, use the Veggie vegetable production facilities on the International Space Station to grow salad crops under different spectral compositions. In VEG-04A and B, mizuna mustard was cultivated with two different red: blue light treatments, and in VEG-05 we are cultivating ‘Red Robin’ dwarf cherry tomatoes under the same light spectra. Light can impact the growth habit, yield, nutritional composition, microbial levels, and even flavor attributes within crops, and our team will assess these characteristics for this crop during VEG-05. Prior to launch and installation on ISS in late 2022, both a science verification test (SVT), and an experiment verification test (EVT) were conducted at Kennedy Space Center in ISS Environment Simulator Chambers. Science verification testing, and a previous fertilizer test, grew plants in both plant pillows and PONDS (Passive Orbital Nutrient Delivery System) units and tested two different fertilizer treatments in both sets of hardware, with each test under only one of the light conditions. Because of challenges validating the PONDS hardware on ISS, and with good crop production in plant pillows, the EVT moved forward using only plant pillows with the highest fertilizer composition tested during SVT, and two Veggie units were utilized. One Veggie had light settings consisting of equal levels of red: blue light (150 µmol/m2/s for each color) plus green light (30 µmol/m2/s) while the second Veggie had a 90:10 ratio of red: blue light (270 µmol/m2/s red and 30 µmol/m2/s blue) plus green, so each unit provided 330 µmol/m2/s of photosynthetically active radiation to the tomato crops on average. Our original plan, based on prior ground testing, was to grow the crop for 104 days and harvest at 80, 90 and 104 days after initiation. For SVT, under the equal red: blue light treatment, fruit ripening in plant pillows was delayed and fruit were not ripe by day 80, so actual harvest days were days 90, 97, and 104. For EVT we saw fruit ripening earlier, especially in the high red treatment, and so we harvested at days 83, 90, and 99 days after initiation. In SVT we had mostly daily watering, and this led to excess water in plant pillows, which leaked out. This excess water also caused fungus to grow on one leaf and a couple of plant stems. To reduce this excess moisture, we throttled back the watering for EVT, and used the root mat reservoir more frequently. This led to watering only every other day, reducing crew time needed for plant care, however, two wilting events occurred during this EVT, at days 51 and 75. Plants recovered from these wilting events, but these events may have influenced the rate of fruit ripening and flower formation. Regardless, more than 10 fruit were produced from each plant on average, with the high red treatment producing slightly heavier fruit. Microbial testing from fruit during SVT indicated that fruit were safe for consumption with microbial levels below detection limits. VEG-05 flight and ground operations are expected to run between December 2022 and March 2023. This research was co-funded by the Human Research Program and Space Biology (MTL#1075) in the ILSRA 2015 NRA call.

Gioia D. Massa↗

Europa Clipper Payload Verification and Validation: Avionics-Instrument Interface Test Campaign

NASA's Europa Clipper mission will investigate Jupiter's icy moon Europa using a payload suite consisting of nine instruments to address a range of scientific objectives concerning Europa's habitability. As the project proceeds past its Critical Design Review, confidence is being built in the system's ability to achieve mission objectives through the implementation of a rigorous payload verification and validation (V&V) program. As part of this payload V&V program, instrument box-level testing was performed by the payload team to verify select instrument-avionics interface requirements. This testing was performed at JPL using the avionics testbed's Bulk Data Storage Emulator (BDSEM) with visiting instrument Test Models. This paper summarizes the Data Link test campaign involving roughly four days of functional testing per instrument, including planning, testing methods, types of issues found, and the requirement closure process. Detail is also provided on the development, deployment, and validation of a standardized analysis tool used in data reviews. This testing verified requirements related to commanding rates, loss of link, packet format, clock counters, loopback test capability, and SpaceWire jitter and skew margins. Additional risk reduction testing of basic commanding, counter behavior, science data collection and transfer, and interface swapping was also performed. Because the BDSEM venue was not originally designed to be a run for record venue, the process of characterizing venue fidelity and establishing suitability for requirement closure using data collected in this venue will also be addressed.In order to close requirements, an extensible tool was developed to post-process instrument command and telemetry data from their original binary to a human-readable format and give visibility to errors detected within the data, such as packets with Cyclic Redundancy Check errors. This tool, called payload-packet-parser, is a Python 3.9 command line tool built using a variety of open-source Python libraries. Payload-packet-parser was designed to support parsing command and telemetry packets for all Europa Clipper instruments and additional analysis tools were developed for verification of specific information interface requirements. This test campaign, including post-processing using a single parsing and verification toolset, allowed for early interface testing, alleviating testing burdens on instrument teams and buying down risk on the instrument-avionics interface by finding hardware and software issues and idiosyncrasies prior to integration with system test venues. Over twenty issues were discovered across the payload, resulting in software updates and instrument rework well in advance of any system impacts. This paper concludes with an assessment of benefits and costs of this type of testing and lessons learned.

Montanez, Leticia↗

Model-driven software verification

In this paper we explore a different approach to software verification. With this approach, a software application can be included, without substantial change, into a verification test-harness and then verified directly, while presearving the ability to apply data abstraction techniques. Only the test-harness is written in the language of the model checker.

software verification↗

Revisiting Training and Verification Process Implementation for Risk Reduction on New Missions at NASA Jet Propulsion Laboratory

In 2003 we proposed an effort to develop a core program of standardized training and verification practices and standards against which the implementation of these practices could be measured. The purpose was to provide another means of risk reduction for deep space missions to preclude the likelihood of a repeat of the tragedies of the 1998 Mars missions. We identified six areas where the application of standards and standardization would benefit the overall readiness process for flight projects at JPL. These are Individual Training, Team Training, Interface and Procedure Development, Personnel Certification, Interface and procedure Verification, and Operations Readiness Testing. In this paper we will discuss the progress that has been made in the tasks of developing the proposed infrastructure in each of these areas. Specifically we will address the Position Training and Certification Standards that are now available for each operational position found on our Flight Operations Teams (FOT). We will also discuss the MGSS Baseline Flight Operations Team Training Plan which can be tailored for each new flight project at JPL. As these tasks have been progressing, the climate and emphasis for Training and for V and V at JPL has changed, and we have learned about the expansion, growth, and limitations in the roles of traditional positions at JPL such as the Project's Training Engineer, V and V Engineer, and Operations Engineer. The need to keep a tight rein on budgets has led to a merging and/or reduction in these positions which pose challenges to individual capacities and capabilities. We examine the evolution of these processes and the roles involved while taking a look at the impact or potential impact of our proposed training related infrastructure tasks. As we conclude our examination of the changes taking place for new flight projects, we see that the importance of proceeding with our proposed tasks and adapting them to the changing climate remains an important element in reducing the risk in the challenging business of space exploration.

verifications↗

A Design Rationale Capture Tool to Support Design Verification and Re-use

A design rationale tool (DR tool) was developed to capture design knowledge to support design verification and design knowledge re-use. The design rationale tool captures design drivers and requirements, and documents the design solution including: intent (why it is included in the overall design); features (why it is designed the way it is); information about how the design components support design drivers and requirements; and, design alternatives considered but rejected. For design verification purposes, the tool identifies how specific design requirements were met and instantiated within the final design, and which requirements have not been met. To support design re-use, the tool identifies which design decisions are affected when design drivers and requirements are modified. To validate the design tool, the design knowledge from the Taxiway Navigation and Situation Awareness (T-NASA; Foyle et al., 1996) system was captured and the DR tool was exercised to demonstrate its utility for validation and re-use.

design verification↗

SMAP Verification and Validation Project - Final Report

In 2007, the National Research Council (NRC) released the Decadal Survey of Earth science. In the future decade, the survey identified 15 new space missions of significant scientific and application value for the National Aeronautics and Space Administration (NASA) to undertake. One of these missions was the Soil Moisture Active Passive (SMAP) mission that NASA assigned to the Jet Propulsion Laboratory (JPL) in 2008. The goal of SMAP1 is to provide global, high resolution mapping of soil moisture and its freeze/thaw states. The SMAP project recently passed its Critical Design Review and is proceeding with its fabrication and testing phase.Verification and Validation (V&V) is widely recognized as a critical component in system engineering and is vital to the success of any space mission. V&V is a process that is used to check that a system meets its design requirements and specifications in order to fulfill its intended purpose. Verification often refers to the question "Have we built the system right?" whereas Validation asks "Have we built the right system?" Currently the SMAP V&V team is verifying design requirements through inspection, demonstration, analysis, or testing. An example of the SMAP V&V process is the verification of the antenna pointing accuracy with mathematical models since it is not possible to provide the appropriate micro-gravity environment for testing the antenna on Earth before launch.

Soil Moisture Active Passive (SMAP)↗

Runtime Verification with State Estimation

We introduce the concept of Runtime Verification with State Estimation and show how this concept can be applied to estimate theprobability that a temporal property is satisfied by a run of a program when monitoring overhead is reduced by sampling. In such situations, there may be gaps in the observed program executions, thus making accurate estimation challenging. To deal with the effects of sampling on runtime verification, we view event sequences as observation sequences of a Hidden Markov Model (HMM), use an HMM model of the monitored program to "fill in" sampling-induced gaps in observation sequences, and extend the classic forward algorithm for HMM state estimation (which determines the probability of a state sequence, given an observation sequence) to compute the probability that the property is satisfied by an execution of the program. To validate our approach, we present a case study based on the mission software for a Mars rover. The results of our case study demonstrate high prediction accuracy for the probabilities computed by our algorithm. They also show that our technique is much more accurate than simply evaluating the temporal property on the given observation sequences, ignoring the gaps.

sampling↗

Verification of Triple Modular Redundancy Insertion for Reliable and Trusted Systems

If a system is required to be protected using triple modular redundancy (TMR), improper insertion can jeopardize the reliability and security of the system. Due to the complexity of the verification process and the complexity of digital designs, there are currently no available techniques that can provide complete and reliable confirmation of TMR insertion. We propose a method for TMR insertion verification that satisfies the process for reliable and trusted systems.

Verification↗

Verification of Viscous Goal-Based Anisotropic Mesh Adaptation

Adaptive unstructured mesh techniques have a limited, but growing impact on production analysis workflows where the control of discretization error is critical to obtaining reliable simulation results. Recent progress has matured a number of independent implementations of flow solvers, error estimation methods, and anisotropic mesh adaptation mechanics. Anisotropic metric construction methods are evaluated with analytically defined primal and adjoint fields. This allows the comparison of different metric formulations and different implementations of the same formulation without the complications of a flow and adjoint solution method. Unstructured mesh adaptation tools are verified by comparison on analytic primal and dual field before verification on benchmark aerodynamics cases. The documentation of these verification exercises helps to prepare these goal-based methods for routine use in production simulation workflows.

Mesh adaptation↗

Verification of Viscous Goal-Based Anisotropic Mesh Adaptation

Adaptive unstructured mesh techniques have a limited, but growing impact on production analysis workflows where the control of discretization error is critical to obtaining reliable simulation results. Recent progress has matured a number of independent implementations of flow solvers, anisotropic metric construction methods, and anisotropic mesh adaptation mechanics. A key ingredient for the broader acceptance of unstructured mesh adaptation is the verification of these implementations. Anisotropic metric construction methods are evaluated with analytically defined primal fields and the corresponding entropy variables as adjoint fields. This allows the comparison of different metric formulations and different implementations of the same formulation without the complications of a flow and adjoint solution method. The convergence of the output associated with the entropy variable adjoint is studied for mesh adaptation to these fields and a manufactured solution. Mesh adapted drag output is studied for two simple wings in compressible laminar flow to show fine-mesh convergence of multiple metric construction methods to less than a single drag count. The documentation of these verification exercises helps to prepare these goal-based methods for routine use in more complex simulations for production workflows.

mesh adaptation↗

Verification Test Suite for Spalart-Allmaras QCR2000 Turbulence Model

The paper presents three benchmark cases for verification of Reynolds-averaged Navier-Stokes solvers. The verification studies focus on a one-equation Spalart-Allmaras model, SA-[neg]-QCR2000, that uses a version of quadratic constitutive relations.The benchmark cases are a two-dimensional subsonic flow around a Joukowski airfoil, a three-dimensional supersonic flow through a square duct, and a three-dimensional flow over a wing-fuselage configuration. The turbulence-model formulation, geometry, flow conditions, grids, and the expected output are described in detail. Reference solutions computed by several established codes are shown

Computational Aerodynamics↗

Overview of the TOPEX/Poseidon Platform Harvest Verification Experiment

An overview is given of the in situ measurement system installed on Texaco's Platform Harvest for verification of the sea-level measurement from the TOPEX/POSEIDON satellite. The pre-launch error budget suggested that the total root mean square (RMS) error due to measurements made at this verification site would be less than four centimeters.

satellite↗

Runtime Verification with Ogma

Ultra-critical systems require high-level assurance, which cannot always be guaranteed in compile time. The use of runtime verification (RV) enable monitoring these systems in runtime, to detect property violations early and limit their potential consequences. However, the introduction of monitors in ultra-critical systems poses a challenge, as failures and delays in the RV subsystem could affect other subsystems and threaten the mission as a whole. In this talk we discuss two systems: NASA's Ogma, a tool to transform high-level specifications into monitoring code, and Copilot, a runtime verification framework for real-time embedded systems. The toolchain can be used to translate structured natural language requirements into C code with static memory requirements, which can be compiled to run on embedded hardware.

Ogma↗

Automated Verification of Programmable Logic Controller Programs Against Structured Natural Language Requirements

PLCverif is an actively developed project at CERN, enabling the formal verification of Programmable Logic Controller (PLC) programs in critical systems. In this paper, we present our work on improving the formal requirements specification experience in PLCverif through the use of natural language. To this end, we integrate NASA’s FRET, a formal requirement elicitation and authoring tool, into PLCverif. FRET is used to specify formal requirements in structured natural language, which automatically translates into temporal logic formulae. FRET’s output is then directly used by PLCverif for verification purposes. We discuss practical challenges that PLCverif users face when authoring requirements and the FRET features that help alleviate these problems. We present the new requirement formalization workflow and report our experience using it on two critical CERN case studies.

formal methods↗

Recent Progress on Rans-Based Transition Model Verification

The current efforts to assess and improve the Reynolds-averaged Navier-Stokes (RANS)-coupled transition models in the NASA FUN3D and OVERFLOW codes are summarized in this study. The first AIAA Transition Modeling Workshop and the NATO AVT-313 Transition Workshop both emphasized the need for code verification for transport equations based transition models as a top priority. We discuss the methods used for the model verification, the resulting grid families, the flow solutions, and other supporting information collected with at least two established NASA flow solvers, namely, FUN3D and OVERFLOW. These results, which will be uploaded onto the NASA Turbulence Modeling Resource, should assist other members of the computational fluid dynamics (CFD) community in verifying their own implementations of various transition models, such as the Langtry-Menter (LM2009) model, the one-equation γ model, and Coder’s amplification factor transport (AFT) model. Grid convergence is assessed using both global and local flow metrics of interest such as lift and drag as well as local skin-friction coefficients. We also explore the anisotropic unstructured metric-based adaptive mesh refinement library known as refine with the NASA FUN3D solver to determine if this capability can achieve the same accuracy as handcrafted structured grids with a significantly smaller node count and to learn the characteristics of the resulting grid distribution, especially in the vicinity of the transition zone.

Transition↗

Runtime Verification with Ogma

Ultra-critical systems require high-level assurance, which cannot always be guaranteed in compile time. The use of runtime verification (RV) enable monitoring these systems in runtime, to detect property violations early and limit their potential consequences. However, the introduction of monitors in ultra-critical systems poses a challenge, as failures and delays in the RV subsystem could affect other subsystems and threaten the mission as a whole. In this talk we discuss two systems: NASA's Ogma, a tool to transform high-level specifications into monitoring code, and Copilot, a runtime verification framework for real-time embedded systems. The toolchain can be used to translate structured natural language requirements into C code with static memory requirements, which can be compiled to run on embedded hardware.

Ogma↗

The Roman Space Telescope Optical System: Status, Test, and Verification

The Nancy Grace Roman Space Telescope (“Roman”) was prioritized by the 2010 Decadal Survey in Astronomy & Astrophysics and is NASA’s next flagship observatory. Launching no earlier than 2026, Roman will explore the nature of dark energy, as well as expand the census of exoplanets in our galaxy via microlensing. Roman will also demonstrate key technology needed to image and spectrally characterize extra-solar planets. Roman’s large field of view, agile survey capabilities, and excellent stability enable these scientific objectives, yet present unique challenges for the design, test, and verification of its optical system. The Roman optical system comprises an optical telescope assembly (OTA) and two instruments: the primary science wide-field instrument (WFI) and a technology demonstration coronagraph instrument (CGI), and the instrument carrier (IC), which meters the OTA to each instrument. This paper presents a status of the optical system hardware as it begins integration and test (I&T), as well as describes key optical test, alignment, and verification activities as part of the I&T program.

space telescope↗