Search NASA⌕ Search

SEARCH · Search NASA

Results for “COMPILER PROGRAM”

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 361 records · Page 20

X-33 Flight Operations Center

In response to Clause 17 of the Cooperative Agreement NCC8-115, Lockheed Martin Skunk Works has compiled an Annual Performance Report of the X-33/RLV Program. This report consists of individual reports from all industry team members, as well as NASA team centers. Contract award was announced on July 2, 1996 and the first milestone was hand delivered to NASA MSFC on July 17, 1996. With the dedication of the launch site, and continuing excellence in technological achievement, the third year of the Cooperative Agreement has been one of outstanding accomplishment and excitement.

Source record↗

Lockheed Martin Skunk Works Single Stage to Orbit/Reusable Launch Vehicle

Lockheed Martin Skunk Works has compiled an Annual Performance Report of the X-33/RLV Program. This report consists of individual reports from all industry team members, as well as NASA team centers. This portion of the report is comprised of a status report of Lockheed Martin's contribution to the program. The following is a summary of the Lockheed Martin Centers involved and work reviewed under their portion of the agreement: (1) Lockheed Martin Skunk Works - Vehicle Development, Operations Development, X-33 and RLV Systems Engineering, Manufacturing, Ground Operations, Reliability, Maintainability/Testability, Supportability, & Special Analysis Team, and X-33 Flight Assurance; (2) Lockheed Martin Technical Operations - Launch Support Systems, Ground Support Equipment, Flight Test Operations, and RLV Operations Development Support; (3) Lockheed Martin Space Operations - TAEM and A/L Guidance and Flight Control Design, Evaluation of Vehicle Configuration, TAEM and A/L Dispersion Analysis, Modeling and Simulations, Frequency Domain Analysis, Verification and Validation Activities, and Ancillary Support; (4) Lockheed Martin Astronautics-Denver - Systems Engineering, X-33 Development; (5) Sanders - A Lockheed Martin Company - Vehicle Health Management Subsystem Progress, GSS Progress; and (6) Lockheed Martin Michoud Space Systems - X-33 Liquid Oxygen (LOX) Tank, Key Challenges, Lessons Learned, X-33/RLV Composite Technology, Reusable Cyrogenic Insulation (RCI) and Vehicle Health Monitoring, Main Propulsion Systems (MPS), Structural Testing, X-33 System Integration and Analysis, and Cyrogenic Systems Operations.

Source record↗

[X-33 Systems]

Lockheed Martin Skunk Works has compiled an Annual Performance Report of the X-33/RLV Program. This report consists of individual reports from all industry team members, as well as NASA team centers. This portion of the report is comprised of a status report of Allied-Signal Aerospace's contribution to the program. The following is a summary of the work reviewed under their portion of the agreement: (1) Communication Systems; (2) Environmental Control Systems- Active Thermal Control System (ATCS), Purge and Vent System, Hydrogen Detection System (HDS), Avionics Bay Inerting System (ABIS), and Flush Air Data System (FADS); (2) Landing Systems; (3) Power Management and Generation Systems; (4) Flight Control Actuation System (FCAS)- Electric Power Control & Distribution System (EPCDS), and Battery Power System (BPS); and (5) Vehicle Management Systems (VMS)- VMS Hardware, VMS Software Development Activities, and System Integration Laboratory (SIL).

Source record↗

[X-33 Research By NASA Centers]

Lockheed Martin Skunk Works has compiled an Annual Performance Report of the X-33/RLV Program. This report consists of individual reports from all industry team members, as well as NASA team centers. This portion of the report is comprised of overviews of each NASA Center's contribution to the program during the period 1 Apr. 1998 - 31 Mar. 1999.

Source record↗

New Software for Ensemble Creation in the Spitzer-Space-Telescope Operations Database

