Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Programming Framework”

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 865 records · Page 48
All sourcesNASA NTRSDOE OSTI
NASA NTRS2006

A Concept for Run-Time Support of the Chapel Language

A document presents a concept for run-time implementation of other concepts embodied in the Chapel programming language. (Now undergoing development, Chapel is intended to become a standard language for parallel computing that would surpass older such languages in both computational performance in the efficiency with which pre-existing code can be reused and new code written.) The aforementioned other concepts are those of distributions, domains, allocations, and access, as defined in a separate document called "A Semantic Framework for Domains and Distributions in Chapel" and linked to a language specification defined in another separate document called "Chapel Specification 0.3." The concept presented in the instant report is recognition that a data domain that was invented for Chapel offers a novel approach to distributing and processing data in a massively parallel environment. The concept is offered as a starting point for development of working descriptions of functions and data structures that would be necessary to implement interfaces to a compiler for transforming the aforementioned other concepts from their representations in Chapel source code to their run-time implementations.

James, Mark↗
NASA NTRS2018

Automating Test Procedures Using Robot Software

This paper will discuss the project I was assigned during the 2018 Spring semester NIFS internship, what the project does for NASA, and what I contributed to the project. It will begin with a broad analysis of the types of software I worked on and how they were used to complete the project. Then, it will narrow in scope to concentrate on the group and parts of NASA assigned the project. Next, it will pay attention to the project itself and how it worked. After that, it will focus on my direct contributions to the project. Lastly, a few personal experiences I encountered to make my internship relatable. The initial points discussed will be an introduction to the basics of automated testing and the types of software used. Next, I will briefly discuss why these tools were chosen and whether or not they can be improved. Then, a look at where my group fits into the hierarchy of NASA, what the group working on my project did for NASA, and who were the entities working together for this project. Afterwards, a review of my involvement in the program, my development as an individual, and my new skills and abilities. Finally, a sense of involvement with the community through personal development will be demonstrated using unique experiences only available to me through this internship..

SikuliX↗
NASA NTRS2004

OTIS 3.2 Software Released

Trajectory, mission, and vehicle engineers concern themselves with finding the best way for an object to get from one place to another. These engineers rely upon special software to assist them in this. For a number of years, many engineers have used the OTIS program for this assistance. With OTIS, an engineer can fully optimize trajectories for airplanes, launch vehicles like the space shuttle, interplanetary spacecraft, and orbital transfer vehicles. OTIS provides four modes of operation, with each mode providing successively stronger optimization capability. The most powerful mode uses a mathematical method called implicit integration to solve what engineers and mathematicians call the optimal control problem. OTIS 3.2, which was developed at the NASA Glenn Research Center, is the latest release of this industry workhorse and features new capabilities for parameter optimization and mission design. OTIS stands for Optimal Control by Implicit Simulation, and it is implicit integration that makes OTIS so powerful at solving trajectory optimization problems. Why is this so important? The optimization process not only determines how to get from point A to point B, but it can also determine how to do this with the least amount of propellant, with the lightest starting weight, or in the fastest time possible while avoiding certain obstacles along the way. There are numerous conditions that engineers can use to define optimal, or best. OTIS provides a framework for defining the starting and ending points of the trajectory (point A and point B), the constraints on the trajectory (requirements like "avoid these regions where obstacles occur"), and what is being optimized (e.g., minimize propellant). The implicit integration method can find solutions to very complicated problems when there is not a lot of information available about what the optimal trajectory might be. The method was first developed for solving two-point boundary value problems and was adapted for use in OTIS. Implicit integration usually allows OTIS to find solutions to problems much faster than programs that use explicit integration and parametric methods. Consequently, OTIS is best suited to solving very complicated and highly constrained problems.

Riehl, John P.↗
NASA NTRS1993

An investigation of fighter aircraft agility

