Search NASA⌕ Search

SEARCH · Search NASA

Results for “documentation”

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 271 records · Page 15
All sourcesNASA NTRSDOE OSTI
NASA NTRS2001

GEOSAT Follow-on (GFO) Altimeter Document Series: GFO Altimeter Engineering Assessment Report: From Launch to Acceptance, 10 February 1998 to 29 November 2000 - Volume 1

The US Navy's Geosat Follow-On (GFO) Mission, launched on February 10, 1998, is the latest in a series of altimetric satellites which include Seasat, Geosat, ERS-1, and TOPEX/POSEIDON (T/P). The purpose of this report is to document the GFO altimeter performance determined from the analyses and results performed by the NASA/GSFC/Wallops altimeter calibration team. It is the first of an anticipated series of NASA/GSFC/Wallops' GFO performance documents, each of which will update assessment results. This report covers the performance from launch to instrument acceptance by the Navy on November 29, 2000. Data derived from GFO will lead to improvements in the knowledge of ocean circulation, ice sheet topography, and climate change. In order to capture the maximum amount of information from the GFO data, accurate altimeter calibrations are required for the civilian data set which NOAA will produce. Wallops Flight Facility has provided similar products for the Geosat and T/P missions and is doing the same for GFO.

Hancock, David W., III↗
NASA NTRS2002

GEOSAT Follow-on (GFO) Altimeter Document Series: GFO Altimeter Engineering Assessment Report, Version 1 - Volume 3

The U.S. Navy's Geosat Follow-On (GFO) Mission, launched on February 20, 1998, is one of a series of altimetric satellites which include Seasat, Geosat, ERS-1, and TOPEX/POSEIDON (T/P). The purpose of this report is to document the GFO altimeter performance determined from the analyses and results performed by NASA's GSFC and Wallops altimeter, calibration team. It is the second of an anticipated series of NASA's GSFC and Wallops GFO performance documents, each of which will update assessment results. This report covers the performance from instrument acceptance by the Navy on November 29, 2000, to the end of Cycle 20 on November 21, 2001. Data derived from GFO will lead to improvements in the knowledge of ocean circulation, ice sheet topography, and climate change. In order to capture the maximum amount of information from the GFO data, accurate altimeter calibrations are required for the civilian data set which NOAA will produce. Wallops Flight Facility has provided similar products for the Geosat and T/P missions and is doing the same for GFO.

Hancock, David W., III↗
NASA NTRS2002

Intelligent Software for System Design and Documentation

In an effort to develop a real-time, on-line database system that tracks documentation changes in NASA's propulsion test facilities, engineers at Stennis Space Center teamed with ECT International of Brookfield, WI, through the NASA Dual-Use Development Program to create the External Data Program and Hyperlink Add-on Modules for the promis*e software. Promis*e is ECT's top-of-the-line intelligent software for control system design and documentation. With promis*e the user can make use of the automated design process to quickly generate control system schematics, panel layouts, bills of material, wire lists, terminal plans and more. NASA and its testing contractors currently use promis*e to create the drawings and schematics at the E2 Cell 2 test stand located at Stennis Space Center.

Source record↗
NASA NTRS2005

EXTENSIBLE DATABASE FRAMEWORK FOR MANAGEMENT OF UNSTRUCTURED AND SEMI-STRUCTURED DOCUMENTS

Method and system for querying a collection of Unstructured or semi-structured documents to identify presence of, and provide context and/or content for, keywords and/or keyphrases. The documents are analyzed and assigned a node structure, including an ordered sequence of mutually exclusive node segments or strings. Each node has an associated set of at least four, five or six attributes with node information and can represent a format marker or text, with the last node in any node segment usually being a text node. A keyword (or keyphrase) is specified. and the last node in each node segment is searched for a match with the keyword. When a match is found at a query node, or at a node determined with reference to a query node, the system displays the context andor the content of the query node.

Gawdiak, Yuri O.↗
NASA NTRS2006

GEOSAT Follow-On (GFO) Altimeter Document Series, Volume 8: GFO Altimeter Engineering Assessment Report Update:The First 109 Cycles Since Acceptance November 29, 2000 to December 26, 2005

