SEARCH · Search NASA

Results for “Building codes”

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 91 records · Page 5

All sources NASA NTRS DOE OSTI

NASA NTRS2013

Science Opportunity Analyzer (SOA) Version 8

SOA allows scientists to plan spacecraft observations. It facilitates the identification of geometrically interesting times in a spacecraft s orbit that a user can use to plan observations or instrument-driven spacecraft maneuvers. These observations can then be visualized multiple ways in both two- and three-dimensional views. When observations have been optimized within a spacecraft's flight rules, the resulting plans can be output for use by other JPL uplink tools. Now in its eighth major version, SOA improves on these capabilities in a modern and integrated fashion. SOA consists of five major functions: Opportunity Search, Visualization, Observation Design, Constraint Checking, and Data Output. Opportunity Search is a GUI-driven interface to existing search engines that can be used to identify times when a spacecraft is in a specific geometrical relationship with other bodies in the solar system. This function can be used for advanced mission planning as well as for making last-minute adjustments to mission sequences in response to trajectory modifications. Visualization is a key aspect of SOA. The user can view observation opportunities in either a 3D representation or as a 2D map projection. Observation Design allows the user to orient the spacecraft and visualize the projection of the instrument field of view for that orientation using the same views as Opportunity Search. Constraint Checking is provided to validate various geometrical and physical aspects of an observation design. The user has the ability to easily create custom rules or to use official project-generated flight rules. This capability may also allow scientists to easily assess the cost to science if flight rule changes occur. Data Output allows the user to compute ancillary data related to an observation or to a given position of the spacecraft along its trajectory. The data can be saved as a tab-delimited text file or viewed as a graph. SOA combines science planning functionality unique to both JPL and the sponsoring spacecraft. SOA is able to ingest JPL SPICE Kernels that are used to drive the tool and its computations. A Percy search engine is then included that identifies interesting time periods for the user to build observations. When observations are then built, flight-like orientation algorithms replicate spacecraft dynamics to closely simulate the flight spacecraft s dynamics. SOA v8 represents large steps forward from SOA v7 in terms of quality, reliability, maintainability, efficiency, and user experience. A tailored agile development environment has been built around SOA that provides automated unit testing, continuous build and integration, a consolidated Web-based code and documentation storage environment, modern Java enhancements, and a focus on usability

Witoff, Robert J.↗

NASA NTRS2006

Deductive Glue Code Synthesis for Embedded Software Systems Based on Code Patterns

Automated code synthesis is a constructive process that can be used to generate programs from specifications. It can, thus, greatly reduce the software development cost and time. The use of formal code synthesis approach for software generation further increases the dependability of the system. Though code synthesis has many potential benefits, the synthesis techniques are still limited. Meanwhile, components are widely used in embedded system development. Applying code synthesis to component based software development (CBSD) process can greatly enhance the capability of code synthesis while reducing the component composition efforts. In this paper, we discuss the issues and techniques for applying deductive code synthesis techniques to CBSD. For deductive synthesis in CBSD, a rule base is the key for inferring appropriate component composition. We use the code patterns to guide the development of rules. Code patterns have been proposed to capture the typical usages of the components. Several general composition operations have been identified to facilitate systematic composition. We present the technique for rule development and automated generation of new patterns from existing code patterns. A case study of using this method in building a real-time control system is also presented.

automated code synthesis↗

NASA NTRSDate not supplied

Simulation of Radiation-Induced DNA Damage With the Code RITRACKS

INTRODUCTION DNA damage is one of the most physiologically important effects of ionizing radiation. Clustered DNA damage events, like double-strand breaks (DSBs), have the most notable biological consequences. DNA damage types depend on both the track structure of the radiation and the spatial organization of the DNA. High linear energy transfer (LET) charged nuclei, found in galactic cosmic rays (GCR), are known to produce large numbers of complex DNA damage events. The human genome is packaged into chromatin, which can take on locus-dependent and cell type-dependent spatial conformations that correspond to epigenetic states, such as more open, extended structures in transcriptionally active chromatin. These epigenetic differences can affect DNA break patterns in response to ionizing radiation, potentially creating distinct DNA repair and signaling outcomes across the genome in different cells. MATERIAL AND METHODS The code RITRACKS (Relativistic Ion Tracks), which simulates stochastic radiation track structures and radiation chemistry, was used to model damage on isolated and histone-bound DNA by various types of ions and photons. The changes made to the code to perform radiation-induced DNA damage, and simulation results on single nucleosomes are given in our recent paper. In this work, the DNA building capabilities of RITRACKS have been extended to simulate more complex DNA structures build on the coarse-grain simulation framework meso-WLCsim. This code can sample generic chromatin fiber conformation ensembles based on the geometry of nucleosomes and mechanical properties of DNA. Using RITRACKS, we simulated the fragment length distributions (FLD) of irradiated DNA structures built using the chromatin conformations of WLCsim and obtained results representative of those obtained with Radiation-Induced Correlated Cleavage with sequencing (RICC-Seq) experiments [6]. We have also performed Fe ion and photon irradiations of K562, IMR90, BJ and RPE-1 cells at NSRL to experimentally validate results. Sample processing and data analysis are in progress and any available preliminary results will be discussed. DISCUSSION The recent updates in the code RITRACKS allow the calculation of several quantities such as the DNA damage yield and the FLD. This approach can be used to model epigenetic state-specific chromatin structure parameters to leverage the epigenetic state data available for many human cell types to infer relative DNA damage sensitivity among genomic loci.