This report attempts to unify in a single document the results of a series of studies on fighter aircraft agility funded by the NASA Ames Research Center, Dryden Flight Research Facility and conducted at the University of Kansas Flight Research Laboratory during the period January 1989 through December 1993. New metrics proposed by pilots and the research community to assess fighter aircraft agility are collected and analyzed. The report develops a framework for understanding the context into which the various proposed fighter agility metrics fit in terms of application and testing. Since new metrics continue to be proposed, this report does not claim to contain every proposed fighter agility metric. Flight test procedures, test constraints, and related criteria are developed. Instrumentation required to quantify agility via flight test is considered, as is the sensitivity of the candidate metrics to deviations from nominal pilot command inputs, which is studied in detail. Instead of supplying specific, detailed conclusions about the relevance or utility of one candidate metric versus another, the authors have attempted to provide sufficient data and analyses for readers to formulate their own conclusions. Readers are therefore ultimately responsible for judging exactly which metrics are 'best' for their particular needs. Additionally, it is not the intent of the authors to suggest combat tactics or other actual operational uses of the results and data in this report. This has been left up to the user community. Twenty of the candidate agility metrics were selected for evaluation with high fidelity, nonlinear, non real-time flight simulation computer programs of the F-5A Freedom Fighter, F-16A Fighting Falcon, F-18A Hornet, and X-29A. The information and data presented on the 20 candidate metrics which were evaluated will assist interested readers in conducting their own extensive investigations. The report provides a definition and analysis of each metric; details of how to test and measure the metric, including any special data reduction requirements; typical values for the metric obtained using one or more aircraft types; and a sensitivity analysis if applicable. The report is organized as follows. The first chapter in the report presents a historical review of air combat trends which demonstrate the need for agility metrics in assessing the combat performance of fighter aircraft in a modern, all-aspect missile environment. The second chapter presents a framework for classifying each candidate metric according to time scale (transient, functional, instantaneous), further subdivided by axis (pitch, lateral, axial). The report is then broadly divided into two parts, with the transient agility metrics (pitch lateral, axial) covered in chapters three, four, and five, and the functional agility metrics covered in chapter six. Conclusions, recommendations, and an extensive reference list and biography are also included. Five appendices contain a comprehensive list of the definitions of all the candidate metrics; a description of the aircraft models and flight simulation programs used for testing the metrics; several relations and concepts which are fundamental to the study of lateral agility; an in-depth analysis of the axial agility metrics; and a derivation of the relations for the instantaneous agility and their approximations.

Valasek, John↗
NASA NTRS1986

Transportability, distributability and rehosting experience with a kernel operating system interface set

For the past two years, PRC has been transporting and installing a software engineering environment framework, the Automated Product control Environment (APCE), at a number of PRC and government sites on a variety of different hardware. The APCE was designed using a layered architecture which is based on a standardized set of interfaces to host system services. This interface set called the APCE Interface Set (AIS), was designed to support many of the same goals as the Common Ada Programming Support Environment (APSE) Interface Set (CAIS). The APCE was developed to provide support for the full software lifecycle. Specific requirements of the APCE design included: automation of labor intensive administrative and logistical tasks: freedom for project team members to use existing tools: maximum transportability for APCE programs, interoperability of APCE database data, and distributability of both processes and data: and maximum performance on a wide variety of operating systems. A brief description is given of the APCE and AIS, a comparison of the AIS and CAIS both in terms of functionality and of philosophy and approach and a presentation of PRC's experience in rehosting AIS and transporting APCE programs and project data. Conclusions are drawn from this experience with respect to both the CAIS efforts and Space Station plans.

Blumberg, F. C.↗
NASA NTRS1992

In the soft-to-hard technical spectrum: Where is software engineering?

In the computer journals and tabloids, there have been a plethora of articles written about the software engineering field. But while advocates of the need for an engineering approach to software development, it is impressive how many authors have treated the subject of software engineering without adequately addressing the fundamentals of what engineering as a discipline consists of. A discussion is presented of the various related facets of this issue in a logical framework to advance the thesis that the software development process is necessarily an engineering process. The purpose is to examine more of the details of the issue of whether or not the design and development of software for digital computer processing systems should be both viewed and treated as a legitimate field of professional engineering. Also, the type of academic and professional level education programs that would be required to support a software engineering discipline is examined.