The purpose of this document is to present and document GFO performance analyses and results. This is the fifth Assessment Report since the initial report. This report extends the performance assessment since acceptance to 26 December 2005. The initial GFO Altimeter Engineering Assessment Report, March 2001 (NASA/TM-2001-209984/Ver.1/Vol.1) covered the GFO performance from Launch to Acceptance (10 February 1998 to 29 November 2000). The second of the series covered the performance from Acceptance to the end of Cycle 20 (29 November 2000 to 21 November 2001). The third of the series covered the performance from Acceptance to the end of Cycle 42 (29 November 2000 to 30 November 2002). The fourth of the series covered the performance from Acceptance to the end of Cycle 64 (29 November 2000 to 17 December 2003). The fifth of the series covered performance from Acceptance to the end of Cycle 86 (29 November 2000 to 17 December 2004). Since launch, we have performed a variety of GFO performance studies; an accumulative index of those studies is provided in Appendix A.

Conger, A. M.↗
NASA NTRS2007

Policy Document on Earth Observation for Urban Planning and Management: State of the Art and Recommendations for Application of Earth Observation in Urban Planning

A policy document on earth observation for urban planning and management resulting from a workshop held in Hong Kong in November 2006 is presented. The aim of the workshop was to provide a forum for researchers and scientists specializing in earth observation to interact with practitioners working in different aspects of city planning, in a complex and dynamic city, Hong Kong. A summary of the current state of the art, limitations, and recommendations for the use of earth observation in urban areas is presented here as a policy document.

Nichol, Janet↗
NASA NTRS2008

Documentation for Three Wake Vortex Model Data Sets from Simulation of Flight 587 Wake Vortex Encounter Accident Case

This document contains a general description for data sets of a wake vortex system in a turbulent environment. The turbulence and thermal stratification of the environment are representative of the conditions on November 12, 2001 near John F. Kennedy International Airport. The simulation assumes no ambient winds. The full three dimensional simulation of the wake vortex system from a Boeing 747 predicts vortex circulation levels at 80% of their initial value at the time of the proposed vortex encounter. The linked vortex oval orientation showed no twisting, and the oval elevations at the widest point were about 20 meters higher than where the vortex pair joined. Fred Proctor of NASA?s Langley Research Center presented the results from this work at the NTSB public hearing that started 29 October 2002. This document contains a description of each data set including: variables, coordinate system, data format, and sample plots. Also included are instructions on how to read the data.

Switzer, George F.↗
NASA NTRS2007

Human Research Program Requirements Document

The purpose of this document is to define, document, and allocate the Human Research Program (HRP) requirements to the HRP Program elements. It establishes the flow-down of requirements from Exploration Systems Mission Directorate (ESMD) and Office of the Chief Health and Medical Officer (OCHMO) to the various Program Elements of the HRP to ensure that human research and technology countermeasure investments are made to insure the delivery of countermeasures and technologies that satisfy ESMD s and OCHMO's exploration mission requirements.

Rieger, Gabe↗
NASA NTRS2005

Contingency Management Requirements Document: Preliminary Version. Revision F

This is the High Altitude, Long Endurance (HALE) Remotely Operated Aircraft (ROA) Contingency Management (CM) Functional Requirements document. This document applies to HALE ROA operating within the National Airspace System (NAS) limited at this time to enroute operations above 43,000 feet (defined as Step 1 of the Access 5 project, sponsored by the National Aeronautics and Space Administration). A contingency is an unforeseen event requiring a response. The unforeseen event may be an emergency, an incident, a deviation, or an observation. Contingency Management (CM) is the process of evaluating the event, deciding on the proper course of action (a plan), and successfully executing the plan.

Source record↗
NASA NTRS2008

Tolerance and UQ4SIM: Nimble Uncertainty Documentation and Analysis Software

