SEARCH · Search NASA
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.
Explore the source record for details and available documents.
High-resolution spectra of H 2 16 O were recorded with a Fourier-transform spectrometer covering transitions in the (100)-(010), (001)-(010), (100)-(000), and (001)-(000) bands. The measured line frequencies were used to determine high accuracy values of rotational energy levels in the (100) and (001) vibrational states. The experimental results provide a more accurate representation of the line positions and strengths than those presently available for these bands.
The Sedna Planitia Quadrangle (V-19) extend from 25 deg N - 50 deg N latitude, 330 deg - 0 deg longitude. The quadrangle contains the northern-most portion of western Eistla Regio and the Sedna Planitia lowlands. Geologic maps of Sedna Planitia (V-199), Hecate Chasma (V-28) quadrangles have been completed at the 1:5,000,000 scale as part of the NASA Planetary Geologic Mapping Program. All quadrangles (V-53, V-28 and V-19) have been reviewed at lease once and will be resubmitted. In V-28 and V-53, more plains materials units have been mapped than in previously mapped quadrangles V-46 and V-39. V-19 is more comparable to these latter maps in terms of numbers of plains units. In V-28, all of the plains materials units to the south of the rift have an unusually high concentration of volcanic edifices, which both predate and postdate the units. A similar situation is seen in V-53 and V-19, where small edifice formation is not confined to any specific time period. In the two chasma-related quadrangles, coronae are located along the rift, as well as to the north and the south of the rifts. Coronae in both quadrangles exhibit all forms of corona topographic shapes, including depressions, rimmed depressions, plateaus and domes. In V-28 and V-53, some coronae along the rift do not have much associated volcanism; coronae with the most volcanism in these quadrangles are located at least 500 km off the rifts or on the Themis Regio highland. All three quadrangles have very horizontal stratigraphic columns, as limited contact between units prevents clear age determinations. While this results in the appearance that all units formed at the same time, the use of hachured columns for each unit illustrates the limited nature of our stratigraphic knowledge in these quadrangles, allowing for numerous possible geologic histories. The scale of resurfacing in these quadrangles is on the scale of 100s of kilometers, consistent with the fact that they lie in the most volcanic region of Venus.
This report is in answer to the Nuclear Criticality Safety Program FY24 quarter 4 milestone that requires: “Format and V&V nu-bar means and covariances” for 238,240-242 Pu average prompt fission neutron multiplicities, $\overline{ν}$ p , that were obtained by a consistent evaluation leveraging the fission-event generator CGMF and a detailed uncertainty quantification of experimental data. It is described how nuclear data mean values and covariances were formatted using ENDFtk. Implementing the new 238,240-242 Pu $\overline{ν}$ p into the ENDF/B-VIII.1β 4 library leads to only small overall changes in criticality values of the Jezebel, Dirty Jezebel, Jupiter-001, Jupiter-002, EUCLID 3x2 and EUCLID 8x1 critical assemblies. Simulated k eff uncertainties due to $\overline{ν}$ p covariances change only little if cross-isotope covariances are considered or not for those assemblies with low percentage content of minor Pu isotopes. However, for the Dirty Jezebel critical assembly, that has a sizeable 240 Pu and non-negligible 241 Pu content, the simulated k eff uncertainties due to considering or neglecting cross-isotope $\overline{ν}$ p covariances is 443 versus 374 pcm.
Physiological responses and work capacity studies conducted during cosmonaut training and space flights
Explore the source record for details and available documents.
Knowledge Based Systems (KBS's) are expected to be heavily used in the Space Station Freedom Program (SSFP). Although SSFP Verification and Validation (V&V) requirements are based on the latest state-of-the-practice in software engineering technology, they may be insufficient for Knowledge Based Systems (KBS's); it is widely stated that there are differences in both approach and execution between KBS V&V and conventional software V&V. In order to better understand this issue, we have surveyed and/or interviewed developers from sixty expert system projects in order to understand the differences and difficulties in KBS V&V. We have used this survey results to analyze the SSFP V&V requirements for conventional software in order to determine which specific requirements are inappropriate for KBS V&V and why they are inappropriate. Further work will result in a set of recommendations that can be used either as guidelines for applying conventional software V&V requirements to KBS's or as modifications to extend the existing SSFP conventional software V&V requirements to include KBS requirements. The results of this work are significant to many projects, in addition to SSFP, which will involve KBS's.
NASA has established a far-reaching and long-term program for robotic and manned exploration of the solar system, beginning with missions to the moon and Mars. The Crew Transportation System (CTS), a key system for space exploration, imposes four requirements' that ISHM addresses. These requirements have a wide range of implications for V&V and certification of ISHM. There is a range of time-criticality for ISHM actions, from prognostication, which is often (but not always) non-time-critical, to time-critical state estimation and system management under off-nominal emergency conditions. These are externally imposed requirements on ISHM that are subject to V&V. - In addition, a range of techniques are needed to implement an ISHM. The approaches to ISHM are described elsewhere. These approaches range from well-understood algorithms for low-level data analysis, validation and reporting, to AI techniques for state estimation and planning. The range of techniques, and specifically the use of AI techniques such as reasoning under uncertainty and mission planning (and re-planning), implies that several V&V approaches may be required. Depending on the ISHM architecture, traditional testing approaches may be adequate for some ISHM functionality. The AI-based approaches to reasoning under uncertainty, model-based reasoning, and planning share characteristics typical of other complex software systems, but they also have characteristics that set them apart and challenge standard V&V techniques. The range of possible solutions to the overall ISHM problem impose internal challenges to V&V. The V&V challenges increase when hard real-time constraints are imposed for time-critical functionality. For example, there is an external requirement that impending catastrophic failure of the Launch Vehicle (LV) at launch time be detected and life-saving action be taken within two seconds. In this paper we outline the challenges for ISHM V&V, existing approaches and analogs in other software application areas, and possible new approaches to the V&V challenges for space exploration ISHM.
Verification and validation (V&V) is performed during application development for many systems, especially safety-critical and mission-critical systems. The V&V process is intended to discover errors, especially errors related to critical processing, as early as possible during the development process. Early discovery is important in order to minimize the cost and other impacts of correcting these errors. In order to provide early detection of errors, V&V is conducted in parallel with system development, often beginning with the concept phase. In reuse-based software engineering, however, decisions on the requirements, design and even implementation of domain assets can be made prior to beginning development of a specific system. In this case, V&V must be performed during domain engineering in order to have an impact on system development. This paper describes a framework for performing V&V within architecture-centric, reuse-based software engineering. This framework includes the activities of traditional application-level V&V, and extends these activities into domain engineering and into the transition between domain engineering and application engineering. The framework includes descriptions of the types of activities to be performed during each of the life-cycle phases, and provides motivation for the activities.
This paper describes the role of Verification and Validation (V&V) during the requirements and high level design processes, and in particular the role of Independent V&V (IV&V). The job of IV&V during these phases is to ensure that the requirements are complete, consistent and valid, and to ensure that the high level design meets the requirements. This contrasts with the role of Quality Assurance (QA), which ensures that appropriate standards and process models are defined and applied. This paper describes the current state of practice for IV&V, concentrating on the process model used in NASA projects. We describe a case study, showing the processes by which problem reporting and tracking takes place, and how IV&V feeds into decision making by the development team. We then describe the problems faced in implementing IV&V. We conclude that despite a well defined process model, and tools to support it, IV&V is still beset by communication and coordination problems.
Verification and validation (V&V) is used to increase the level of assurance of critical software, particularly that of safety-critical and mission critical software. This paper describes the working group's success in identifying V&V tasks that could be performed in the domain engineering and transition levels of reuse-based software engineering. The primary motivation for V&V at the domain level is to provide assurance that the domain requirements are correct and that the domain artifacts correctly implement the domain requirements. A secondary motivation is the possible elimination of redundant V&V activities at the application level. The group also considered the criteria and motivation for performing V&V in domain engineering.
The purpose of this report is to describe current NASA Verification and Validation (V&V) techniques and to explain how these techniques are applicable to 2nd Generation RLV Integrated Vehicle Health Management (IVHM) software. It also contains recommendations for special V&V requirements for IVHM. This report is divided into the following three sections: 1) Survey - Current NASA V&V Processes/Methods; 2) Applicability of NASA V&V to 2nd Generation RLV IVHM; and 3) Special 2nd Generation RLV IVHM V&V Requirements.
The purpose of this report is to provide correctness and reliability criteria for verification and validation (V&V) of Second Generation Reusable Launch Vehicle (RLV) Diagnostic Modeling Environment, describe current NASA Ames Research Center tools for V&V of Model Based Reasoning systems, and discuss the applicability of Advanced V&V to DME. This report is divided into the following three sections: (1) correctness and reliability criteria; (2) tools for V&V of Model Based Reasoning; and (3) advanced V&V applicable to DME. The Executive Summary includes an overview of the main points from each section. Supporting details, diagrams, figures, and other information are included in subsequent sections. A glossary, acronym list, appendices, and references are included at the end of this report.
Rigorous Verification and Validation (V&V) techniques are essential for high assurance systems. Lately, the performance of some of these systems is enhanced by embedded adaptive components in order to cope with environmental changes. Although the ability of adapting is appealing, it actually poses a problem in terms of V&V. Since uncertainties induced by environmental changes have a significant impact on system behavior, the applicability of conventional V&V techniques is limited. In safety-critical applications such as flight control system, the mechanisms of change must be observed, diagnosed, accommodated and well understood prior to deployment. In this paper, we propose a non-conventional V&V approach suitable for online adaptive systems. We apply our approach to an intelligent flight control system that employs a particular type of Neural Networks (NN) as the adaptive learning paradigm. Presented methodology consists of a novelty detection technique and online stability monitoring tools. The novelty detection technique is based on Support Vector Data Description that detects novel (abnormal) data patterns. The Online Stability Monitoring tools based on Lyapunov's Stability Theory detect unstable learning behavior in neural networks. Cases studies based on a high fidelity simulator of NASA's Intelligent Flight Control System demonstrate a successful application of the presented V&V methodology. ,
This paper describes the results of a special breakout session of the NASA Independent Verification and Validation (IV&V) Workshop held in the fall of 2012 entitled "V&V of Fault Management: Challenges and Successes." The NASA IV&V Program is in a unique position to interact with projects across all of the NASA development domains. Using this unique opportunity, the IV&V program convened a breakout session to enable IV&V teams to share their challenges and successes with respect to the V&V of Fault Management (FM) architectures and software. The presentations and discussions provided practical examples of pitfalls encountered while performing V&V of FM including the lack of consistent designs for implementing faults monitors and the fact that FM information is not centralized but scattered among many diverse project artifacts. The discussions also solidified the need for an early commitment to developing FM in parallel with the spacecraft systems as well as clearly defining FM terminology within a project.
Orientation‐patterned (OP) III–V semiconductors—used as quasi‐phase‐matched crystals for nonlinear optics applications—are typically epitaxially grown on expensive III–V substrates using a complex process requiring three separate epitaxy steps. In this work, a method is demonstrated for growing orientation‐patterned III–V crystals on Si substrates through V‐groove nanopatterning and a single epitaxial growth. V‐groove Si allows for suppression of random antiphase domain formation that is typical of III–V growth on (001)‐oriented Si through the use of (111)‐faceted trenches patterned on (001)‐oriented Si substrates. By alternating the directions of the V‐groove trenches between [110] and [10], antiphase boundaries can be selectively induced at the boundaries between the two directions of trenches due to the difference in symmetry between the III–V material and Si. This approach allows for a greatly simplified process for growing OP‐III‐Vs and more broadly is a new, robust approach for precisely patterning antiphase boundaries of arbitrary shape and length scales down to 50 nm.
Verification and Validation (V&V) is performed during application development for many systems, especially safety-critical and mission-critical systems. The V&V process is intended to discover errors as early as possible during the development process. Early discovery is important in order to minimize the cost and other impacts of correcting these errors. In reuse-based software engineering, decisions on the requirements, design and even implementation of domain assets can can be made prior to beginning development of a specific system. in order to bring the effectiveness of V&V to bear within reuse-based software engineering. V&V must be incorporated within the domain engineering process.
Verification and Validation (V&V) is used to increase the level of assurance of critical software, particularly that of safety-critical and mission-critical software. V&V is a systems engineering discipline that evaluates the software in a systems context, and is currently applied during the development of a specific application system. In order to bring the effectiveness of V&V to bear within reuse-based software engineering, V&V must be incorporated within the domain engineering process.