Leibfried, Theodore F.↗
NASA NTRS2011

NASA Schedule Management Handbook

The purpose of schedule management is to provide the framework for time-phasing, resource planning, coordination, and communicating the necessary tasks within a work effort. The intent is to improve schedule management by providing recommended concepts, processes, and techniques used within the Agency and private industry. The intended function of this handbook is two-fold: first, to provide guidance for meeting the scheduling requirements contained in NPR 7120.5, NASA Space Flight Program and Project Management Requirements, NPR 7120.7, NASA Information Technology and Institutional Infrastructure Program and Project Requirements, NPR 7120.8, NASA Research and Technology Program and Project Management Requirements, and NPD 1000.5, Policy for NASA Acquisition. The second function is to describe the schedule management approach and the recommended best practices for carrying out this project control function. With regards to the above project management requirements documents, it should be noted that those space flight projects previously established and approved under the guidance of prior versions of NPR 7120.5 will continue to comply with those requirements until project completion has been achieved. This handbook will be updated as needed, to enhance efficient and effective schedule management across the Agency. It is acknowledged that most, if not all, external organizations participating in NASA programs/projects will have their own internal schedule management documents. Issues that arise from conflicting schedule guidance will be resolved on a case by case basis as contracts and partnering relationships are established. It is also acknowledged and understood that all projects are not the same and may require different levels of schedule visibility, scrutiny and control. Project type, value, and complexity are factors that typically dictate which schedule management practices should be employed.

Source record↗
NASA NTRS2004

Simulating Operation of a Planetary Rover

Simulating Operation of a Planetary Rover Rover Analysis, Modeling, and Simulations (ROAMS) is a computer program that simulates the operation of a robotic vehicle (rover) engaged in exploration of a remote planet. ROAMS is a roverspecific extension of the DARTS and Dshell programs, described in prior NASA Tech Briefs articles, which afford capabilities for mathematical modeling of the dynamics of a spacecraft as a whole and of its instruments, actuators, and other subsystems. ROAMS incorporates mathematical models of kinematics and dynamics of rover mechanical subsystems, sensors, interactions with terrain, solar panels and batteries, and onboard navigation and locomotion-control software. ROAMS provides a modular simulation framework that can be used for analysis, design, development, testing, and operation of rovers. ROAMS can be used alone for system performance and trade studies. Alternatively, ROAMS can be used in an operator-in-the-loop or flight-software closed-loop environment. ROAMS can also be embedded within other software for use in analysis and development of algorithms, or for Monte Carlo studies, using a variety of terrain models, to generate performance statistics. Moreover, taking advantage of realtime features of the underlying DARTS/Dshell simulation software, ROAMS can also be used for real-time simulations.

Jain, Abhinandan↗
NASA NTRS2014

CFD Vision 2030 Study: A Path to Revolutionary Computational Aerosciences

This report documents the results of a study to address the long range, strategic planning required by NASA's Revolutionary Computational Aerosciences (RCA) program in the area of computational fluid dynamics (CFD), including future software and hardware requirements for High Performance Computing (HPC). Specifically, the "Vision 2030" CFD study is to provide a knowledge-based forecast of the future computational capabilities required for turbulent, transitional, and reacting flow simulations across a broad Mach number regime, and to lay the foundation for the development of a future framework and/or environment where physics-based, accurate predictions of complex turbulent flows, including flow separation, can be accomplished routinely and efficiently in cooperation with other physics-based simulations to enable multi-physics analysis and design. Specific technical requirements from the aerospace industrial and scientific communities were obtained to determine critical capability gaps, anticipated technical challenges, and impediments to achieving the target CFD capability in 2030. A preliminary development plan and roadmap were created to help focus investments in technology development to help achieve the CFD vision in 2030.