I Plante↗

NASA NTRS2003

Implementation of Premixed Equilibrium Chemistry Capability in OVERFLOW

An implementation of premixed equilibrium chemistry has been completed for the OVERFLOW code, a chimera capable, complex geometry flow code widely used to predict transonic flowfields. The implementation builds on the computational efficiency and geometric generality of the solver.

Olsen, M. E.↗

NASA NTRS2004

Implementation of Premixed Equilibrium Chemistry Capability in OVERFLOW

Olsen, Mike E.↗

NASA NTRS2005

Characterization of the Space Shuttle Ascent Debris using CFD Methods

After video analysis of space shuttle flight STS-107's ascent showed that an object shed from the bipod-ramp region impacted the left wing, a transport analysis was initiated to determine a credible flight path and impact velocity for the piece of debris. This debris transport analysis was performed both during orbit, and after the subsequent re-entry accident. The analysis provided an accurate prediction of the velocity a large piece of foam bipod ramp would have as it impacted the wing leading edge. This prediction was corroborated by video analysis and fully-coupled CFD/six degree of freedom (DOF) simulations. While the prediction of impact velocity was accurate enough to predict critical damage in this case, one of the recommendations of the Columbia Accident Investigation Board (CAIB) for return-to-flight (RTF) was to analyze the complete debris environment experienced by the shuttle stack on ascent. This includes categorizing all possible debris sources, their probable geometric and aerodynamic characteristics, and their potential for damage. This paper is chiefly concerned with predicting the aerodynamic characteristics of a variety of potential debris sources (insulating foam and cork, nose-cone ablator, ice, ...) for the shuttle ascent configuration using CFD methods. These aerodynamic characteristics are used in the debris transport analysis to predict flight path, impact velocity and angle, and provide statistical variation to perform risk analyses where appropriate. The debris aerodynamic characteristics are difficult to determine using traditional methods, such as static or dynamic test data, due to the scaling requirements of simulating a typical debris event. The use of CFD methods has been a critical element for building confidence in the accuracy of the debris transport code by bridging the gap between existing aerodynamic data and the dynamics of full-scale, in-flight events.

Murman, Scott M.↗

NASA NTRS2014

Remote Software Application and Display Development

The era of the shuttle program has come to an end, but only to give rise to newer and more exciting projects. Now is the time of the Orion spacecraft, a work of art designed to exceed all previous endeavors of man. NASA is exiting the time of exploration and is entering a new period, a period of pioneering. With this new mission, many of NASAs organizations must undergo a great deal of change and development to support the Orion missions. The Spaceport Command and Control System (SCCS) is the new system that will provide NASA the ability to launch rockets into orbit and thus control Orion and other spacecraft as the goal of populating Mars becomes ever increasingly tangible. Since the previous control system, Launch Processing System (LPS), was primarily designed to launch the shuttles, SCCS was needed as Kennedy Space Center (KSC) reorganized to a multiuser spaceport for commercial flights, providing a more versatile control over rockets. Within SCCS, is the Launch Control System (LCS), which is the remote software behind the command and monitoring of flight and ground system hardware. This internship at KSC has involved two main components in LCS, including Remote Software Application and Display development. The display environment provides a graphical user interface for an operator to view and see if any cautions are raised, while the remote applications are the backbone that communicate with hardware, and then relay the data back to the displays. These elements go hand in hand as they provide monitoring and control over hardware and software alike from the safety of the Launch Control Center. The remote software applications are written in Application Control Language (ACL), which must undergo unit testing to ensure data integrity. This paper describes both the implementation and writing of unit tests in ACL code for remote software applications, as well as the building of remote displays to be used in the Launch Control Center (LCC).

ACL↗

NASA NTRS1999

