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 1,693 records · Page 94
All sourcesNASA NTRSDOE OSTI
NASA NTRS1998

Analysis of Lidar Remote Sensing Concepts

An orbiting coherent Doppler lidar for measuring winds is required to provide two basic pieces of data to the user community. The first is the line of sight wind velocity and the second is knowledge of the position at which the measurement was made. In order to obtain this data for targets of interest to the atmospheric community the instrument must also have a level of backscatter sensitivity sufficient to achieve the goal. Sensitivity analyses for the line of sight velocity and position requirements for two lidar instruments, one with a nadir angle of 30 deg. in a 300 km altitude, 58 deg. inclination orbit and the second for a 45 deg. nadir angle instrument in a 833 km altitude , 89 deg. inclination orbit are performed. The issues relating to the backscatter sensitivity of a coherent lidar have been well documented previously and are not discussed here other than to identify a space-specific issue that does not typically need to be considered for ground and aircraft based coherent lidars. Section 2 and appendices A1 and A2 document these sensitivity analyses. This contract was intended to develop requirements for a space shuttle (STS) based coherent lidar however, shortly after the award of this contract NASA MSFC won the SPARCLE program to put a coherent Doppler lidar on STS. Consequently much of the work conducted under this contract has been documented within the development of the SPARCLE project documentation. The relevant portions of the SPARCLE documentation are identified in section 3.0 and included in appendices A3 and A4. Section 4.0 briefly outlines miscellaneous other activities that occurred under this contract.

Spiers, Gray D.↗
NASA NTRS2003

TOPEX SDR Processing, October 1998

This document is a compendium of the WFF TOPEX Software Development Team's knowledge regarding Sensor Data Record (SDR) Processing. It includes many elements of a requirements document, a software specification document, a software design document, and a user's manual. In the more technical sections, this document assumes the reader is familiar with TOPEX and instrument files.

Lee, Jeffrey E.↗
NASA NTRS2004

Globe Teachers Guide and Photographic Data on the Web

The task of managing the GLOBE Online Teacher s Guide during this time period focused on transforming the technology behind the delivery system of this document. The web application transformed from a flat file retrieval system to a dynamic database access approach. The new methodology utilizes Java Server Pages (JSP) on the front-end and an Oracle relational database on the backend. This new approach allows users of the web site, mainly teachers, to access content efficiently by grade level and/or by investigation or educational concept area. Moreover, teachers can gain easier access to data sheets and lab and field guides. The new online guide also included updated content for all GLOBE protocols. The GLOBE web management team was given documentation for maintaining the new application. Instructions for modifying the JSP templates and managing database content were included in this document. It was delivered to the team by the end of October, 2003. The National Geophysical Data Center (NGDC) continued to manage the school study site photos on the GLOBE website. 333 study site photo images were added to the GLOBE database and posted on the web during this same time period for 64 schools. Documentation for processing study site photos was also delivered to the new GLOBE web management team. Lastly, assistance was provided in transferring reference applications such as the Cloud and LandSat quizzes and Earth Systems Online Poster from NGDC servers to GLOBE servers along with documentation for maintaining these applications.

Kowal, Dan↗
NASA NTRS2004

Proposed Plan for Adopting Updated Range Reference Atmospheres

The Terrestrial and Planetary Environments Team at Marshall Space Flight Center (MSFC) proposes to facilitate validation, documentation, and adoption of updated Range Reference Atmospheres (RRAs). This viewgraph presentation describes the plan, focusing on seven tasks: 1) Document data sources; 2) Document analytical models; 3) Document data processing procedures; 4) Compare updates to 1983 versions; 5) Compile written documentation; 6) Obtain approval for final volumes; 7) Publish new RRA datasets/documents.

Keller, Vernon↗
NASA NTRS2004

Realtime Knowledge Management (RKM): From an International Space Station (ISS) Point of View

