Search NASA⌕ Search

SEARCH · Search NASA

Results for “program compilers”

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 469 records · Page 26

A universal structured-design diagramer

Program (FLOWCHARTER) generates standardized flowcharts and concordances for development and debugging of programs in any language. User describes programming-language grammar, providing syntax rules in Backus-Naur form (BNF), list of semantic rules, and set of concordance rules. Once grammar is described, user supplies only source code of program to be diagrammed. FLOWCHARTER automatically produces flow diagram and concordance. Source code for program is written for PASCAL Release 2 compiler, as distributed by University of Minnesota.

Source record↗

Modular photovoltaic stand-alone systems: Phase 1

A family of modular stand-alone power systems that covered the range in power level from 1 kw to 14 kw was developed. Products within this family were required to be easily adaptable to different environments and applications, and were to be both reliable and cost effective. Additionally, true commonality in hardware was to be exploited, and unnecessary recurrence of design and development costs were to be minimized; thus improving hardware availability. Assurance of compatibility with large production runs, was also an underlying program goal. A secondary objective was to compile, evaluate, and determine the economic and technical status of available, and potentially available, technology options associated with the balance of systems (BOS) for stand-along photovoltaic (PV) power systems. The secondary objective not only directly supported the primary but additionally contributed to the definition and implementation of the BOS cost reduction plan.

Naff, G. J.↗

Research and Technology Objectives and Plans Summary (RTOPS)

This publication represents the NASA research and technology program for FY 1985. It is a compilation of the Summary portions of each of the RTOPs (Research and Technology Objectives and Plans) used for management review and control of research currently in progress throughout NASA. The RTOP summary is designed to facilitate communication and coordination among concerned technical personnel in government, in industry, and in universities. The first section containing citations and abstracts of the RTOPs is followed by four indexes: Subject, Technical Monitor, Responsible NASA Organization, and RTOP number.

Source record↗

Automating FEA programming

In this paper we briefly describe a combined symbolic and numeric approach for solving mathematical models on parallel computers. An experimental software system, PIER, is being developed in Common Lisp to synthesize computationally intensive and domain formulation dependent phases of finite element analysis (FEA) solution methods. Quantities for domain formulation like shape functions, element stiffness matrices, etc., are automatically derived using symbolic mathematical computations. The problem specific information and derived formulae are then used to generate (parallel) numerical code for FEA solution steps. A constructive approach to specify a numerical program design is taken. The code generator compiles application oriented input specifications into (parallel) FORTRAN77 routines with the help of built-in knowledge of the particular problem, numerical solution methods and the target computer.

Sharma, Naveen↗

Database of proposed payloads and instruments for SEI missions

A database of all payloads and instruments proposed for lunar and Mars missions was compiled by the author for the Exploration Programs Office at NASA's Johnson Sapce Center. The database is an outgrowth of the document produced by C. J. Budney et al. at the Jet Propulsion Laboratory in 1991. The present database consists not only of payloads proposed for human exploratory missions of the Moon and Mars, but also experiments selected or proposed for robotic precursor missions such as Lunar Scout, Mars Observer, and MESUR. The database consists of two parts: a written payload description and a matrix that provides a breakdown of payload components. Each payload description consists of the following information: (1) the rationale for why the instrument or payload package is being proposed for operation on the Moon or Mars; (2) a description of how the instrument works; (3) a breakdown of the payload, providing detailed information about the mass, volume, power requirements, and data rates for the constituent pieces of the experiment; (4) estimates of the power consumption and data rate; (5) how the data will be returned to Earth and distributed to the scientific community; (6) any constraints on the location or conditions under which the instrument can or cannot operate; (7) what type of crew interaction (if any) is needed; (8) how the payload is to be delivered to the lunar or martian surface (along with alternative delivery options); (9) how long the instrument or payload package will take to set up; (10) what type of maintenance needs are anticipated for the experiment; (11) stage of development for the instrument and environmental conditions under which the instrument has been tested; (12) an interface required by the instrument with the lander, a rover, an outpost, etc.; (13) information about how often the experiment will need to be resupplied with parts or consumables, if it is to be resupplied; (14) the name and affiliation of a contact person for the experiment; and (15) references where further information about the experiment can be found.