FDNS CFD Code Benchmark for RBCC Ejector Mode Operation

Computational Fluid Dynamics (CFD) analysis results are compared with benchmark quality test data from the Propulsion Engineering Research Center's (PERC) Rocket Based Combined Cycle (RBCC) experiments to verify fluid dynamic code and application procedures. RBCC engine flowpath development will rely on CFD applications to capture the multi-dimensional fluid dynamic interactions and to quantify their effect on the RBCC system performance. Therefore, the accuracy of these CFD codes must be determined through detailed comparisons with test data. The PERC experiments build upon the well-known 1968 rocket-ejector experiments of Odegaard and Stroup by employing advanced optical and laser based diagnostics to evaluate mixing and secondary combustion. The Finite Difference Navier Stokes (FDNS) code was used to model the fluid dynamics of the PERC RBCC ejector mode configuration. Analyses were performed for both Diffusion and Afterburning (DAB) and Simultaneous Mixing and Combustion (SMC) test conditions. Results from both the 2D and the 3D models are presented.

Holt, James B.↗

NASA NTRS2000

FDNS CFD Code Benchmark for RBCC Ejector Mode Operation: Continuing Toward Dual Rocket Effects

Computational Fluid Dynamics (CFD) analysis results are compared with benchmark quality test data from the Propulsion Engineering Research Center's (PERC) Rocket Based Combined Cycle (RBCC) experiments to verify fluid dynamic code and application procedures. RBCC engine flowpath development will rely on CFD applications to capture the multi -dimensional fluid dynamic interactions and to quantify their effect on the RBCC system performance. Therefore, the accuracy of these CFD codes must be determined through detailed comparisons with test data. The PERC experiments build upon the well-known 1968 rocket-ejector experiments of Odegaard and Stroup by employing advanced optical and laser based diagnostics to evaluate mixing and secondary combustion. The Finite Difference Navier Stokes (FDNS) code [2] was used to model the fluid dynamics of the PERC RBCC ejector mode configuration. Analyses were performed for the Diffusion and Afterburning (DAB) test conditions at the 200-psia thruster operation point, Results with and without downstream fuel injection are presented.

West, Jeff↗

NASA NTRSDate not supplied

The Detection of Aromatic Amino Acids in CR Chondrites Suggests They are Prebiotically Plausible

Amino acids (AAs) are the building blocks of proteins and are essential for life on Earth. Sources of AAs on early Earth range from exogenous sources such as delivery from extraterrestrial materials(i.e., meteorites, interplanetary dust particles, comets, etc.) to endogenous sources including chemical reactions in hydrothermal vents or atmospheric mixtures. Analyses of AAs of extraterrestrial origin from meteorites and laboratory studies of simulated prebiotic environments revealed that a diverse set of abiotically produced AAs may have been present on early Earth. However only a fraction of these AAs is found within the proteins of living organisms. Of the22 genetically encoded (proteinogenic) AAs, 20 occur in the standard genetic code (SGC) and are used by nearly all living organisms to build proteins. The universality of this AA alphabet suggests the presence and incorporation of these specific AAs occurred early in the evolution of life.

A. S. Burton↗

NASA NTRS1996

Scheduling System Assessment, and Development and Enhancement of Re-engineered Version of GPSS

The objective of this project is two-fold. First to provide an evaluation of a commercially developed version of the ground processing scheduling system (GPSS) for its applicability to the Kennedy Space Center (KSC) ground processing problem. Second, to work with the KSC GPSS development team and provide enhancement to the existing software. Systems reengineering is required to provide a sustainable system for the users and the software maintenance group. Using the LISP profile prototype code developed by the GPSS reverse reengineering groups as a building block, we have implemented the resource deconfliction portion of GPSS in common LISP using its object oriented features. The prototype corrects and extends some of the deficiencies of the current production version, plus it uses and builds on the classes from the development team's profile prototype.

Loganantharaj, Rasiah↗

NASA NTRS2004

Implementation of Finite Rate Chemistry Capability in OVERFLOW

An implementation of both finite rate and equilibrium chemistry have been completed for the OVERFLOW code, a chimera capable, complex geometry flow code widely used to predict transonic flow fields. The implementation builds on the computational efficiency and geometric generality of the solver.

Olsen, M. E.↗

NASA NTRS2004

The Role of Ontologies in Schema-based Program Synthesis