Jeffrey P Slotnick↗
NASA NTRS2022

Impact Simulation of Composite Panels for Aerospace Applications

The aerospace research community has been working towards the development of a comprehensive framework for the design of composite structures at the component, subassembly, assembly, and system levels. Such a framework requires accurate, efficient and easy-to-use mathematical and computational models that are in sync with physical reality. The research work in this paper is designed to help an aerospace structural engineer move towards this goal by simulating dynamic impact to composite panels. First, the existing orthotropic visco-elastic visco-plastic material model in LS-DYNA commercial finite element program, MAT_COMPOSITE_TABULATED_PLASTICITY_DAMAGE (MAT_213) is enhanced with the development and use of rate-dependent damage data. Using state-of-the-art experimental procedures, impact validation test data are created. Second, the versatility of the constitutive model is examined by its ability to simulate a low velocity (27 ft/s, 8 m/s) impact test, and two high velocity impact tests (385–417 ft/s, 117–127 m/s) that straddle the ballistic limit of the projectile and the composite panels. Third, these impact events are modeled using three different finite element types – under-integrated and fully-integrated solid elements, and fully-integrated thin shell elements. Insight into accuracy versus numerical efficiency is gained by comparing the performance of solid versus thin shell elements. The numerical results show that accurate predictions of these impact events can be obtained with reasonable effort and care.

Simulations↗
NASA NTRSDate not supplied

Developing Concepts of Operations Using Multi-Step Tool Techniques With Large Language Models

The National Aeronautics and Space Administration (NASA) Air Mobility Pathfinders (AMP) project is developing and evaluating concepts of operations (ConOps) for safe, secure, and scalable Urban Air Mobility (UAM) operations. The AMP project’s Operational Concepts, Architecture, and Requirements Integration (OCARI) Team is using a Model Based System Engineering (MBSE) approach for integration, interoperability, and traceability of Advanced Air Mobility (AAM) ecosystems centered around urban air taxi services. The team’s goal is to define structures and behaviors needed for system feasibility, readiness, and interoperability, establish a UAM knowledge base, and trace and validate assumptions and requirements relevant to AAM. NASA Langley Research Center (LaRC) is spearheading an innovative digital engineering approach to integrate, communicate, and facilitate the research of multi-modal transportation systems. The Knowledge-based Digital Platform (KbDP) is a concept being developed that ties the workflows of Project Managers (PM), Principal Investigators (PI), and System Engineers together across organizational boundaries. It does so through the management of an information database defined by mathematical, data science, and system engineering principles. Machine Learning (ML) algorithms play a key role in this concept by extracting meaningful knowledge from relational and graph databases, document repositories, and system artifacts, which the human user leverages to greatly improve the efficiency and effectiveness of their research. Recent advancements in the field of Large Language Models (LLMs), specifically models trained for tool use, such as Command-R , now allow for the reliable implementation of single-step and multi-step tool-centric systems. These techniques provide the LLM with a set of tools, in our case Python functions, that can be called on to answer a much wider range of questions compared to LLMs implemented using a traditional single-source or Retrieval Augmented Generation (RAG) approach. Through this method, the LLM can pull information from multiple data sources, such as relational or graph databases, document repositories, application programming interfaces (APIs), and SysML artifacts depending on the user’s question. The LLM can also output the information in a variety of different formats, using output generation tools, such as CSV, UML, or SysML artifacts. Additionally, tools can be assigned roles and can work together to provide answers to queries in an “agent” like approach, similar to that implemented by Microsoft’s AutoGen framework where different agents can converse with each other to accomplish tasks. Previously, our team developed a chatbot system with “agent like” functionality in the form of different “modes” the user could select from a user interface (UI), this architecture can be seen on the left in figure 1. Three different modes were implemented, the first mode allowed the LLM to utilize the structures and algorithms within a graph database to trace UAM requirements. The second mode gave the LLM access to a vector search capable of providing relevant information from thousands of document pages related to UAM ConOps and requirements. The third mode served as a general assistant where users could enter open-ended questions and custom prompts to utilize the LLM for different use-cases. This system improved the process surrounding generating and analyzing information related to UAM requirements, however, the implementation provided a clunky user experience. Users were required to know what mode to select within the UI in advance before entering their question to the selected tool. Moreover, the different tools were isolated from each other, they lacked bidirectional links that would allow for tools to collaborate to generate better responses. Our team is working on a new architecture, seen on the right in the below figure, with the goal to address many of the UX shortcomings of our original system while improving the accuracy and depth of responses from the LLM. This new system will automatically select the appropriate tool to use based off the user’s question. Each tool will be capable of calling on any of the other tools available to the LLM, resulting in a collaborative pipeline where tools can pass data between other tools until enough data is received to generate an answer to the user’s question. Using a locally deployed, open-source, LLM, the NASA OCARI team, in collaboration with Collins Aerospace, will implement a prototype application that will bridge knowledge across multiple sources to assist System Engineers (SEs) with requirements discovery and tracing, research question and use case identification, and assumption validation. Such a system will also allow SEs to more easily, and intuitively, explore the AAM ecosystem, ultimately improving the efficiency and effectiveness of the SE's research and decision-making processes surrounding ConOps development and validation. In this session, our team will provide a video demonstration of our new prototype architecture in action. We will also present an overview of our prototype system architecture and talk about its advantages over traditional LLM deployments along with how those advantages can provide additional value to the field of System Engineering.