Barlow, N. G.↗

Research and Technology Objectives and Plans Summary (RTOPS)

This publication represents the NASA research and technology program for FY-93. It is a compilation of the Summary portions of each of the RTOP's (Research and Technology Objectives and Plans) used for management review and control of research currently in progress throughout NASA. The RTOP Summary is designed to facilitate communication and coordination among concerned technical personnel in government, in industry, and in universities. The first section containing citations and abstracts of the RTOP's is followed by four indexes: Subject, Technical Monitor, Responsible NASA Organization, and RTOP Number.

Source record↗

Challenge To Apollo: The Soviet Union and The Space Race, 1945-1974

This book is, in essence, sixteen years in the making. First attempted to compile a history of the Soviet space program in 1982 author put together a rough chronology of the main events. A decade later, while living on a couch in a college friend's apartment, he began writing what would be a short history of the Soviet lunar landing program. The first draft was sixty-nine pages long. Late the following year, he decided to expand the topic to handle all early Soviet piloted exploration programs. That work eventually grew into what you are holding in your hand now.

Siddiqi, Asif A.↗

Aggregate Risk Tool for Human Space Flight

This project utilized Data fusion capabilities developed from the 2020-2022 Information Fusion (IFDA) IRAD to enhance functionality of a Human Spaceflight (HSF) Aggregate Risk Product developed by the JSC Flight Safety Office. The tool compiles and presents risk data from multiple Program and Commercial Provider vehicles to provide a holistic assessment of residual risk to Program Managers and Technical Authorities prior to HSF Launches. The aggregation or coupling of risks from multiple sources (Examples: PRA, variances, anomaly data bases, Program Risk Management data bases, technical review board minutes, Hazard Analysis, etc.) when analyzed, identify potential areas of elevated risk in components, systems or mission phases that would otherwise be undetected by nonintegrated program risk management tools and possesses.

Patrick Huckaby↗

Aggregate Risk Tool for Human Space Flight

This tool utilizes Data fusion capabilities developed from the 2020-2022 Information Fusion (IFDA) IRAD to enhance functionality of a Human Spaceflight (HSF) Aggregate Risk Product developed by the JSC Flight Safety Office. The tool compiles and present risk data from multiple Program and Commercial Provider sources to provide a holistic assessment for Program Managers and Technical Authorities to evaluate residual risk prior to HSF Launches. The aggregation, or coupling of risks from multiple sources (Ex: PRA, variances, anomaly data bases, CRM data, technical review board minutes, Hazard Analysis, etc.) identifies areas of elevated risk in components, systems or mission phases that would otherwise be undetected by non-integrated program risk management tools and possesses. Data is then displayed in an interactive user interface/dashboard that enables users to see potential areas of concern requiring more in-depth analysis.

Patrick M Huckaby↗

FTMP (Fault Tolerant Multiprocessor) programmer's manual

The Fault Tolerant Multiprocessor (FTMP) computer system was constructed using the Rockwell/Collins CAPS-6 processor. It is installed in the Avionics Integration Research Laboratory (AIRLAB) of NASA Langley Research Center. It is hosted by AIRLAB's System 10, a VAX 11/750, for the loading of programs and experimentation. The FTMP support software includes a cross compiler for a high level language called Automated Engineering Design (AED) System, an assembler for the CAPS-6 processor assembly language, and a linker. Access to this support software is through an automated remote access facility on the VAX which relieves the user of the burden of learning how to use the IBM 4381. This manual is a compilation of information about the FTMP support environment. It explains the FTMP software and support environment along many of the finer points of running programs on FTMP. This will be helpful to the researcher trying to run an experiment on FTMP and even to the person probing FTMP with fault injections. Much of the information in this manual can be found in other sources; we are only attempting to bring together the basic points in a single source. If the reader should need points clarified, there is a list of support documentation in the back of this manual.

Feather, F. E.↗

Microgravity Science and Applications Program tasks, 1990 revision

