Search NASA⌕ Search

SEARCH · Search NASA

Results for “evaluation requirements”

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 127 records · Page 7

Extreme Space Weather Events and Charging Hazard Assessments in Lunar Environments

The sunlit lunar surface charges to positive potentials with mean values of a few tens of volts where photoelectron currents dominate the charging process. In contrast, surfaces in darkness may charge to negative potentials on the order of a few hundred volts when the charging process is dominated by hot electron populations in the absence of solar photons. Recently, observations of electron beams measured by instruments on spacecraft in low lunar orbit have been interpreted as evidence for extreme lunar surface potentials exceeding a few kilovolts suggesting that lunar orbital and surface plasma environments may contain charging risks similar to geostationary orbit during extreme space weather conditions. Space system design for successful operation in a wide range of lunar environments will therefore require evaluation of charging hazards during extreme space weather conditions. We present results from a study of space weather environments conducted to obtained credible extreme charging environments for use in charging hazard assessments for lunar missions including extreme conditions encountered when the Moon is in the solar wind, the magnetosheath, and the Earth's magnetotail.

Minow, Joseph I.↗

Creating Interactive Graphical Overlays in the Advanced Weather Interactive Processing System Using Shapefiles and DGM Files

Graphical overlays can be created in real-time in the Advanced Weather Interactive Processing System (AWIPS) using shapefiles or Denver AWIPS Risk Reduction and Requirements Evaluation (DARE) Graphics Metafile (DGM) files. This presentation describes how to create graphical overlays on-the-fly for AWIPS, by using two examples of AWIPS applications that were created by the Applied Meteorology Unit (AMU) located at Cape Canaveral Air Force Station (CCAFS), Florida. The first example is the Anvil Threat Corridor Forecast Tool, which produces a shapefile that depicts a graphical threat corridor of the forecast movement of thunderstorm anvil clouds, based on the observed or forecast upper-level winds. This tool is used by the Spaceflight Meteorology Group (SMG) at Johnson Space Center, Texas and 45th Weather Squadron (45 WS) at CCAFS to analyze the threat of natural or space vehicle-triggered lightning over a location. The second example is a launch and landing trajectory tool that produces a DGM file that plots the ground track of space vehicles during launch or landing. The trajectory tool can be used by SMG and the 45 WS forecasters to analyze weather radar imagery along a launch or landing trajectory. The presentation will list the advantages and disadvantages of both file types for creating interactive graphical overlays in future AWIPS applications. Shapefiles are a popular format used extensively in Geographical Information Systems. They are usually used in AWIPS to depict static map backgrounds. A shapefile stores the geometry and attribute information of spatial features in a dataset (ESRI 1998). Shapefiles can contain point, line, and polygon features. Each shapefile contains a main file, index file, and a dBASE table. The main file contains a record for each spatial feature, which describes the feature with a list of its vertices. The index file contains the offset of each record from the beginning of the main file. The dBASE table contains records for each attribute. Attributes are commonly used to label spatial features. Shapefiles can be viewed, but not created in AWIPS. As a result, either third-party software can be installed on an AWIPS workstation, or new software must be written to create shapefiles in the correct format.

Barrett, Joe H., III↗

Conceptual Drivers for an Exploration Medical System

Interplanetary spaceflight provides unique challenges that have not been encountered in prior spaceflight experience. Extended distance and timeframes introduce new challenges such as an inability to resupply medications and consumables, inability to evacuate injured or ill crew, and communication delays that introduce a requirement for some level of autonomous medical capability. Because of these challenges the approaches used in prior programs have limited application to a proposed three year Mars mission. This paper proposes a paradigm shift in the approach to medical risk mitigation for crew health and mission objectives threatened by inadequate medical capabilities in the setting of severely limited resources. A conceptual approach is outlined to derive medical system and vehicle needs from an integrated vision of how medical care will be provided within this new paradigm. Using NASA Design Reference Missions this process assesses each mission phase to deconstruct medical needs at any point during a mission. Two operational categories are proposed, nominal operations (pre-planned activities) and contingency operations (medical conditions requiring evaluation) that meld clinical needs and research needs into a single system. These definitions are used to derive a task level analysis to support quantifiable studies into a medical capabilities trade. This trade allows system design to proceed from both a mission centric and ethics-based approach to medical limitations in an exploration class mission.

