SEARCH · Engineering Papers

Results for “compilation”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 703 records · Page 39

All sources NASA NTRS DOE OSTI

NASA NTRS2009

The 50 Constellation Priority Sites

The Constellation program (CxP) has developed a list of 50 sites of interest on the Moon which will be targeted by the LRO narrow angle camera. The list has also been provided to the M~ team to supplement their targeting list. This list does not represent a "site selection" process; rather the goal was to find "representative" sites and terrains to understand the range of possible surface conditions for human lunar exploration to aid engineering design and operational planning. The list compilers leveraged heavily on past site selection work (e.g. Geoscience and a Lunar Base Workshop - 1988, Site Selection Strategy for a Lunar Outpost - 1990, Exploration Systems Architecture Study (ESAS) - 2005). Considerations included scientific, resource utilization, and operational merits, and a desire to span lunar terrain types. The targets have been organized into two "tiers" of 25 sites each to provide a relative priority ranking in the event of mutual interference. A LEAG SAT (special action team) was established to validate and recommend modifications to the list. This SAT was chaired by Dr. Paul Lucey. They provided their final results to CxP in May. Dr. Wendell Mendell will organize an on-going analysis of the data as they come down to ensure data quality and determine if and when a site has sufficient data to be retired from the list. The list was compiled using the best available data, however, it is understood that with the flood of new lunar data, minor modifications or adjustments may be required.

Noble, S.↗

NASA NTRS2009

Geologic Mapping of the Lunar South Pole, Quadrangle LQ-30: Volcanic History and Stratigraphy of Schroedinger Basin

In this study we use recent images and topographic data to map the geology and geomorphology of the lunar South Pole quadrangle (LQ-30) at 1:2.5M scale [1-4] in accordance with the Lunar Geologic Mapping Program. Mapping of LQ-30 began during Mest's postdoctoral appointment and has continued under the PG&G Program, from which funding became available in February 2009. Preliminary map-ping and analyses have been done using base materials compiled by Mest, but properly mosaicked and spatially registered base materials are being compiled by the USGS and should be received by the end of June 2009. The overall objective of this research is to constrain the geologic evolution of the lunar South Pole (LQ-30: 60deg -90deg S, 0deg - +/-180deg ) with specific emphasis on evaluation of a) the regional effects of basin formation on the structure and composition of the crust and b) the spatial distribution of ejecta, in particular resulting from formation of the South Pole-Aitken (SPA) basin and other large basins. Key scientific objectives include: 1) Constraining the geologic history of the lunar South Pole and examining the spatial and temporal variability of geologic processes within the map area. 2) Constraining the vertical and lateral structure of the lunar regolith and crust, assessing the distribution of impact-generated materials, and determining the timing and effects of major basin-forming impacts on crustal structure and stratigraphy in the map area. And 3) assessing the distribution of resources (e.g., H, Fe, Th) and their relationships with surface materials.

Mest, S. C.↗

NASA NTRS2009

Mars Structural and Stratigraphic Mapping along the Coprates Rise

This geologic mapping project supports a topical study of structures in east Thaumasia associated with the Coprates rise. The study examines cuesta-like features on the east flank of the Coprates rise first identified by Saunders et al. [1]. Mapping combines detailed local stratigraphy, structural geology and topography. Hogbacks and cuestas indicate erosion of tilted rock units. The extent of the erosion will be determined in the course of the mapping. The region of interest lies along the eastern margin of Thaumasia bounded by latitudes -15 and -35 and longitudes 50 to 70 W (Figure 1). Three MTM geologic quadrangles are being compiled for publication by the USGS (-20057, -25057, -30057). All existing data sources are used including THEMIS, MOC, CTX, HiRISE, MOLA and gravity, as well as higher level data available through the PDS data nodes at ASU, UA and Washington University. The extremely valuable ASU JMARS tools are used for analysis of many of the data sets. ArcGIS software has been obtained and is being learned for the map compilation.