The active research tasks as of the end of the fiscal year 1990 sponsored by the Microgravity Science and Applications Division of the NASA Office of Space Science and Applications are compiled. The purpose is to provide an overview of the program scope for managers and scientists in industry, university, and government communities. The report includes an introductory description of the program, the strategy and overall goal; an index of principle investigators; and a description of each task. A list of recent publications is also provided. The tasks are grouped into six major categories: electronic materials; solidification of metals, alloys, and composites; fluid dynamics and transport phenomena; biotechnology; glasses and ceramics; combustion; experimental technology; facilities; and Physics And Chemistry Experiments (PACE). The tasks are divided into ground-based and flight experiments.

Source record↗

The Rodinia Benchmark Suite in SYCL

As opposed to the Open Computing Language (OpenCL) programming model in which host and device codes are generally written in different programming languages, SYCL can combine host and device codes for an application in a type-safe way to improve development productivity and performance portability. Rodinia is a widely used benchmark suite for heterogeneous computing. Hence, we port the OpenCL implementations of the benchmark suite to SYCL manually. The SYCL benchmark suite is an opensource project for tracking the development of the mainstream SYCL compilers, and for developers and researchers interested in programming productivity, performance analysis, and portability across different computing platforms. We organize the remainder of the report as follows. Section II introduces the SYCL programming model, shows the major differences between an OpenCL program and a SYCL program, and gives a summary of the benchmark suite. In Section III, we describe our SYCL implementations in more details. We evaluate the SYCL benchmarks on the Intel® central processing units (CPUs) and graphics processing units (GPUs) in Section IV. Section V concludes the report.

97 MATHEMATICS AND COMPUTING↗

Analysis of Validating and Verifying OpenACC Compilers 3.0 and Above

OpenACC is a high-level directive-based parallel programming model that can manage the sophistication of heterogeneity in architectures and abstract it from the users. The portability of the model across CPUs and accelerators has gained the model a wide variety of users. This means it is also crucial to analyze the reliability of the compilers’ implementations. To address this challenge, the OpenACC Validation and Verification team has proposed a validation testsuite to verify the OpenACC implementations across various compilers with an infrastructure for a more streamlined execution. This paper will cover the following aspects: (a) the new developments since the last publication on the testsuite, (b) outline the use of the infrastructure, (c) discuss tests that highlight our workflow process, (d) analyze the results from executing the testsuite on various systems, and (e) outline future developments.

Jarmusch, Aaron↗

Testing New Programming Paradigms with NAS Parallel Benchmarks

Over the past decade, high performance computing has evolved rapidly, not only in hardware architectures but also with increasing complexity of real applications. Technologies have been developing to aim at scaling up to thousands of processors on both distributed and shared memory systems. Development of parallel programs on these computers is always a challenging task. Today, writing parallel programs with message passing (e.g. MPI) is the most popular way of achieving scalability and high performance. However, writing message passing programs is difficult and error prone. Recent years new effort has been made in defining new parallel programming paradigms. The best examples are: HPF (based on data parallelism) and OpenMP (based on shared memory parallelism). Both provide simple and clear extensions to sequential programs, thus greatly simplify the tedious tasks encountered in writing message passing programs. HPF is independent of memory hierarchy, however, due to the immaturity of compiler technology its performance is still questionable. Although use of parallel compiler directives is not new, OpenMP offers a portable solution in the shared-memory domain. Another important development involves the tremendous progress in the internet and its associated technology. Although still in its infancy, Java promisses portability in a heterogeneous environment and offers possibility to "compile once and run anywhere." In light of testing these new technologies, we implemented new parallel versions of the NAS Parallel Benchmarks (NPBs) with HPF and OpenMP directives, and extended the work with Java and Java-threads. The purpose of this study is to examine the effectiveness of alternative programming paradigms. NPBs consist of five kernels and three simulated applications that mimic the computation and data movement of large scale computational fluid dynamics (CFD) applications. We started with the serial version included in NPB2.3. Optimization of memory and cache usage was applied to several benchmarks, noticeably BT and SP, resulting in better sequential performance. In order to overcome the lack of an HPF performance model and guide the development of the HPF codes, we employed an empirical performance model for several primitives found in the benchmarks. We encountered a few limitations of HPF, such as lack of supporting the "REDISTRIBUTION" directive and no easy way to handle irregular computation. The parallelization with OpenMP directives was done at the outer-most loop level to achieve the largest granularity. The performance of six HPF and OpenMP benchmarks is compared with their MPI counterparts for the Class-A problem size in the figure in next page. These results were obtained on an SGI Origin2000 (195MHz) with MIPSpro-f77 compiler 7.2.1 for OpenMP and MPI codes and PGI pghpf-2.4.3 compiler with MPI interface for HPF programs.