Some of the computer pipelines used to process digital astronomical images from NASA's Spitzer Space Telescope require multiple input images, in order to generate high-level science and calibration products. The images are grouped into ensembles according to well documented ensemble-creation rules by making explicit associations in the operations Informix database at the Spitzer Science Center (SSC). The advantage of this approach is that a simple database query can retrieve the required ensemble of pipeline input images. New and improved software for ensemble creation has been developed. The new software is much faster than the existing software because it uses pre-compiled database stored-procedures written in Informix SPL (SQL programming language). The new software is also more flexible because the ensemble creation rules are now stored in and read from newly defined database tables. This table-driven approach was implemented so that ensemble rules can be inserted, updated, or deleted without modifying software.

Spitzer Science Center (SSC)↗

Evolvable Hardware for Spacecraft Autonomy

Evolvable hardware is a recently proposed technology in which reconfigurable hardware under the control of and evolutionary (genetic) algorithm can automatically self-reconfigure into sonfigurations with the desired behavior.

digital↗

An Expanded Role for Python in Expediting System Simulation Development

The Python programming language has traditionally been used as a “scripting” language and is not generally recognized as a language for building system simulations, where C++, Java, and other compiled languages are typically used. While very powerful and gaining favor for a large set of programming tasks, Python is generally regarded as not having the speed to directly do the extensive numeric computations required in large-scale simulation. This paper aims to present an approach, supported by case studies, to re-think this assertion. Directly using Python in this new role has the potential to expedite an agile, spiral cycle of development of design-test-modify for systems simulation.

programming language↗

SLS-SPEC-159 Cross-Program Design Specification for Natural Environments (DSNE) Revision D

This document is derived from the former National Aeronautics and Space Administration (NASA) Constellation Program (CxP) document CxP 70023, titled "The Design Specification for Natural Environments (DSNE), Revision C." The original document has been modified to represent updated Design Reference Missions (DRMs) for the NASA Exploration Systems Development (ESD) Programs. The DSNE completes environment-related specifications for architecture, system-level, and lower-tier documents by specifying the ranges of environmental conditions that must be accounted for by NASA ESD Programs. To assure clarity and consistency, and to prevent requirements documents from becoming cluttered with extensive amounts of technical material, natural environment specifications have been compiled into this document. The intent is to keep a unified specification for natural environments that each Program calls out for appropriate application. This document defines the natural environments parameter limits (maximum and minimum values, energy spectra, or precise model inputs, assumptions, model options, etc.), for all ESD Programs. These environments are developed by the NASA Marshall Space Flight Center (MSFC) Natural Environments Branch (MSFC organization code: EV44). Many of the parameter limits are based on experience with previous programs, such as the Space Shuttle Program. The parameter limits contain no margin and are meant to be evaluated individually to ensure they are reasonable (i.e., do not apply unrealistic extreme-on-extreme conditions). The natural environments specifications in this document should be accounted for by robust design of the flight vehicle and support systems. However, it is understood that in some cases the Programs will find it more effective to account for portions of the environment ranges by operational mitigation or acceptance of risk in accordance with an appropriate program risk management plan and/or hazard analysis process. The DSNE is not intended as a definition of operational models or operational constraints, nor is it adequate, alone, for ground facilities which may have additional requirements (for example, building codes and local environmental constraints). "Natural environments," as the term is used here, refers to the environments that are not the result of intended human activity or intervention. It consists of a variety of external environmental factors (most of natural origin and a few of human origin) which impose restrictions or otherwise impact the development or operation of flight vehicles and destination surface systems. These natural environments include the following types of environments: Terrestrial environments at launch, abort, and normal landing sites (winds, temperatures, pressures, surface roughness, sea conditions, etc.); Space environments (ionizing radiation, orbital debris, meteoroids, thermosphere density, plasma, solar, Earth, and lunar-emitted thermal radiation, etc.); Destination environments (Lunar surface and orbital, Mars atmosphere and surface, near Earth asteroids, etc.). Many of the environmental specifications in this document are based on models, data, and environment descriptions contained in the CxP 70044, Constellation Program Natural Environment Definition for Design (NEDD). The NEDD provides additional detailed environment data and model descriptions to support analytical studies for ESD Programs. For background information on specific environments and their effects on spacecraft design and operations, the environment models, and the data used to generate the specifications contained in the DSNE, the reader is referred to the NEDD paragraphs listed in each section of the DSNE. Also, most of the environmental specifications in this document are tied specifically to the ESD DRMs in ESD-10012, Revision B, Exploration Systems Development Concept of Operations (ConOps). Coordination between these environment specifications and the DRMs must be maintained. This document should be compatible with the current ESD DRMs, but updates to the mission definitions and variations in interpretation may require adjustments to the environment specifications.