Saunders, R Stephen↗

NASA NTRS2010

Hardware-Independent Proofs of Numerical Programs

On recent architectures, a numerical program may give different answers depending on the execution hardware and the compilation. Our goal is to formally prove properties about numerical programs that are true for multiple architectures and compilers. We propose an approach that states the rounding error of each floating-point computation whatever the environment. This approach is implemented in the Frama-C platform for static analysis of C code. Small case studies using this approach are entirely and automatically proved

Boldo, Sylvie↗

NASA NTRS2006

Infrastructure for Rapid Development of Java GUI Programs

The Java Application Shell (JAS) is a software framework that accelerates the development of Java graphical-user-interface (GUI) application programs by enabling the reuse of common, proven GUI elements, as distinguished from writing custom code for GUI elements. JAS is a software infrastructure upon which Java interactive application programs and graphical user interfaces (GUIs) for those programs can be built as sets of plug-ins. JAS provides an application- programming interface that is extensible by application-specific plugins that describe and encapsulate both specifications of a GUI and application-specific functionality tied to the specified GUI elements. The desired GUI elements are specified in Extensible Markup Language (XML) descriptions instead of in compiled code. JAS reads and interprets these descriptions, then creates and configures a corresponding GUI from a standard set of generic, reusable GUI elements. These elements are then attached (again, according to the XML descriptions) to application-specific compiled code and scripts. An application program constructed by use of JAS as its core can be extended by writing new plug-ins and replacing existing plug-ins. Thus, JAS solves many problems that Java programmers generally solve anew for each project, thereby reducing development and testing time.

Jones, Jeremy↗

NASA NTRS2010

ISS and Shuttle Payload Research Development and Processing

NASA's ISS and Spacecraft Processing Directorate (UB) is charged with the performance of payload development for research originating through NASA, ISS international partners, and the National Laboratory. The Payload Development sector of the Directorate takes biological research approved for on orbit experimentation from its infancy stage and finds a way to integrate and implement that research into a payload on either a Shuttle sortie or Space Station increment. From solicitation and selection, to definition, to verification, to integration and finally to operations and analysis, Payload Development is there every step of the way. My specific work as an intern this summer has consisted of investigating data received by separate flight and ground control Advanced Biological Research Systems (ABRS) units for Advanced Plant Experiments (APEX) and Cambium research. By correlation and analysis of this data and specific logbook information I have been working to explain changes in environmental conditions on both the flight and ground control unit. I have then, compiled all of that information into a form that can be presentable to the Principal Investigator (PI). This compilation allows that PI scientist to support their findings and add merit to their research. It also allows us, as the Payload Developers, to further inspect the ABRS unit and its performance

Calhoun, Kyle A.↗

NASA NTRS2008

Generating Customized Verifiers for Automatically Generated Code

Program verification using Hoare-style techniques requires many logical annotations. We have previously developed a generic annotation inference algorithm that weaves in all annotations required to certify safety properties for automatically generated code. It uses patterns to capture generator- and property-specific code idioms and property-specific meta-program fragments to construct the annotations. The algorithm is customized by specifying the code patterns and integrating them with the meta-program fragments for annotation construction. However, this is difficult since it involves tedious and error-prone low-level term manipulations. Here, we describe an annotation schema compiler that largely automates this customization task using generative techniques. It takes a collection of high-level declarative annotation schemas tailored towards a specific code generator and safety property, and generates all customized analysis functions and glue code required for interfacing with the generic algorithm core, thus effectively creating a customized annotation inference algorithm. The compiler raises the level of abstraction and simplifies schema development and maintenance. It also takes care of some more routine aspects of formulating patterns and schemas, in particular handling of irrelevant program fragments and irrelevant variance in the program structure, which reduces the size, complexity, and number of different patterns and annotation schemas that are required. The improvements described here make it easier and faster to customize the system to a new safety property or a new generator, and we demonstrate this by customizing it to certify frame safety of space flight navigation code that was automatically generated from Simulink models by MathWorks' Real-Time Workshop.