Program synthesis is the process of automatically deriving executable code from (non-executable) high-level specifications. It is more flexible and powerful than conventional code generation techniques that simply translate algorithmic specifications into lower-level code or only create code skeletons from structural specifications (such as UML class diagrams). Key to building a successful synthesis system is specializing to an appropriate application domain. The AUTOBAYES and AUTOFILTER systems, under development at NASA Ames, operate in the two domains of data analysis and state estimation, respectively. The central concept of both systems is the schema, a representation of reusable computational knowledge. This can take various forms, including high-level algorithm templates, code optimizations, datatype refinements, or architectural information. A schema also contains applicability conditions that are used to determine when it can be applied safely. These conditions can refer to the initial specification, to intermediate results, or to elements of the partially-instantiated code. Schema-based synthesis uses AI technology to recursively apply schemas to gradually refine a specification into executable code. This process proceeds in two main phases. A front-end gradually transforms the problem specification into a program represented in an abstract intermediate code. A backend then compiles this further down into a concrete target programming language of choice. A core engine applies schemas on the initial problem specification, then uses the output of those schemas as the input for other schemas, until the full implementation is generated. Since there might be different schemas that implement different solutions to the same problem this process can generate an entire solution tree. AUTOBAYES and AUTOFILTER have reached the level of maturity where they enable users to solve interesting application problems, e.g., the analysis of Hubble Space Telescope images. They are large (in total around 100kLoC Prolog), knowledge intensive systems that employ complex symbolic reasoning to generate a wide range of non-trivial programs for complex application do- mains. Their schemas can have complex interactions, which make it hard to change them in isolation or even understand what an existing schema actually does. Adding more capabilities by increasing the number of schemas will only worsen this situation, ultimately leading to the entropy death of the synthesis system. The root came of this problem is that the domain knowledge is scattered throughout the entire system and only represented implicitly in the schema implementations. In our current work, we are addressing this problem by making explicit the knowledge from Merent parts of the synthesis system. Here; we discuss how Gruber's definition of an ontology as an explicit specification of a conceptualization matches our efforts in identifying and explicating the domain-specific concepts. We outline the dual role ontologies play in schema-based synthesis and argue that they address different audiences and serve different purposes. Their first role is descriptive: they serve as explicit documentation, and help to understand the internal structure of the system. Their second role is prescriptive: they provide the formal basis against which the other parts of the system (e.g., schemas) can be checked. Their final role is referential: ontologies also provide semantically meaningful "hooks" which allow schemas and tools to access the internal state of the program derivation process (e.g., fragments of the generated code) in domain-specific rather than language-specific terms, and thus to modify it in a controlled fashion. For discussion purposes we use AUTOLINEAR, a small synthesis system we are currently experimenting with, which can generate code for solving a system of linear equations, Az = b.

Bures, Tomas↗

NASA NTRS2015

Experimental Products Development Team (EPDT) Supporting New AWIPS : Capabilities - Part 2

In 2012, the Experimental Products Development Team (EPDT) was formed within NASA's Short-term Prediction Research and Transition (SPoRT) Center to create training for development of plug‐ins to extend the National Weather Service (NWS) Advanced Weather Interactive Processing System (AWIPS) version 2. The broader atmospheric science community had a need for AWIPS II development training being created at SPoRT and EPDT was expanded to include other groups who were looking for training. Since the expansion of the group occurred, EPDT has provided AWIPS II development training to over thirty participants spanning a wide variety of groups such as NWS Systems Engineering Center, NWS Meteorological Development Laboratory, and several NOAA Cooperative Institutes. Participants within EPDT solidify their learning experience through hands‐on learning and by participating in a "code-sprint" in which they troubleshoot existing and develop plug‐ins. The hands‐on learning workshop is instructor lead with participants completing exercises within the AWIPS II Development Environment. During the code sprints EPDT groups work on projects important to the community and have worked on various plug‐ins such as an RGB image recipe creation tool, and an mPing (crowd sourced precipitation type reporting system) ingest and display. EPDT has developed a well‐defined training regime which prepares participants to fully develop plug‐ins for the extendible AWIPS II architecture from ingest to the display of new data. SPoRT has hosted 2 learning workshops and 1 code sprint over the last two years, and continues to build and shape the EPDT group based on feedback from previous workshops. The presentation will provide an overview of EPDT current and future activities, and best practices developed within EPDT.

Burks, Jason E.↗

NASA NTRS1983

Development of V/STOL methodology based on a higher order panel method

The development of a computational technique to predict the complex flowfields of V/STOL aircraft was initiated in which a number of modules and a potential flow aerodynamic code were combined in a comprehensive computer program. The modules were developed in a building-block approach to assist the user in preparing the geometric input and to compute parameters needed to simulate certain flow phenomena that cannot be handled directly within a potential flow code. The PAN AIR aerodynamic code, which is higher order panel method, forms the nucleus of this program. PAN AIR's extensive capability for allowing generalized boundary conditions allows the modules to interact with the aerodynamic code through the input and output files, thereby requiring no changes to the basic code and easy replacement of updated modules.