Antonsen, E.↗

Traffic Management Coordinator Evaluation of the Dynamic Weather Routes Concept and System

Dynamic Weather Routes (DWR) is a weather-avoidance system for airline dispatchers and FAA traffic managers that continually searches for and advises the user of more efficient routes around convective weather. NASA and American Airlines (AA) have been conducting an operational trial of DWR since July 17, 2012. The objective of this evaluation is to assess DWR from a traffic management coordinator (TMC) perspective, using recently retired TMCs and actual DWR reroutes advisories that were rated acceptable by AA during the operational trial. Results from the evaluation showed that the primary reasons for a TMC to modify or reject airline reroute requests were related to airspace configuration. Approximately 80 percent of the reroutes evaluated required some coordination before implementation. Analysis showed TMCs approved 62 percent of the requested DWR reroutes, resulting in 57 percent of the total requested DWR time savings.

weather avoidance↗

Upgrades to Common Data Acquisition System Software Development for NASA's Rocket Propulsion Test Facilities and Software Reuse

Approximately five years ago, the National Aeronautics and Space Administration (NASA) Stennis Space Center (SSC) resumed operation of its large rocket engine test facilities after thirty years of contractor control. During this period, contactors used their own proprietary Data Acquisition System (DAS) to record and process rocket propulsion test data. The transition from a contractor managed facility to a NASA managed facility posed a difficult challenge. In order to support the commercial space launch initiative, SSC needed to develop a software replacement for the contractor proprietary DAS. This replacement software would enable SSC to operate propulsion test facilities more cost effectively and to be more readily able to adapt software for reuse, while at the same time provide internal and external customers with reliable population test data. Therefore, SSC developed in-house, a non-proprietary software suite of applications to replace the previously used proprietary DAS. The requirements for the DAS suite included recording and processing propulsion test data. This capability eliminates the necessity for customers to provide a DAS or rely on a competitor's DAS. An additional benefit of owning the software suite included enabling the ability to add additional features and functionality at a lower cost. The Rocket Propulsion Test (RPT) Program Office reviewed consideration for funding this project with the caveat that development of the software included availability for use with minimal modifications to all SSC test facilities and RPT centers: Marshall Space Flight Center (MSFC), White Sands Test Facility (WSTF), and Glenn Research Center (GRC) Plum Brook Station. Based upon this guideline, SSC created the NASA Data Acquisition System (NDAS) software suite. The ability to use the software at multiple centers, even though each field center uses differing DAS hardware with different capabilities, drove a requirement that the software design be portable with minimal modifications to the software. Then, with software release requirements, evaluations, and approvals completed, the NDAS software suite could also become available to other government agencies, corporations, universities, and the general United States public.

Herbert, Phillip W., Sr.↗

R2U2: Tool Overview

R2U2 (Realizable, Responsive, Unobtrusive Unit) is an extensible framework for runtime System HealthManagement (SHM) of cyber-physical systems. R2U2 can be run in hardware (e.g., FPGAs), or software; can monitorhardware, software, or a combination of the two; and can analyze a range of different types of system requirementsduring runtime. An R2U2 requirement is specified utilizing a hierarchical combination of building blocks: temporal formula runtime observers (in LTL or MTL), Bayesian networks, sensor filters, and Boolean testers. Importantly, the framework is extensible; it is designed to enable definitions of new building blocks in combination with the core structure. Originally deployed on Unmanned Aerial Systems (UAS), R2U2 is designed to run on a wide range of embedded platforms, from autonomous systems like rovers, satellites, and robots, to human-assistive ground systems and cockpits. R2U2 is named after the requirements it satisfies; while the exact requirements vary by platform and mission, the ability to formally reason about realizability, responsiveness, and unobtrusiveness is necessary for flight certifiability, safety-critical system assurance, and achievement of technology readiness levels for target systems. Realizability ensures that R2U2 is suficiently expressive to encapsulate meaningful runtime requirements while maintaining adaptability to run on different platforms, transition between different mission stages, and update quickly between missions. Responsiveness entails continuously monitoring the system under test, real-time reasoning, reporting intermediate status, and as-early-as-possible requirements evaluations. Unobtrusiveness ensures compliance with the crucial properties of the target architecture: functionality, certifiability, timing, tolerances, cost, or other constraints.