Denney, Ewen↗

NASA NTRS2002

Timeliner: Automating Procedures on the ISS

Timeliner has been developed as a tool to automate procedural tasks. These tasks may be sequential tasks that would typically be performed by a human operator, or precisely ordered sequencing tasks that allow autonomous execution of a control process. The Timeliner system includes elements for compiling and executing sequences that are defined in the Timeliner language. The Timeliner language was specifically designed to allow easy definition of scripts that provide sequencing and control of complex systems. The execution environment provides real-time monitoring and control based on the commands and conditions defined in the Timeliner language. The Timeliner sequence control may be preprogrammed, compiled from Timeliner "scripts," or it may consist of real-time, interactive inputs from system operators. In general, the Timeliner system lowers the workload for mission or process control operations. In a mission environment, scripts can be used to automate spacecraft operations including autonomous or interactive vehicle control, performance of preflight and post-flight subsystem checkouts, or handling of failure detection and recovery. Timeliner may also be used for mission payload operations, such as stepping through pre-defined procedures of a scientific experiment.

Brown, Robert↗

NASA NTRS2011

Astronaut Demographic Database: Everything You Want to Know About Astronauts and More

A wealth of information regarding the astronaut population is available that could be especially useful to researchers. However, until now, it has been difficult to obtain that information in a systematic way. Therefore, this "astronaut database" began as a way for researchers within the Behavioral Health and Performance Group to keep track of the ever growing astronaut corps population. Before our effort, compilation of such data could be found, but not in a way that was easily acquired or accessible. One would have to use internet search engines, read through lengthy and potentially inaccurate informational sites, or read through astronaut biographies compiled by NASA. Astronauts are a unique class of individuals and, by examining such information, which we dubbed "Demographics," we hoped to find some commonalities that may be useful for other research areas and future research topics. By organizing the information pertaining to astronauts1 in a formal, unified catalog, we believe we have made the information more easily accessible, readily useable, and user friendly. Our end goal is to provide this database to others as a highly functional resource within the research community. Perhaps the database can eventually be an official, published document for researchers to gain full access.

Keeton, Kathryn↗

NASA NTRS2008

Efficient Probabilistic Diagnostics for Electrical Power Systems

We consider in this work the probabilistic approach to model-based diagnosis when applied to electrical power systems (EPSs). Our probabilistic approach is formally well-founded, as it based on Bayesian networks and arithmetic circuits. We investigate the diagnostic task known as fault isolation, and pay special attention to meeting two of the main challenges . model development and real-time reasoning . often associated with real-world application of model-based diagnosis technologies. To address the challenge of model development, we develop a systematic approach to representing electrical power systems as Bayesian networks, supported by an easy-to-use speci.cation language. To address the real-time reasoning challenge, we compile Bayesian networks into arithmetic circuits. Arithmetic circuit evaluation supports real-time diagnosis by being predictable and fast. In essence, we introduce a high-level EPS speci.cation language from which Bayesian networks that can diagnose multiple simultaneous failures are auto-generated, and we illustrate the feasibility of using arithmetic circuits, compiled from Bayesian networks, for real-time diagnosis on real-world EPSs of interest to NASA. The experimental system is a real-world EPS, namely the Advanced Diagnostic and Prognostic Testbed (ADAPT) located at the NASA Ames Research Center. In experiments with the ADAPT Bayesian network, which currently contains 503 discrete nodes and 579 edges, we .nd high diagnostic accuracy in scenarios where one to three faults, both in components and sensors, were inserted. The time taken to compute the most probable explanation using arithmetic circuits has a small mean of 0.2625 milliseconds and standard deviation of 0.2028 milliseconds. In experiments with data from ADAPT we also show that arithmetic circuit evaluation substantially outperforms joint tree propagation and variable elimination, two alternative algorithms for diagnosis using Bayesian network inference.