Roberts, Barry C.↗

SLS-SPEC-159 Cross-Program Design Specification for Natural Environments (DSNE) Revision E

The DSNE completes environment-related specifications for architecture, system-level, and lower-tier documents by specifying the ranges of environmental conditions that must be accounted for by NASA ESD Programs. To assure clarity and consistency, and to prevent requirements documents from becoming cluttered with extensive amounts of technical material, natural environment specifications have been compiled into this document. The intent is to keep a unified specification for natural environments that each Program calls out for appropriate application. This document defines the natural environments parameter limits (maximum and minimum values, energy spectra, or precise model inputs, assumptions, model options, etc.), for all ESD Programs. These environments are developed by the NASA Marshall Space Flight Center (MSFC) Natural Environments Branch (MSFC organization code: EV44). Many of the parameter limits are based on experience with previous programs, such as the Space Shuttle Program. The parameter limits contain no margin and are meant to be evaluated individually to ensure they are reasonable (i.e., do not apply unrealistic extreme-on-extreme conditions). The natural environments specifications in this document should be accounted for by robust design of the flight vehicle and support systems. However, it is understood that in some cases the Programs will find it more effective to account for portions of the environment ranges by operational mitigation or acceptance of risk in accordance with an appropriate program risk management plan and/or hazard analysis process. The DSNE is not intended as a definition of operational models or operational constraints, nor is it adequate, alone, for ground facilities which may have additional requirements (for example, building codes and local environmental constraints). "Natural environments," as the term is used here, refers to the environments that are not the result of intended human activity or intervention. It consists of a variety of external environmental factors (most of natural origin and a few of human origin) which impose restrictions or otherwise impact the development or operation of flight vehicles and destination surface systems.

Roberts, Barry C.↗

Cross-Program Design Specification for Natural Environments (DSNE) Revision G

The DSNE completes environment-related specifications for architecture, system-level, and lower-tier documents by specifying the ranges of environmental conditions that must be accounted for by NASA ESD Programs. To assure clarity and consistency, and to prevent requirements documents from becoming cluttered with extensive amounts of technical material, natural environment specifications have been compiled into this document. The intent is to keep a unified specification for natural environments that each Program calls out for appropriate application.

Barry C Roberts↗

Cross-Program Design Specification for Natural Environments (DSNE) Revision H

The DSNE completes environment-related specifications for architecture, system-level, and lower-tier documents by specifying the ranges of environmental conditions that must be accounted for by NASA ESD Programs. To assure clarity and consistency, and to prevent requirements documents from becoming cluttered with extensive amounts of technical material, natural environment specifications have been compiled into this document. The intent is to keep a unified specification for natural environments that each Program calls out for appropriate application.

Frank B Leahy↗

The GOAL-to-HAL/S translator specification

The specification sets forth a technical framework within which to deal with the transfer of specific GOAL features to HAL/S. Key technical features of the translator are described which communicate with the data bank, handle repeat statements, and deal with software interrupts. GOAL programs, databank information, and GOAL system subroutines are integrated into one GOAL in HAL/S. This output is fully compatible HAL/S source ready for insertion into the HAL/S compiler. The Translator uses a PASS1 to establish all the global data needed for the HAL/S output program. Individual GOAL statements are translated in PASS2. The specification document makes extensive use of flowcharts to specify exactly how each variation of each GOAL statement is to be translated. The specification also deals with definitions and assumptions, executive support structure and implementation. An appendix, entitled GOAL-to-HAL Mapping, provides examples of translated GOAL statements.