Bhateley, I. C.↗

NASA NTRS2013

Adoption of Test Driven Development and Continuous Integration for the Development of the Trick Simulation Toolkit

This paper describes the adoption of a Test Driven Development approach and a Continuous Integration System in the development of the Trick Simulation Toolkit, a generic simulation development environment for creating high fidelity training and engineering simulations at the NASA/Johnson Space Center and many other NASA facilities. It describes what was learned and the significant benefits seen, such as fast, thorough, and clear test feedback every time code is checked-in to the code repository. It also describes a system that encourages development of code that is much more flexible, maintainable, and reliable. The Trick Simulation Toolkit development environment provides a common architecture for user-defined simulations. Trick builds executable simulations using user-supplied simulation-definition files (S_define) and user supplied "model code". For each Trick-based simulation, Trick automatically provides job scheduling, checkpoint / restore, data-recording, interactive variable manipulation (variable server), and an input-processor. Also included are tools for plotting recorded data and various other supporting tools and libraries. Trick is written in C/C++ and Java and supports both Linux and MacOSX. Prior to adopting this new development approach, Trick testing consisted primarily of running a few large simulations, with the hope that their complexity and scale would exercise most of Trick's code and expose any recently introduced bugs. Unsurprising, this approach yielded inconsistent results. It was obvious that a more systematic, thorough approach was required. After seeing examples of some Java-based projects that used the JUnit test framework, similar test frameworks for C and C++ were sought. Several were found, all clearly inspired by JUnit. Googletest, a freely available Open source testing framework, was selected as the most appropriate and capable. The new approach was implemented while rewriting the Trick memory management component, to eliminate a fundamental design flaw. The benefits became obvious almost immediately, not just in the correctness of the individual functions and classes but also in the correctness and flexibility being added to the overall design. Creating code to be testable, and testing as it was created resulted not only in better working code, but also in better-organized, flexible, and readable (i.e., articulate) code. This was, in essence the Test-driven development (TDD) methodology created by Kent Beck. Seeing the benefits of Test Driven Development, other Trick components were refactored to make them more testable and tests were designed and implemented for them.

Penn, John M.↗

NASA NTRS2022

Exploring the MeV Sky With A Combined Coded Mask and Compton Telescope: the Galactic Explorer With A Coded Aperture Mask Compton Telescope (GECCO)

The sky at MeV energies is currently poorly explored. Here we present an innovative mission concept that builds upon the heritage of past and current missions improving the sensitivity and, very importantly, the angular resolution. This consists in combining a Compton telescope and a coded-mask telescope. We delineate the motivation for such a concept and we define the scientific goals for such a mission. The Galactic Explorer with a Coded Aperture Mask Compton Telescope (GECCO) is a novel concept for a next-generation telescope covering hard X-ray and soft gamma-ray energies. The potential and importance of this approach that bridges the observational gap in the MeV energy range are presented. With the unprecedented angular resolution of the coded mask telescope combined with the sensitive Compton telescope, a mission such as GECCO can disentangle the discrete sources from the truly diffuse emission. Individual Galactic and extragalactic sources are detected. This also allows to understand the gamma-ray Galactic center excess and the Fermi Bubbles, and to trace the low-energy cosmic rays, and their propagation in the Galaxy. Nuclear and annihilation lines are spatially and spectrally resolved from the continuum emission and from sources, addressing the role of low-energy cosmic rays in star formation and galaxy evolution, the origin of the 511 keV positron line, fundamental physics, and the chemical enrichment in the Galaxy. Such an instrument also detects explosive transient gamma-ray sources, which, in turn, enables identifying and studying the astrophysical objects that produce gravitational waves and neutrinos in a multi-messenger context. By looking at a poorly explored energy band it also allows discoveries of new astrophysical phenomena.

Elena Orlando↗

NASA NTRS1986

Coding for Electronic Mail

Scheme for coding facsimile messages promises to reduce data transmission requirements to one-tenth current level. Coding scheme paves way for true electronic mail in which handwritten, typed, or printed messages or diagrams sent virtually instantaneously - between buildings or between continents. Scheme, called Universal System for Efficient Electronic Mail (USEEM), uses unsupervised character recognition and adaptive noiseless coding of text. Image quality of resulting delivered messages improved over messages transmitted by conventional coding. Coding scheme compatible with direct-entry electronic mail as well as facsimile reproduction. Text transmitted in this scheme automatically translated to word-processor form.

Rice, R. F.↗