Mengshoel, Ole J.↗

NASA NTRS2008

Aspect-Oriented Monitoring of C Programs

The paper presents current work on extending ASPECTC with state machines, resulting in a framework for aspect-oriented monitoring of C programs. Such a framework can be used for testing purposes, or it can be part of a fault protection strategy. The long term goal is to explore the synergy between the fields of runtime verification, focused on program monitoring, and aspect-oriented programming, focused on more general program development issues. The work is inspired by the observation that most work in this direction has been done for JAVA, partly due to the lack of easily accessible extensible compiler frameworks for C. The work is performed using the SILVER extensible attribute grammar compiler framework, in which C has been defined as a host language. Our work consists of extending C with ASPECTC, and subsequently to extend ASPECTC with state machines.

runtime verifications↗

NASA NTRS2006

Architecture Adaptive Computing Environment

Architecture Adaptive Computing Environment (aCe) is a software system that includes a language, compiler, and run-time library for parallel computing. aCe was developed to enable programmers to write programs, more easily than was previously possible, for a variety of parallel computing architectures. Heretofore, it has been perceived to be difficult to write parallel programs for parallel computers and more difficult to port the programs to different parallel computing architectures. In contrast, aCe is supportable on all high-performance computing architectures. Currently, it is supported on LINUX clusters. aCe uses parallel programming constructs that facilitate writing of parallel programs. Such constructs were used in single-instruction/multiple-data (SIMD) programming languages of the 1980s, including Parallel Pascal, Parallel Forth, C*, *LISP, and MasPar MPL. In aCe, these constructs are extended and implemented for both SIMD and multiple- instruction/multiple-data (MIMD) architectures. Two new constructs incorporated in aCe are those of (1) scalar and virtual variables and (2) pre-computed paths. The scalar-and-virtual-variables construct increases flexibility in optimizing memory utilization in various architectures. The pre-computed-paths construct enables the compiler to pre-compute part of a communication operation once, rather than computing it every time the communication operation is performed.

Dorband, John E.↗

NASA NTRS2006

Dynamically Alterable Arrays of Polymorphic Data Types

An application library package was developed that represents data packets for Deep Space Network (DSN) message packets as dynamically alterable arrays composed of arbitrary polymorphic data types. The software was to address a limitation of the present state of the practice for having an array directly composed of a single monomorphic data type. This is a severe limitation when one is dealing with science data in that the types of objects one is dealing with are typically not known in advance and, therefore, are dynamic in nature. The unique feature of this approach is that it enables one to define at run-time the dynamic shape of the matrix with the ability to store polymorphic data types in each of its indices. Existing languages such as C and C++ have the restriction that the shape of the array must be known in advance and each of its elements be a monomorphic data type that is strictly defined at compile-time. This program can be executed on a variety of platforms. It can be distributed in either source code or binary code form. It must be run in conjunction with any one of a number of Lisp compilers that are available commercially or as shareware.

James, Mark↗

NASA NTRS2011

The Updated IAU MDC Catalogue of Photographic Meteor Orbits