Ultimately, scientific numerical models need quantified output uncertainties so that modeling can evolve to better match reality. Documenting model input uncertainties and variabilities is a necessary first step toward that goal. Without known input parameter uncertainties, model sensitivities are all one can determine, and without code verification, output uncertainties are simply not reliable. The basic premise of uncertainty markup is to craft a tolerance and tagging mini-language that offers a natural, unobtrusive presentation and does not depend on parsing each type of input file format. Each file is marked up with tolerances and optionally, associated tags that serve to label the parameters and their uncertainties. The evolution of such a language, often called a Domain Specific Language or DSL, is given in [1], but in final form it parallels tolerances specified on an engineering drawing, e.g., 1 +/- 0.5, 5 +/- 10%, 2 +/- 10 where % signifies percent and o signifies order of magnitude. Tags, necessary for error propagation, can be added by placing a quotation-mark-delimited tag after the tolerance, e.g., 0.7 +/- 20% 'T_effective'. In addition, tolerances might have different underlying distributions, e.g., Uniform, Normal, or Triangular, or the tolerances may merely be intervals due to lack of knowledge (uncertainty). Finally, to address pragmatic considerations such as older models that require specific number-field formats, C-style format specifiers can be appended to the tolerance like so, 1.35 +/- 10U_3.2f. As an example of use, consider figure 1, where a chemical reaction input file is has been marked up to include tolerances and tags per table 1. Not only does the technique provide a natural method of specifying tolerances, but it also servers as in situ documentation of model uncertainties. This tolerance language comes with a utility to strip the tolerances (and tags), to provide a path to the nominal model parameter file. And, as shown in [1], having the ability to quickly mark and identify model parameter uncertainties facilitates error propagation, which in turn yield output uncertainties.

Kleb, Bil↗
NASA NTRS2009

Human Research Program Requirements Document (Revision C)

The purpose of this document is to define, document, and allocate the Human Research Program (HRP) requirements to the HRP Program Elements. It establishes the flow-down of requirements from Exploration Systems Mission Directorate (ESMD) and Office of the Chief Health and Medical Officer (OCHMO) to the various Program Elements of the HRP to ensure that human research and technology countermeasure investments are made to insure the delivery of countermeasures and technologies that satisfy ESMD's and OCHMO's exploration mission requirements. Requirements driving the HRP work and deliverables are derived from the exploration architecture, as well as Agency standards regarding the maintenance of human health and performance. Agency human health and performance standards will define acceptable risk for each type and duration of exploration mission. It is critical to have the best available scientific and clinical evidence in setting and validating these standards. In addition, it is imperative that the best available evidence on preventing and mitigating human health and performance risks is incorporated into exploration mission and vehicle designs. These elements form the basis of the HRP research and technology development requirements and highlight the importance of HRP investments in enabling NASA's exploration missions. This PRD defines the requirements of the HRP which is comprised of the following major Program Elements: Behavioral Health and Performance (BHP), Exploration Medical Capability (ExMC), Human Health Countermeasures (HHC), ISS Medical Project (ISSMP), Space Human Factors and Habitability (SHFH), and Space Radiation (SR).

Vargas, Paul R.↗
NASA NTRS2003

Topography Experiment (TOPEX) Software Document Series Volume 7: TOPEX Mission Radar Altimeter Engineering Assessment Report, February 1994

This document describes the GSFC/WFF analysis of the on-orbit engineering data from the TOPEX radar altimeter, to establish altimeter performance. In accordance with Project guidelines, neither surface truth nor precision orbital data are used for the engineering assessment of the altimeter. The use of such data would imply not only a more intensive and complete performance evaluation, but also a calibration. Such evaluations and.calibrations are outside the scope of this document and will be presented in a separate Verification Report.

Hancock, David W., III↗
NASA NTRS2009

A Verification-Driven Approach to Traceability and Documentation for Auto-Generated Mathematical Software

Model-based development and automated code generation are increasingly used for production code in safety-critical applications, but since code generators are typically not qualified, the generated code must still be fully tested, reviewed, and certified. This is particularly arduous for mathematical and control engineering software which requires reviewers to trace subtle details of textbook formulas and algorithms to the code, and to match requirements (e.g., physical units or coordinate frames) not represented explicitly in models or code. Both tasks are complicated by the often opaque nature of auto-generated code. We address these problems by developing a verification-driven approach to traceability and documentation. We apply the AUTOCERT verification system to identify and then verify mathematical concepts in the code, based on a mathematical domain theory, and then use these verified traceability links between concepts, code, and verification conditions to construct a natural language report that provides a high-level structured argument explaining why and how the code uses the assumptions and complies with the requirements. We have applied our approach to generate review documents for several sub-systems of NASA s Project Constellation.

Denney, Ewen W.↗
NASA NTRS2010

International Space Station Mechanisms and Maintenance Flight Control Documentation and Training Development