We are developing automated methods to provide realtime access to spacecraft domain knowledge relevant a spacecraft's current operational state. The method is based upon analyzing state-transition signatures in the telemetry stream. A key insight is that documentation relevant to a specific failure mode or operational state is related to the structure and function of spacecraft systems. This means that diagnostic dependency and state models can provide a roadmap for effective documentation navigation and presentation. Diagnostic models consume the telemetry and derive a high-level state description of the spacecraft. Each potential spacecraft state description is matched against the predictions of models that were developed from information found in the pages and sections in the relevant International Space Station (ISS) documentation and reference materials. By annotating each model fragment with the domain knowledge sources from which it was derived we can develop a system that automatically selects those documents representing the domain knowledge encapsulated by the models that compute the current spacecraft state. In this manner, when the spacecraft state changes, the relevant documentation context and presentation will also change.

Robinson, Peter I.↗
NASA NTRS2004

Book Out! An Inventory Story

The NASA Glenn Library is a science and engineering research library providing the most current books, journals, CD-ROM's and documents to support the study of aeronautics, space propulsion and power, communications technology, materials and structures and microgravity science. The GRC technical library also supports the research and development efforts of all scientists and engineers on site via full text electronic files, literature searching, technical reports, etc. As an intern in the NASA Glenn Library, I attempt to support these objectives through efficiently and effectively fulfilling the assignment that was given to me. The assignment that was relegated to me was to catalog National Advisory Committee for Aeronautics, NASA Technical Documents into NASA Galaxie. This process consists of holdings being added to existing Galaxie records, upgrades and editing done to the bibliographic records when needed, adding URL's into Galaxie when they were missing from the record. NASA ASAP and Digidoc was used to locate URL's of PDF's that were not in Galaxie. A spreadsheet of documents with no URL's were maintained. Also, a subject channel of web, fill-text, paid and free, journal and other subject specific pages were developed and expanded fiom current content of intranet pages. To expand upon the second half of my assignment, I was given the project of taking inventory of the library s book collection. I kept record of the books that were not accounted for on a master list I was given to work fiom and submitted them for correction and addition. I also made sure the books were placed in the appropriate order and made corrections to any discrepancies that existed between the master list and what was on the shelf. Upon completion of this assignment, I will have verified that 21,113 books were in the correct location, order and have the correct corresponding serial number and barcode. In conclusion, as of this date I have input around 750 documents into NASA Galaxie, inputting about half of the NASA Technical Documents into the system. The rest of my tenure in this program will consist of finishing the other half of the reports. In regard to the second assignment, I still have about three-quarters of the collection to record and correct.

Panait, Claudia M.↗
NASA NTRS2004

Space Communications Emulation Facility

Establishing space communication between ground facilities and other satellites is a painstaking task that requires many precise calculations dealing with relay time, atmospheric conditions, and satellite positions, to name a few. The Space Communications Emulation Facility (SCEF) team here at NASA is developing a facility that will approximately emulate the conditions in space that impact space communication. The emulation facility is comprised of a 32 node distributed cluster of computers; each node representing a satellite or ground station. The objective of the satellites is to observe the topography of the Earth (water, vegetation, land, and ice) and relay this information back to the ground stations. Software originally designed by the University of Kansas, labeled the Emulation Manager, controls the interaction of the satellites and ground stations, as well as handling the recording of data. The Emulation Manager is installed on a Linux Operating System, employing both Java and C++ programming codes. The emulation scenarios are written in extensible Markup Language, XML. XML documents are designed to store, carry, and exchange data. With XML documents data can be exchanged between incompatible systems, which makes it ideal for this project because Linux, MAC and Windows Operating Systems are all used. Unfortunately, XML documents cannot display data like HTML documents. Therefore, the SCEF team uses XML Schema Definition (XSD) or just schema to describe the structure of an XML document. Schemas are very important because they have the capability to validate the correctness of data, define restrictions on data, define data formats, and convert data between different data types, among other things. At this time, in order for the Emulation Manager to open and run an XML emulation scenario file, the user must first establish a link between the schema file and the directory under which the XML scenario files are saved. This procedure takes place on the command line on the Linux Operating System. Once this link has been established the Emulation manager validates all the XML files in that directory against the schema file, before the actual scenario is run. Using some very sophisticated commercial software called the Satellite Tool Kit (STK) installed on the Linux box, the Emulation Manager is able to display the data and graphics generated by the execution of a XML emulation scenario file. The Emulation Manager software is written in JAVA programming code. Since the SCEF project is in the developmental stage, the source code for this type of software is being modified to better fit the requirements of the SCEF project. Some parameters for the emulation are hard coded, set at fixed values. Members of the SCEF team are altering the code to allow the user to choose the values of these hard coded parameters by inserting a toolbar onto the preexisting GUI.