Jin, H.↗

Program For Evaluation Of Reliability Of Ceramic Parts

CARES/LIFE predicts probability of failure of monolithic ceramic component as function of service time. Assesses risk that component fractures prematurely as result of subcritical crack growth (SCG). Effect of proof testing of components prior to service also considered. Coupled to such commercially available finite-element programs as ANSYS, ABAQUS, MARC, MSC/NASTRAN, and COSMOS/M. Also retains all capabilities of previous CARES code, which includes estimation of fast-fracture component reliability and Weibull parameters from inert strength (without SCG contributing to failure) specimen data. Estimates parameters that characterize SCG from specimen data as well. Written in ANSI FORTRAN 77 to be machine-independent. Program runs on any computer in which sufficient addressable memory (at least 8MB) and FORTRAN 77 compiler available. For IBM-compatible personal computer with minimum 640K memory, limited program available (CARES/PC, COSMIC number LEW-15248).

Nemeth, N.↗

Nevada National Security Site 2011 Data Report: Groundwater Monitoring Program Area 5 Radioactive Waste Management Site

This report is a compilation of the groundwater sampling results from the Area 5 Radioactive Waste Management Site (RWMS). The data have been collected since 1993 and include calendar year 2011 results. During 2011, groundwater samples were collected and static water levels were measured at the three pilot wells surrounding the Area 5 RWMS. Samples were collected at UE5PW-1 on March 8, August 2, August 24, and October 19, 2011; at UE5PW-2 on March 8, August 2, August 23, and October 19, 2011; and at UE5PW-3 on March 8, August 2, August 23, and October 19, 2011. Static water levels were measured at each of the three pilot wells on March 1, June 7, August 1, and October 17, 2011. Groundwater samples were analyzed for the following indicators of contamination: pH, specific conductance, total organic carbon, total organic halides, and tritium. Indicators of general water chemistry (cations and anions) were also measured. Initial total organic carbon and total organic halides results for samples collected in August 2011 were above previous measurements and, in some cases, above the established investigation limits. However, after field sample pumps and tubing were disinfected with Clorox solution, the results returned to normal levels. Final results from samples collected in 2011 were within the limits established by agreement with the Nevada Division of Environmental Protection for each analyte. These data indicate that there has been no measurable impact to the uppermost aquifer from the Area 5 RWMS. There were no significant changes in measured groundwater parameters compared to previous years. The report contains an updated cumulative chronology for the Area 5 RWMS Groundwater Monitoring Program and a brief description of the site hydrogeology.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

The LHEA PDP 11/70 graphics processing facility users guide

A compilation of all necessary and useful information needed to allow the inexperienced user to program on the PDP 11/70. Information regarding the use of editing and file manipulation utilities as well as operational procedures are included. The inexperienced user is taken through the process of creating, editing, compiling, task building and debugging his/her FORTRAN program. Also, documentation on additional software is included.

Source record↗

Ompparser

ompparser is a standalone and unified OpenMP parser, which is motivated by the facts that: 1) The differences in terms of syntax and semantics of OpenMP constructs between C/C++ and Fortran are minor. 2) Current OpenMP compilers often develop their own parsers, which represent redundant work. The features of ompparser include: 1) ompparser can be used standalone for static source code analysis, e.g. tools for semantics checking or similarity analysis between C/C++ and Fortran programs 2) omppaser can be integrated into an OpenMP compiler implementation can reduce the development efforts, and there is no need to create and maintain two separate parsers for C/C++ and Fortran. 3) ompparser provides a complete reference OpenMP grammar in the Backus-Naur Form that formally describes all the latest OpenMP language constructs. This will help users understand the rules and restriction of the OpenMP standard, which no longer contains a reference grammar in its recent versions.

Wang, Anjia↗