The database of photographic meteor orbits of the IAU Meteor Data Center at the Astronomical Institute SAS has gradually been updated. To the 2003 version of 4581 photographic orbits compiled from 17 different stations and obtained in the period 1936-1996, additional new 211 orbits compiled from 7 sources have been added. Thus, the updated version of the catalogue contains 4792 photographic orbits (equinox J2000.0) available either in two separate orbital and geophysical data files or a file with the merged data. All the updated files with relevant documentation are available at the web of the IAU Meteor Data Center. Keywords astronomical databases photographic meteor orbits 1 Introduction Meteoroid orbits are a basic tool for investigation of distribution and spatial structure of the meteoroid population in the close surroundings of the Earth s orbit. However, information about them is usually widely scattered in literature and often in publications with limited circulation. Therefore, the IAU Comm. 22 during the 1976 IAU General Assembly proposed to establish a meteor data center for collection of meteor orbits recorded by photographic and radio techniques. The decision was confirmed by the next IAU GA in 1982 and the data center was established (Lindblad, 1987). The purpose of the data center was to acquire, format, check and disseminate information on precise meteoroid orbits obtained by multi-station techniques and the database gradually extended as documented in previous reports on the activity of the Meteor Data Center by Lindblad (1987, 1995, 1999 and 2001) or Lindblad and Steel (1993). Up to present, the database consists of 4581 photographic meteor orbits (Lindblad et al., 2005), 63.330 radar determined orbit: Harvard Meteor Project (1961-1965, 1968-1969), Adelaide (1960-1961, 1968-1969), Kharkov (1975), Obninsk (1967-1968), Mogadish (1969-1970) and 1425 video-recordings (Lindblad, 1999) to which additional 817 video meteors orbits published by Koten el al. (2003) were

Porubcan, V.↗

NASA NTRS2011

MicroShell Minimalist Shell for Xilinx Microprocessors

MicroShell is a lightweight shell environment for engineers and software developers working with embedded microprocessors in Xilinx FPGAs. (MicroShell has also been successfully ported to run on ARM Cortex-M1 microprocessors in Actel ProASIC3 FPGAs, but without project-integration support.) Micro Shell decreases the time spent performing initial tests of field-programmable gate array (FPGA) designs, simplifies running customizable one-time-only experiments, and provides a familiar-feeling command-line interface. The program comes with a collection of useful functions and enables the designer to add an unlimited number of custom commands, which are callable from the command-line. The commands are parameterizable (using the C-based command-line parameter idiom), so the designer can use one function to exercise hardware with different values. Also, since many hardware peripherals instantiated in FPGAs have reasonably simple register-mapped I/O interfaces, the engineer can edit and view hardware parameter settings at any time without stopping the processor. MicroShell comes with a set of support scripts that interface seamlessly with Xilinx's EDK tool. Adding an instance of MicroShell to a project is as simple as marking a check box in a library configuration dialog box and specifying a software project directory. The support scripts then examine the hardware design, build design-specific functions, conditionally include processor-specific functions, and complete the compilation process. For code-size constrained designs, most of the stock functionality can be excluded from the compiled library. When all of the configurable options are removed from the binary, MicroShell has an unoptimized memory footprint of about 4.8 kB and a size-optimized footprint of about 2.3 kB. Since MicroShell allows unfettered access to all processor-accessible memory locations, it is possible to perform live patching on a running system. This can be useful, for instance, if a bug is discovered in a routine but the system cannot be rebooted: Shell allows a skilled operator to directly edit the binary executable in memory. With some forethought, MicroShell code can be located in a different memory location from custom code, permitting the custom functionality to be overwritten at any time without stopping the controlling shell.

Werne, Thomas A.↗

NASA NTRS2011

Computer-Aided Parallelizer and Optimizer

The Computer-Aided Parallelizer and Optimizer (CAPO) automates the insertion of compiler directives (see figure) to facilitate parallel processing on Shared Memory Parallel (SMP) machines. While CAPO currently is integrated seamlessly into CAPTools (developed at the University of Greenwich, now marketed as ParaWise), CAPO was independently developed at Ames Research Center as one of the components for the Legacy Code Modernization (LCM) project. The current version takes serial FORTRAN programs, performs interprocedural data dependence analysis, and generates OpenMP directives. Due to the widely supported OpenMP standard, the generated OpenMP codes have the potential to run on a wide range of SMP machines. CAPO relies on accurate interprocedural data dependence information currently provided by CAPTools. Compiler directives are generated through identification of parallel loops in the outermost level, construction of parallel regions around parallel loops and optimization of parallel regions, and insertion of directives with automatic identification of private, reduction, induction, and shared variables. Attempts also have been made to identify potential pipeline parallelism (implemented with point-to-point synchronization). Although directives are generated automatically, user interaction with the tool is still important for producing good parallel codes. A comprehensive graphical user interface is included for users to interact with the parallelization process.