Hill, Chante A.↗
NASA NTRS2006

Earth Observations and the Role of UAVs: A Capabilities Assessment

This three-volume document, based on the draft document located on the website given on page 6, presents the findings of a NASA-led capabilities assessment of Uninhabited Aerial Vehicles (UAVs) for civil (defined as non-DoD) use in Earth observations. Volume 1 is the report that presents the overall assessment and summarizes the data. The second volume contains the appendices and references to address the technologies and capabilities required for viable UAV missions. The third volume is the living portion of this effort and contains the outputs from each of the Technology Working Groups (TWGs) along with the reviews conducted by the Universities Space Research Association (USRA). The focus of this report, intended to complement the Office of the Secretary of Defense UAV Roadmap, is four-fold: 1) To determine and document desired future Earth observation missions for all UAVs based on user-defined needs; 2) To determine and document the technologies necessary to support those missions; 3) To discuss the present state of the art platform capabilities and required technologies, including identifying those in progress, those planned, and those for which no current plans exist; 4) Provide the foundations for development of a comprehensive civil UAV roadmap. It is expected that the content of this report will be updated periodically and used to assess the feasibility of future missions. In addition, this report will provide the foundation to help influence funding decisions to develop those technologies that are considered enabling or necessary but are not contained within approved funding plans. This document is written such that each section will be supported by an Appendix that will give the reader a more detailed discussion of that section's topical materials.

Cox, Timothy H.↗
NASA NTRS2006

Earth Observations and the Role of UAVs: A Capabilities Assessment