Rozier, Kristin Y.↗

Simulation and Flight Test Environments for the TASAR Traffic Aware Planner

The Traffic Aware Planner (TAP) software is a flight deck decision support tool that enhances the flight crew’s ability to make flight-optimizing route change requests while airborne. The software provides conflict-free, optimized trajectory suggestions during en route flight to produce time- and fuel-savings compared to the current trajectory. The TAP software requires evaluation in an operational environment with real pilot users to validate projected benefits. To this end, a set of developmental test environments have been developed to mature the software and mitigate technical risk prior to entering operational evaluation. The unique attributes of each test environment were leveraged to provide a range of purpose- and case-dependent TAP software tests. This paper describes the elements of a testing environment, discusses several environments of varying fidelity used to test the TAP software, and provides a review of two case studies highlighting the vital role testing played in the TAP software development process.

Barney, Terique L.↗

Quantifying Methane Leak Emissions by Fused Airborne Imaging Spectroscopy with in Situ Surface Mobile and Airborne Observations of a California Producing Oil Field

Methane (CH4) emission budgets remain uncertain and are projected to grow as oil and gas production from short-lived wells increases and their subsequent transport through aging gas distribution networks. Orders-of-magnitude variations in temporal, spatial, and emission scales present a key challenge to leak detection and quantification. Also, the probability distributions for large and stochastic, leaky systems such as geological reservoirs (by natural migration-seeps) and petroleum production from those reservoirs remain largely unknown, needed to address current approach limitations. The scale of many petroleum systems favors remote sensing, but the sensitivity of such systems often precludes detection of weak emissions. Consequently, an accurate evaluation requires that the relative contribution from the emission "tails" of small leaks also be quantified, which is best carried out using high-sensitivity in situ methods. Fusion of remote sensing and in situ approaches leverages complementary capabilities to address these limitations. We show results from mobile surface (AMOG) and airborne in situ (AJAX) and thermal-infrared (TIR) hyperspectral imaging spectroscopy (Mako) data applied to a producing oil field in the California Central Valley near Bakersfield. AMOG is an automobile-based mobile lab that measures 13 trace gases, aerosol size distributions and vertical profiles, 3D winds and other meteorology, and atmospheric column measurements by solar spectroscopy at highway speeds. AJAX measures 5 trace gases and 3D winds at ~140 m/s. Mako is a broad-area TIR imaging spectrometer that can discriminate multiple gases present in each pixel acquired. In situ-derived, total field emissions were 31±16 Gg/yr CH4. This was compared with Mako-derived emissions from all plumes identified across the study site. We found that super-emitters were not the dominant emissions mode and the spatial pattern of plume locations from production infrastructure was correlated to geological structures.

Leifer, Ira↗

TPSAS-NF1676L-12587-DND

Increased use of integral structures and sensory materials in new aerospace vehicles provides potential to reduce assembly time, reduce damage initiation features, and enhance identification of damage as compared to current built up structures. In this work the nondestructive evaluation requirements of these next generation materials and structures is examined. In particular, electromagnetic methods are explored for the characterization of residual stresses in integral structures and for the characterization embedded sensory alloy particles in an aluminum alloy matrix.

Russell A Wincheski↗

Survey of resource opportunities and critical evaluation of economic requirements

A series of mission analyses were performed to evaluate human mission to Mars and the moon with and without the aid of planetary resource utilization. The types of trade studies that are considered include the use of resources to manufacture propellant, food, habitat atmospheric gases, and lander habitat structure. Also, the potential for export of resources from the moon, Mars, Phobos, Deimos, and selected asteroids is also examined. In all cases, mass leveraging is evaluated. For certain cases, economic factors are evaluated as well. It is concluded that some uses are highly leveraging on the mission, whereas others have lesser impact and, therefore, should be afforded lesser priority in resource utilization studies. This survey is made with a consistent set of scaling laws for spacecraft propulsion and habitation systems and subsystems, and therefore, provides a rational basis for comparing different resource locations and use strategies.