Jin, Haoqiang↗

NASA NTRS2007

ESAS-Derived Earth Departure Stage Design for Human Mars Exploration

The Vision for Space Exploration has set the nation on a course to have humans on Mars as early as 2030. To reduce the cost and risk associated with human Mars exploration, NASA is planning for the Mars architecture to leverage the lunar architecture as fully as possible. This study takes the defined launch vehicles and system capabilities from ESAS and extends their application to DRM 3.0 to design an Earth Departure Stage suitable for the cargo and crew missions to Mars. The impact of a propellant depot in LEO was assessed and sLzed for use with the EDS. To quantitatively assess and compare the effectiveness of alternative designs, an initial baseline architecture was defined using the ESAS launch vehicles and DRM 3.0. The baseline architecture uses three NTR engines, LH2 propellant, no propellant depot in LEO, and launches on the Ares I and Ares V. The Mars transfer and surface elements from DRM 3.0 were considered to be fixed payloads in the design of the EDS. Feasible architecture alternatives were identified from previous architecture studies and anticipated capabilities and compiled in a morphological matrix. ESAS FOMs were used to determine the most critical design attributes for the effectiveness of the EDS. The ESAS-derived FOMs used in this study to assess alternative designs are effectiveness and performance, affordability, reliability, and risk. The individual FOMs were prioritized using the AHP, a method for pairwise comparison. All trades performed were evaluated with respect to the weighted FOMs, creating a Pareto frontier of equivalently ideal solutions. Additionally, each design on the frontier was evaluated based on its fulfillment of the weighted FOMs using TOPSIS, a quantitative method for ordinal ranking of the alternatives. The designs were assessed in an integrated environment using physics-based models for subsystem analysis where possible. However, for certain attributes such as engine type, historical, performance-based mass estimating relations were more easily employed. The elements from the design process were integrated into a single loop, allowing for rapid iteration of subsystem analyses and compilation of resulting designs.

Flaherty, Kevin↗

NASA NTRS2011

EMU Lessons Learned Database

As manned space exploration takes on the task of traveling beyond low Earth orbit, many problems arise that must be solved in order to make the journey possible. One major task is protecting humans from the harsh space environment. The current method of protecting astronauts during Extravehicular Activity (EVA) is through use of the specially designed Extravehicular Mobility Unit (EMU). As more rigorous EVA conditions need to be endured at new destinations, the suit will need to be tailored and improved in order to accommodate the astronaut. The Objective behind the EMU Lessons Learned Database(LLD) is to be able to create a tool which will assist in the development of next-generation EMUs, along with maintenance and improvement of the current EMU, by compiling data from Failure Investigation and Analysis Reports (FIARs) which have information on past suit failures. FIARs use a system of codes that give more information on the aspects of the failure, but if one is unfamiliar with the EMU they will be unable to decipher the information. A goal of the EMU LLD is to not only compile the information, but to present it in a user-friendly, organized, searchable database accessible to all familiarity levels with the EMU; both newcomers and veterans alike. The EMU LLD originally started as an Excel database, which allowed easy navigation and analysis of the data through pivot charts. Creating an entry requires access to the Problem Reporting And Corrective Action database (PRACA), which contains the original FIAR data for all hardware. FIAR data are then transferred to, defined, and formatted in the LLD. Work is being done to create a web-based version of the LLD in order to increase accessibility to all of Johnson Space Center (JSC), which includes converting entries from Excel to the HTML format. FIARs related to the EMU have been completed in the Excel version, and now focus has shifted to expanding FIAR data in the LLD to include EVA tools and support hardware such as the Pistol Grip Tool (PGT) and the Battery Charger Module (BCM), while adding any recently closed EMU-related FIARs.

Matthews, Kevin M., Jr.↗