Stanten, S. F.↗

The SIMRAND 1 computer program: Simulation of research and development projects

The SIMRAND I Computer Program (Version 5.0 x 0.3) written in Microsoft FORTRAN for the IBM PC microcomputer and its compatibles is described. The SIMRAND I Computer Program comprises eleven modules-a main routine and ten subroutines. Two additional files are used at compile time; one inserts the system or task equations into the source code, while the other inserts the dimension statements and common blocks. The SIMRAND I Computer Program can be run on most microcomputers or mainframe computers with only minor modifications to the computer code.

Miles, R. F., Jr.↗

Compiling global name-space parallel loops for distributed execution

Distributed memory machines do not provide hardware support for a global address space. Thus programmers are forced to partition the data across the memories of the architecture and use explicit message passing to communicate data between processors. The compiler support required to allow programmers to express their algorithms using a global name-space is examined. A general method is presented for analysis of a high level source program and its translation into a set of independently executing tasks communicating via messages. If the compiler has enough information, this translation can be carried out at compile time. Otherwise, run-time code is generated to implement the required data movement. The analysis required in both situations is described and the performance of the generated code on the Intel iPSC/2 is presented.

Koelbel, Charles↗

Fasteners and fastening techniques: A compilation

Technology on fasteners and fastening devices is presented, as part of NASA's TU program to provide technical information on devices, methods, and techniques resulting from aerospace research. The material is divided into two sections which include: (1) data concerning a selected group of fasteners and concept for fasteners such as locking devices, couplings, and connect and release mechanisms; and (2) discussions on a number of fastening techniques such as those for mounting panel lamps, clamping flange bolts, stretching fasteners, and transferring fuel from a tanker to another vehicle.

Source record↗

Conference on Fire Resistant Materials (FIREMEN): A compilation of presentations and papers

The proceedings of the NASA Fire Resistant Materials Engineering (FIREMEN) Program held at Ames Research Center on April, 13, 14, 1978 are reported. The purpose of the conference was to discuss the results of NASA in the field of aircraft fire safety and fire resistant materials. The program components include the following: (1) large-scale testing; (2) fire toxicology; (3) polymeric materials; and (4) bibliography related and/or generated from the program.

Kourtides, D. A.↗

Conference on Fire Resistant Materials: A compilation of presentations and papers

The proceedings of the NASA IRE Resistant Materials Engineering (FIREMEN) Program held at Boeing Commercial Airplane Company, Seattle, Washington, on March 1-2, 1979 are reported. The conference was to discuss the results of research by the National Aeronautics and Space Administration in the field of aircraft fire safety and fire-resistant materials. The program topics include the following: (1) large-scale testing; (2) fire toxicology; (3) polymeric materials; and (4) fire modeling.

Kourtides, D. A.↗

Compendium of meteorological space programs, satellites, and experiments

This compendium includes plans and events known to the authors through January 1987. Compilation of the information began in 1967. This document is intended: (1) as a historical record of all satellites and instrumentation that has been useful for meteorological research or operational uses; and (2) as a working document to be used to assist meteorologists in identifying meteorological satellites, locating data from these satellites, and understanding experiment operation which is related to satellite data that may be of interest to them. A summary of all known launched satellites for all countries and their experiments, which were concerned with meteorological operations or research, are included. Programs covered include AEM, Apollo, ATS, Bhaskara, Cosmos, Discoverer, DMSP, DOD, DODGE, EOLE, ERBE, ESSA, Explorer, Gemini, GMS, GOES/SMS, INSAT, IRS, LANDSAT, Mercury, Meteor 1 and 2, Meteosat, Molniya, MOS, Nimbus, NOAA (1-5)/ITOS, NOAA (6,7,D)/TIROS-N, NOAA (8-10, H-J)/ATN, Salyut, Seasat, Shuttle 1, Shuttle 2: Spacelab, Skylab, Soyuz, TIROS, TOPEX, Vanguard, Voskhod, Vostok, and Zond.

Dubach, Leland L.↗