Clark, Benton C.↗

Initial SVS Integrated Technology Evaluation Flight Test Requirements and Hardware Architecture

This document presents the flight test requirements for the Initial Synthetic Vision Systems Integrated Technology Evaluation flight Test to be flown aboard NASA Langley's ARIES aircraft and the final hardware architecture implemented to meet these requirements. Part I of this document contains the hardware, software, simulator, and flight operations requirements for this light test as they were defined in August 2002. The contents of this section are the actual requirements document that was signed for this flight test. Part II of this document contains information pertaining to the hardware architecture that was realized to meet these requirements as presented to and approved by a Critical Design Review Panel prior to installation on the B-757 Airborne Research Integrated Experiments Systems (ARIES) airplane. This information includes a description of the equipment, block diagrams of the architecture, layouts of the workstations, and pictures of the actual installations.

Harrison, Stella V.↗

Coverage Metrics for Requirements-Based Testing: Evaluation of Effectiveness

In black-box testing, the tester creates a set of tests to exercise a system under test without regard to the internal structure of the system. Generally, no objective metric is used to measure the adequacy of black-box tests. In recent work, we have proposed three requirements coverage metrics, allowing testers to objectively measure the adequacy of a black-box test suite with respect to a set of requirements formalized as Linear Temporal Logic (LTL) properties. In this report, we evaluate the effectiveness of these coverage metrics with respect to fault finding. Specifically, we conduct an empirical study to investigate two questions: (1) do test suites satisfying a requirements coverage metric provide better fault finding than randomly generated test suites of approximately the same size?, and (2) do test suites satisfying a more rigorous requirements coverage metric provide better fault finding than test suites satisfying a less rigorous requirements coverage metric? Our results indicate (1) only one coverage metric proposed -- Unique First Cause (UFC) coverage -- is sufficiently rigorous to ensure test suites satisfying the metric outperform randomly generated test suites of similar size and (2) that test suites satisfying more rigorous coverage metrics provide better fault finding than test suites satisfying less rigorous coverage metrics.

Staats, Matt↗

Analytic evaluation of display requirements for approach to landing

A pilot-vehicle-display model is used to study information and display requirements and the effects on system performance and reliability of pilot-induced randomness, wind gusts, configurational changes, etc. A brief description of a control theoretic systems model is given and its use and validity are demonstrated by applying it in a piloted approach to landing situation. The analysis procedure assumes that the vehicle dynamics are represented by linearized equations of motion.

Kleinman, D. L.↗

Apollo experience report: Ground-support equipment

The experience gained in management of the ground-support-equipment and site-readiness activity for the Apollo Program is summarized. The design of equipment and facilities are examined as well as some operational aspects. The organization for ensuring site readiness and the maintenance of ground-support equipment are discussed. Recommendations for use in future programs are given in the areas of design considerations, cleanliness requirements, periodic evaluation of changing requirements, maintenance and overhaul, special test equipment, site-activation schedule coordination, and schematics for ground-support equipment.

Cooper, J. S.↗

Some human factors issues in the development and evaluation of cockpit alerting and warning systems

A set of general guidelines for evaluating a newly developed cockpit alerting and warning system in terms of human factors issues are provided. Although the discussion centers around a general methodology, it is made specifically to the issues involved in alerting systems. An overall statement of the current operational problem is presented. Human factors problems with reference to existing alerting and warning systems are described. The methodology for proceeding through system development to system test is discussed. The differences between traditional human factors laboratory evaluations and those required for evaluation of complex man-machine systems under development are emphasized. Performance evaluation in the alerting and warning subsystem using a hypothetical sample system is explained.

Randle, R. J., Jr.↗

Solar disk sextant optical configuration

In this paper the performance of a plausible configuration for the solar disk sextant, an instrument to be used to monitor the solar diameter, is evaluated. Overall system requirements are evaluated, and tolerable uncertainties are obtained. It is concluded that by using a beam splitting wedge, a folded optics design can be used to measure the solar diameter to an accuracy of 10 to the -6th, despite the greater aberrations present in such optical systems.

Chiu, H.-Y.↗