systems engineering↗
NASA NTRSDate not supplied

Investigating Risks Due to Artemis EVA Tempo Via Probabilistic Risk Assessment

Spaceflight operations pose unique challenges to crew health, safety, and resource management. As space agencies and private companies continue to push the boundaries of human exploration, it is essential to understand the risks associated with Extravehicular Activities (EVAs) and develop strategies to mitigate them. The tempo at which EVAs are conducted – the total number and frequency of these activities – can have a profound impact on medical risks, resource consumption, and overall mission success. Probabilistic risk assessment (PRA) provides a powerful framework for evaluating complex systems and identifying potential hazards. Our work employs the Medical Extensible Dynamic Probabilistic Risk Assessment Tool (MEDPRAT) [1] to simulate mission events, occurrence and treatment of medical conditions, and track the utilization of resources. Coupled with the Evidence Library [2], a medical evidence base for exploration-class missions developed by the Exploration Medical Capability within NASA’s Human Research Program, we can estimate these risks with increased fidelity and optimize medical kit contents to meet specific mission requirements. This presentation provides a detailed examination of how EVA tempo influences medical risk estimates for a lunar surface design reference mission. A comprehensive analysis is conducted to assess the additional mass and volume burden imposed on medical kits required to maintain adequate levels of risk mitigation. Furthermore, we estimate the distribution of the number of successful EVAs completed based on the level of task impairment imposed by medical events and flight rules related to specific medical events, such as decompression sickness.

Modeling↗
NASA NTRS1993

Explainable expert systems: A research program in information processing

Our work in Explainable Expert Systems (EES) had two goals: to extend and enhance the range of explanations that expert systems can offer, and to ease their maintenance and evolution. As suggested in our proposal, these goals are complementary because they place similar demands on the underlying architecture of the expert system: they both require the knowledge contained in a system to be explicitly represented, in a high-level declarative language and in a modular fashion. With these two goals in mind, the Explainable Expert Systems (EES) framework was designed to remedy limitations to explainability and evolvability that stem from related fundamental flaws in the underlying architecture of current expert systems.

Paris, Cecile L.↗
NASA NTRS2002

Intercontinental Bistatic Radar Test Observation of Asteroid 1998 WT24