International Space Station (ISS) crew and flight controller training documentation is used to aid in training operations. The Generic Simulations References SharePoint (Gen Sim) site is a database used as an aid during flight simulations. The Gen Sim site is used to make individual mission segment timelines, data, and flight information easily accessible to instructors. The Waste and Hygiene Compartment (WHC) training schematic includes simple and complex fluid schematics, as well as overall hardware locations. It is used as a teaching aid during WHC lessons for both ISS crew and flight controllers. ISS flight control documentation is used to support all aspects of ISS mission operations. The Quick Look Database and Consolidated Tool Page are imagery-based references used in real-time to help the Operations Support Officer (OSO) find data faster and improve discussions with the Flight Director and Capsule Communicator (CAPCOM). A Quick Look page was created for the Permanent Multipurpose Module (PMM) by locating photos of the module interior, labeling specific hardware, and organizing them in schematic form to match the layout of the PMM interior. A Tool Page was created for the Maintenance Work Area (MWA) by gathering images, detailed drawings, safety information, procedures, certifications, demonstration videos, and general facts of each MWA component and displaying them in an easily accessible and consistent format. Participation in ISS mechanisms and maintenance lessons, mission simulation On-the-Job Training (OJT), and real-time flight OJT was used as an opportunity to train for day-to-day operations as an OSO, as well as learn how to effectively respond to failures and emergencies during mission simulations and real-time flight operations.

Daugherty, Colin C.↗
NASA NTRS2010

Rotor Wake/Stator Interaction Noise Prediction Code Technical Documentation and User's Manual

This report documents the improvements and enhancements made by Pratt & Whitney to two NASA programs which together will calculate noise from a rotor wake/stator interaction. The code is a combination of subroutines from two NASA programs with many new features added by Pratt & Whitney. To do a calculation V072 first uses a semi-empirical wake prediction to calculate the rotor wake characteristics at the stator leading edge. Results from the wake model are then automatically input into a rotor wake/stator interaction analytical noise prediction routine which calculates inlet aft sound power levels for the blade-passage-frequency tones and their harmonics, along with the complex radial mode amplitudes. The code allows for a noise calculation to be performed for a compressor rotor wake/stator interaction, a fan wake/FEGV interaction, or a fan wake/core stator interaction. This report is split into two parts, the first part discusses the technical documentation of the program as improved by Pratt & Whitney. The second part is a user's manual which describes how input files are created and how the code is run.

Topol, David A.↗
NASA NTRS2009

Customer Communication Document

This procedure communicates to the Customers of the Automation, Robotics and Simulation Division (AR&SD) Dynamics Systems Test Branch (DSTB) how to obtain services of the Six-Degrees-Of-Freedom Dynamic Test System (SDTS). The scope includes the major communication documents between the SDTS and its Customer. It established the initial communication and contact points as well as provides the initial documentation in electronic media for the customer. Contact the SDTS Manager (SM) for the names of numbers of the current contact points.

Source record↗
NASA NTRS2011

Human Research Program Requirements Document. Human Research Program Revision E

This document defines, documents, and allocates the Human Research Program (HRP) requirements to the HRP Program Elements. It also establishes the flow of requirements from the Human Exploration and Operations Mission Directorate (HEOMD) and the Office of the Chief Health and Medical Officer (OCHMO) down to the various HRP Program Elements to ensure that human research and technology countermeasure investments support the delivery of countermeasures and technologies that satisfy HEOMD's and OCHMO's exploration mission requirements.

Vargas, Paul↗
NASA NTRS2008

REVEAL: Software Documentation and Platform Migration

The Research Environment for Vehicle Embedded Analysis on Linux (REVEAL) is reconfigurable data acquisition software designed for network-distributed test and measurement applications. In development since 2001, it has been successfully demonstrated in support of a number of actual missions within NASA s Suborbital Science Program. Improvements to software configuration control were needed to properly support both an ongoing transition to operational status and continued evolution of REVEAL capabilities. For this reason the project described in this report targets REVEAL software source documentation and deployment of the software on a small set of hardware platforms different from what is currently used in the baseline system implementation. This report specifically describes the actions taken over a ten week period by two undergraduate student interns and serves as a final report for that internship. The topics discussed include: the documentation of REVEAL source code; the migration of REVEAL to other platforms; and an end-to-end field test that successfully validates the efforts.

Wilson, Michael A.↗