This document provides an assessment of the civil UAV missions and technologies and is intended to parallel the Office of the Secretary of Defense UAV Roadmap. The intent of this document is four-fold: 1. Determine and document desired future missions of Earth observation UAVs based on user-defined needs 2. Determine and document the technologies necessary to support those missions 3. Discuss the present state of the platform capabilities and required technologies, identifying those in progress, those planned, and those for which no current plans exist 4. Provide the foundations for development of a comprehensive civil UAV roadmap to complement the Department of Defense (DoD) effort (http://www.acq.osd.mil/uas/). Two aspects of the President's Management Agenda (refer to the document located at: www.whitehouse.gov/omb/budget/fy2002/mgmt.pdf ) are supported by this undertaking. First, it is one that will engage multiple Agencies in the effort as stakeholders and benefactors of the systems. In that sense, the market will be driven by the user requirements and applications. The second aspect is one of supporting economic development in the commercial sector. Market forecasts for the civil use of UAVs have indicated an infant market stage at present with a sustained forecasted growth. There is some difficulty in quantifying the value of the market since the typical estimate excludes system components other than the aerial platforms. Section 2.4 addresses the civil UAV market forecast and lists several independent forecasts. One conclusion that can be drawn from these forecasts is that all show a sustained growth for the duration of each long-term forecast.

Cox, Timothy H.↗
NASA NTRS2007

Model-Based Systems

Engineers, who design systems using text specification documents, focus their work upon the completed system to meet Performance, time and budget goals. Consistency and integrity is difficult to maintain within text documents for a single complex system and more difficult to maintain as several systems are combined into higher-level systems, are maintained over decades, and evolve technically and in performance through updates. This system design approach frequently results in major changes during the system integration and test phase, and in time and budget overruns. Engineers who build system specification documents within a model-based systems environment go a step further and aggregate all of the data. They interrelate all of the data to insure consistency and integrity. After the model is constructed, the various system specification documents are prepared, all from the same database. The consistency and integrity of the model is assured, therefore the consistency and integrity of the various specification documents is insured. This article attempts to define model-based systems relative to such an environment. The intent is to expose the complexity of the enabling problem by outlining what is needed, why it is needed and how needs are being addressed by international standards writing teams.

Frisch, Harold P.↗
NASA NTRS2006

HALE UAS Concept of Operations. Version 3.0

This document is a system level Concept of Operations (CONOPS) from the perspective of future High Altitude Long Endurance (HALE) Unmanned Aircraft Systems (UAS) service providers and National Airspace System (NAS) users. It describes current systems (existing UAS), describes HALE UAS functions and operations to be performed (via sample missions), and offers insight into the user s environment (i.e., the UAS as a system of systems). It is intended to be a source document for NAS UAS operational requirements, and provides a construct for government agencies to use in guiding their regulatory decisions, architecture requirements, and investment strategies. Although it does not describe the technical capabilities of a specific HALE UAS system (which do, and will vary widely), it is intended to aid in requirements capture and to be used as input to the functional requirements and analysis process. The document provides a basis for development of functional requirements and operational guidelines to achieve unrestricted access into the NAS. This document is an FY06 update to the FY05 Access 5 Project-approved Concept of Operations document previously published in the Public Domain on the Access 5 open website. This version is recommended to be approved for public release also. The updates are a reorganization of materials from the previous version with the addition of an updated set of operational requirements, inclusion of sample mission scenarios, and identification of roles and responsibilities of interfaces within flight phases.

Source record↗
NASA NTRS2008

International Space Station Human Behavior and Performance Competency Model: Volume II

This document further defines the behavioral markers identified in the document "Human Behavior and Performance Competency Model" Vol. I. The Human Behavior and Performance (HBP) competencies were recommended as requirements to participate in international long duration missions, and form the basis for determining the HBP training curriculum for long duration crewmembers. This document provides details, examples, knowledge areas, and affective skills to support the use of the HBP competencies in training and evaluation. This document lists examples and details specific to HBP competencies required of astronauts/cosmonauts who participate in ISS expedition and other international long-duration missions. Please note that this model does not encompass all competencies required. While technical competencies are critical for crewmembers, they are beyond the scope of this document. Additionally, the competencies in this model (and subsequent objectives) are not intended to limit the internal activities or training programs of any international partner.

Schmidt, Lacey↗
NASA NTRS2008

Vibro-Acoustic Response of Buildings Due to Sonic Boom Exposure: July 2007 Field Test

During the month of July 2007, a series of structural response measurements were made on a house on Edwards Air Force Base (EAFB) property that was exposed to sonic booms of various amplitudes. The purpose of this report is to document the measurements that were made, the structure on which they were made, the conditions under which they were made, the sensors and other hardware that were used, and the data that were collected. To that end, Chapter 2 documents the house, its location, the physical layout of the house, the surrounding area, and summarizes the transducers placed in and around the house. Chapter 3 details the sensors and other hardware that were placed in the house during the experiment. In addition, day-to-day variations of hardware configurations and transducer calibrations are documented in Chapter 3. Chapter 4 documents the boom generation process, flight conditions, and ambient weather conditions during the test days. Chapter 5 includes information about sub-experiments that were performed to characterize the vibro-acoustic response of the structure, the acoustic environment inside the house, and the acoustic environment outside the house. Chapter 6 documents the data format and presents examples of reduced data that were collected during the test days.

Klos, Jacob↗
NASA NTRS2010

NASA Docking System (NDS) Users Guide: International Space Station Program. Type 4

The NASA Docking System (NDS) Users Guide provides an overview of the basic information needed to integrate the NDS onto a Host Vehicle (HV). This Users Guide is intended to provide a vehicle developer with a fundamental understanding of the NDS technical and operations information to support their program and engineering integration planning. The Users Guide identifies the NDS Specification, Interface Definition or Requirement Documents that contain the complete technical details and requirements that a vehicle developer must use to design, develop and verify their systems will interface with NDS. This Guide is an initial reference and must not be used as a design document. In the event of conflict between this Users Guide and other applicable interface definition or requirements documents; the applicable document will take precedence. This Users Guide is organized in three main sections. Chapter 1 provides an overview of the NDS and CDA hardware and the operations concepts for the NDS. Chapter 2 provides information for Host Vehicle Program integration with the NDS Project Office. Chapter 2 describes the NDS Project organization, integration and verification processes, user responsibilities, and specification and interface requirement documents. Chapter 3 provides a summary of basic technical information for the NDS design. Chapter 3 includes NDS hardware component descriptions, physical size and weight characteristics, and summary of the capabilities and constraints for the various NDS sub-systems.

Tabakman, Alexander↗
NASA NTRS2005

Doclet To Synthesize UML

The RoseDoclet computer program extends the capability of Java doclet software to automatically synthesize Unified Modeling Language (UML) content from Java language source code. [Doclets are Java-language programs that use the doclet application programming interface (API) to specify the content and format of the output of Javadoc. Javadoc is a program, originally designed to generate API documentation from Java source code, now also useful as an extensible engine for processing Java source code.] RoseDoclet takes advantage of Javadoc comments and tags already in the source code to produce a UML model of that code. RoseDoclet applies the doclet API to create a doclet passed to Javadoc. The Javadoc engine applies the doclet to the source code, emitting the output format specified by the doclet. RoseDoclet emits a Rose model file and populates it with fully documented packages, classes, methods, variables, and class diagrams identified in the source code. The way in which UML models are generated can be controlled by use of new Javadoc comment tags that RoseDoclet provides. The advantage of using RoseDoclet is that Javadoc documentation becomes leveraged for two purposes: documenting the as-built API and keeping the design documentation up to date.

Barry, Matthew R.↗
NASA NTRS2005

Improved Emergency Egress Lighting System for the ISS

Emergency lights provide illumination in corridors, stairwells, ramps, escalators, aisles, and exit passageways during power failures. Safety and visibility are critical during a power outage. If emergency lights fail to operate properly, the building occupants can become disoriented. Four documents in a collection discuss different topics relating to a proposed improved emergency egress lighting system (EELS) for the International Space Station (ISS). While the present EELS is designed around rows of green-light-emitting diodes, the proposed system contains strips of electroluminescent tape using different colors for each egress path. The proposed EELS can be powered by the same battery currently used by the present EELS, but would require an inverter because electroluminescent devices require AC. Electroluminescent devices also require significantly less current and, depending on the color, would emit 3 to 8 times the light of the present EELS. In addition, they could operate for up to 75 hours (versus .20 minutes for the present system). The first document contains a one-page summary of the proposal and an evaluation of technical merit. The second document summarizes the motivation for, and the design of, the proposed EELS. The third document addresses relevant aspects of the measurement of spectral sensitivity and the psychophysics of perception of light. The fourth document presents additional background information and technical specifications for the electroluminescent tapes.

Eaton, Leslie L.↗
NASA NTRS2011

International Low Impact Docking System (iLIDS) Project Technical Requirements Specification, Revision F

The NASA Docking System (NDS) is NASA's implementation for the emerging International Docking System Standard (IDSS) using low impact docking technology. The NASA Docking System Project (NDSP) is the International Space Station (ISS) Program's project to produce the NDS, Common Docking Adapter (CDA) and Docking Hub. The NDS design evolved from the Low Impact Docking System (LIDS). The acronym international Low Impact Docking System (iLIDS) is also used to describe this system as well as the Government Furnished Equipment (GFE) project designing the NDS for the NDSP. NDS and iLIDS may be used interchangeability. This document will use the acronym iLIDS. Some of the heritage documentation and implementations (e.g., software command names, requirement identification (ID), figures, etc.) used on NDS will continue to use the LIDS acronym. This specification defines the technical requirements for the iLIDS GFE delivered to the NDSP by the iLIDS project. This document contains requirements for two iLIDS configurations, SEZ29101800-301 and SEZ29101800-302. Requirements with the statement, iLIDS shall, are for all configurations. Examples of requirements that are unique to a single configuration may be identified as iLIDS (-301) shall or iLIDS (-302) shall. Furthermore, to allow a requirement to encompass all configurations with an exception, the requirement may be designated as iLIDS (excluding -302) shall. Verification requirements for the iLIDS project are identified in the Verification Matrix (VM) provided in the iLIDS Verification and Validation Document, JSC-63966. The following definitions differentiate between requirements and other statements: Shall: This is the only verb used for the binding requirements. Should/May: These verbs are used for stating non-mandatory goals. Will: This verb is used for stating facts or declaration of purpose. A Definition of Terms table is provided in Appendix B to define those terms with specific tailored uses in this document.

Lewis, James L.↗
NASA NTRS2011

Optical Property Requirements for Glasses, Ceramics and Plastics in Spacecraft Window Systems

This is a preliminary draft of a standard published by the National Aeronautics and Space Administration (NASA) Johnson Space Center (JSC) that is intended to provide uniform window optical design requirements in support of the development of human-rated spaceflight hardware. The material covered in this standard is based on data from extensive testing by the Advanced Sensing and Optical Measurement Branch at NASA Langley Research Center, and compiled into requirements format by the NASA JSC Structural Engineering Division. At the time of this initial document release, a broader technical community has not reviewed this standard. The technical content of this standard is primarily based on the Constellation Program Orion Crew Exploration Vehicle Window Optical Properties Requirements, CxP 72407, Baseline. Unlike other optical requirements documents available for human rated spacecraft, this document includes requirements that ensure functionality for windows that contain glass/ceramic and/or plastic window substrate materials. These requirements were derived by measuring the optical properties of fused silica and aluminosilicate glass window assemblies and ensuring that the performance of any window assembly that includes a plastic pane or panes will meet the performance level of the all-glass assemblies. The resulting requirements are based upon the performance and parameter metrology testing of a variety of materials, including glass, transparent ceramics, acrylics, and polycarbonates. In general, these requirements are minimum specifications for each optical parameter in order to achieve the function specified for each functional category, A through D. Because acrylic materials perform at a higher level than polycarbonates in the optics regime, and CxP/Orion is planning to use acrylic in the Orion spacecraft, these requirements are based heavily on metrology from that material. As a result, two of the current Category D requirements for plastics are cited in such a way that will result in the screening out of polycarbonates. It is acknowledged that many polycarbonates can perform the functions of Category D, such as piloting and imagery with lens with apertures up to 25mm, without performance issues. Therefore, this forward warns users that certain requirements, such as birefringence and wavefront, for Category D plastics need to be revised to allow those polycarbonates that perform adequately in Category D to be accepted, while at the same time, screen out those materials that do not perform up to par. At the time of document release, the requirements in question have been identified by a TBD beside the proposed requirement criteria (which is based upon acrylic performance). Vehicles that are designed with acrylic materials for windowpanes are encouraged to use the values presented in this document for all requirements, in order to ensure adequate optical performance.

Lynda R Estes↗