We describe the first intercontinental planetary radar test performed in Italy observing the near Earth asteroid (NEA) 33342 (1998 WT24) in December 2001 by means of the bistatic configurations Goldstone (California, USA)-Medicina (Italy) and Evpatoria (Ukraine)-Medicina. The experiment goal was to characterize the system for realtime radar follow-up observations of NEAs and artificial orbiting debris, in the framework of a feasibility study which aims at using the Sardinia Radio Telescope, at present under construction, also as a planetary radar facility. We report the preliminary results of the radar observations carried out by the IRA-CNR (Instituto di Radioastronomia - Consiglio Nazionale delle Ricerche) and the OATo (Osservatorio Astronomico di Torino) groups, aimed at exploring the scientific potentials of a new space radar program, using the existing facilities in Italy. The planetary radar technique is uniquely capable of investigating geometry and surface properties of various solar system objects, demonstrating advantages over the optical methods in its high spatial resolution and ability to obtain three-dimensional images. A single radar detection allows to obtain extremely accurate orbital elements, improving the instantaneous positional uncertainties by orders of magnitude with respect to an optically determined orbit. Radar is a powerful means to spatially resolve NEAs by measuring the distribution of the echo power in time delay (range) and Doppler frequency (line-of-sight velocity) with extreme precision in each coordinate, as it provides detailed information about the target physical properties like size, shape, rotation, near-surface bulk density and roughness and internal density distribution. The Medicina 32m antenna had been successfully used for the first time as the receiving part of a bistatic configuration during a test experiment (September 2001) held to check the capabilities of the entire data acquisition system. This test was possible thanks to the collaboration undertaken with the Evpatoria radar station, and consisted in the observation of the ETALON-1 low orbit satellite

Righini, S.↗
NASA NTRS2008

Service-Oriented Architecture for NVO and TeraGrid Computing

The National Virtual Observatory (NVO) Extensible Secure Scalable Service Infrastructure (NESSSI) is a Web service architecture and software framework that enables Web-based astronomical data publishing and processing on grid computers such as the National Science Foundation's TeraGrid. Characteristics of this architecture include the following: (1) Services are created, managed, and upgraded by their developers, who are trusted users of computing platforms on which the services are deployed. (2) Service jobs can be initiated by means of Java or Python client programs run on a command line or with Web portals. (3) Access is granted within a graduated security scheme in which the size of a job that can be initiated depends on the level of authentication of the user.

Jacob, Joseph↗
NASA NTRS1993

Generating local addresses and communication sets for data-parallel programs

Generating local addresses and communication sets is an important issue in distributed-memory implementations of data-parallel languages such as High Performance Fortran. We show that for an array A affinely aligned to a template that is distributed across p processors with a cyclic(k) distribution, and a computation involving the regular section A, the local memory access sequence for any processor is characterized by a finite state machine of at most k states. We present fast algorithms for computing the essential information about these state machines, and extend the framework to handle multidimensional arrays. We also show how to generate communication sets using the state machine approach. Performance results show that this solution requires very little runtime overhead and acceptable preprocessing time.

Chatterjee, Siddhartha↗
NASA NTRS1980

A framework for automated decision making and problem solving

Problems can be subdivided into two main categories: well structured problems and ill structured problems. The first require routine repetitive decisions which are generally amenable to programmable decision processes. The second require novel nonprogrammable decision processes. The decision making processes can be subdivided into those representative of those done by humans and those done by machine. Many of such decision processes require a combination of humans d machines. Automated decision making and problem solving technologies are expected to have their greatest potential impact in the space program.

Heer, E.↗
NASA NTRS1992

Sources of mesoscale variability of gravity waves. I - Topographic excitation. II - Frontal, convective, and jet stream excitation

The effect of topography as a source of mesoscale variability was investigated using aircraft measurements of winds and temperature collected during the Global Atmospheric Sampling Program, with results showing marked increases in the variance of zonal and meridional wind speeds and of potential temperature over rough terrain. In addition, four cases of mesoscale variance enhancements of horizontal velocity and temperature due to frontal activity, nonfrontal convection, and wind shear were studied. The implications of these episodic enhancements of variances for the vertical transports of energy and momentum are considered in the framework of the gravity wave theory.

Nastrom, Gregory D.↗