Search NASA⌕ Search

SEARCH · Search NASA

Results for “programming tools”

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 631 records · Page 35
All sourcesNASA NTRSDOE OSTI
NASA NTRS2022

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↗
NASA NTRS1982

Software Engineering Laboratory (SEL) compendium of tools, revision 1

A set of programs used to aid software product development is listed. Known as software tools, such programs include requirements analyzers, design languages, precompilers, code auditors, code analyzers, and software librarians. Abstracts, resource requirements, documentation, processing summaries, and availability are indicated for most tools.

Source record↗
NASA NTRS2011

Discovery and New Frontiers Project Budget Analysis Tool

The Discovery and New Frontiers (D&NF) programs are multi-project, uncoupled programs that currently comprise 13 missions in phases A through F. The ability to fly frequent science missions to explore the solar system is the primary measure of program success. The program office uses a Budget Analysis Tool to perform "what-if" analyses and compare mission scenarios to the current program budget, and rapidly forecast the programs ability to meet their launch rate requirements. The tool allows the user to specify the total mission cost (fixed year), mission development and operations profile by phase (percent total mission cost and duration), launch vehicle, and launch date for multiple missions. The tool automatically applies inflation and rolls up the total program costs (in real year dollars) for comparison against available program budget. Thus, the tool allows the user to rapidly and easily explore a variety of launch rates and analyze the effect of changes in future mission or launch vehicle costs, the differing development profiles or operational durations of a future mission, or a replan of a current mission on the overall program budget. Because the tool also reports average monthly costs for the specified mission profile, the development or operations cost profile can easily be validate against program experience for similar missions. While specifically designed for predicting overall program budgets for programs that develop and operate multiple missions concurrently, the basic concept of the tool (rolling up multiple, independently-budget lines) could easily be adapted to other applications.

Newhouse, Marilyn E.↗
NASA NTRS1992

Application of engineering codes to the assessment of spacecraft charging induced hazards

One of the major hurdles to developing a better understanding of the environmentally induced interactions in spacecraft systems (spacecraft charging) is the lack of simple tools to analyze the behavior of the spacecraft in a sub-storm environment. The available tool, NASA Charging Analyzer Program (NASCAP), is expensive to use and treats only half of the problem - surface effects only. In response to this need, we have developed, under our IRAD Program, a set of engineering tools that operate on personal computers and addresses both the surface and bulk charging aspects of the interactions. These engineering codes utilize circuit analysis techniques and model simplifications to allow rapid computations. The codes were compared to both NASCAP predictions and to bulk charging data with excellent agreement for both phenomena. The models used in our engineering codes are shown, and in the engineering codes, the models are defined in terms of plates or triangles in an unconfined space. The predictions are based upon current balances to each plate. The code has routines to allow interactions between the plates to simulate 'barrier' effects. The agreement for the predicted differential surface voltages for the model is given. In conducting the comparison of engineering codes to NASCAP predictions, it was found that some inconsistencies existed in the NASCAP code that are not obvious to the user. The use of the grid imposes constraints that voltage gradients exist between the grid points. This allows the existence of voltage gradients in conductors and influences surface resistivity predictions. These points are discussed along with the predictions for treating these inconsistencies properly. The model predictions for a variable intensity substorm is also presented.

Stevens, N. J.↗
NASA NTRS2016

Best Practices for Fatigue Risk Management in Non-Traditional Shiftwork

Fatigue risk management programs provide effective tools to mitigate fatigue among shift workers. Although such programs are effective for typical shiftwork scenarios, where individuals of equal skill level can be divided into shifts to cover 24 hour operations, traditional programs are not sufficient for managing sleep loss among individuals with unique skill sets, in occupations where non-traditional schedules are required. Such operations are prevalent at NASA and in other high stress occupations, including among airline pilots, military personnel, and expeditioners. These types of operations require fatigue risk management programs tailored to the specific requirements of the mission. Without appropriately tailored fatigue risk management, such operations can lead to an elevated risk of operational failure, disintegration of teamwork, and increased risk of accidents and incidents. In order to design schedules for such operations, schedule planners must evaluate the impact of a given operation on circadian misalignment, acute sleep loss, chronic sleep loss and sleep inertia. In addition, individual-level factors such as morningness-eveningness preference and sleep disorders should be considered. After the impact of each of these factors has been identified, scheduling teams can design schedules that meet operational requirements, while also minimizing fatigue.

research↗
NASA NTRS1991

Programming with process groups: Group and multicast semantics

Process groups are a natural tool for distributed programming and are increasingly important in distributed computing environments. Discussed here is a new architecture that arose from an effort to simplify Isis process group semantics. The findings include a refined notion of how the clients of a group should be treated, what the properties of a multicast primitive should be when systems contain large numbers of overlapping groups, and a new construct called the causality domain. A system based on this architecture is now being implemented in collaboration with the Chorus and Mach projects.

Birman, Kenneth P.↗
NASA NTRS1994

Applications of automatic differentiation in computational fluid dynamics

Automatic differentiation (AD) is a powerful computational method that provides for computing exact sensitivity derivatives (SD) from existing computer programs for multidisciplinary design optimization (MDO) or in sensitivity analysis. A pre-compiler AD tool for FORTRAN programs called ADIFOR has been developed. The ADIFOR tool has been easily and quickly applied by NASA Langley researchers to assess the feasibility and computational impact of AD in MDO with several different FORTRAN programs. These include a state-of-the-art three dimensional multigrid Navier-Stokes flow solver for wings or aircraft configurations in transonic turbulent flow. With ADIFOR the user specifies sets of independent and dependent variables with an existing computer code. ADIFOR then traces the dependency path throughout the code, applies the chain rule to formulate derivative expressions, and generates new code to compute the required SD matrix. The resulting codes have been verified to compute exact non-geometric and geometric SD for a variety of cases. in less time than is required to compute the SD matrix using centered divided differences.

Green, Lawrence L.↗
NASA NTRS2008

Exploration Supply Chain Simulation

The Exploration Supply Chain Simulation project was chartered by the NASA Exploration Systems Mission Directorate to develop a software tool, with proper data, to quantitatively analyze supply chains for future program planning. This tool is a discrete-event simulation that uses the basic supply chain concepts of planning, sourcing, making, delivering, and returning. This supply chain perspective is combined with other discrete or continuous simulation factors. Discrete resource events (such as launch or delivery reviews) are represented as organizational functional units. Continuous resources (such as civil service or contractor program functions) are defined as enabling functional units. Concepts of fixed and variable costs are included in the model to allow the discrete events to interact with cost calculations. The definition file is intrinsic to the model, but a blank start can be initiated at any time. The current definition file is an Orion Ares I crew launch vehicle. Parameters stretch from Kennedy Space Center across and into other program entities (Michaud Assembly Facility, Aliant Techsystems, Stennis Space Center, Johnson Space Center, etc.) though these will only gain detail as the file continues to evolve. The Orion Ares I file definition in the tool continues to evolve, and analysis from this tool is expected in 2008. This is the first application of such business-driven modeling to a NASA/government-- aerospace contractor endeavor.

Source record↗
NASA NTRSDate not supplied

Water and Disasters Tools and Development Across the SERVIR Program and Lessons-Learned Within the Hindukush Himalayan Region

The NASA-USAID SERVIR program works in partnership with leading regional organizations around the globe to help developing countries use information provided by earth observing satellites and geospatial technologies. The SERVIR Applied Sciences Team (AST) is assembled on a 3-year rotating cycle to partner with these regional organizations on the joint development and implementation of tools and techniques that can be used operationally in each region. The Portfolio of AST projects address regional priorities in four thematic service areas: Land Cover, Land Use Change & Ecosystems; Water and water-related Disasters; Weather & Climate and Food Security & Agriculture. An important goal of AST is knowledge sharing across the different regional entities to share tools and technologies for the improvement of all. This talk will focus on the Water and Disasters service area and review how tools developed in the Hindu Kush Himalayan region in partnership with the International Centre for Integrated Mountain Development (ICIMOD) have evolved over the AST cycles. We will provide examples of stakeholder engagement both at ICIMOD and across the regional partners they support. We will also share recent examples and lessons learned with users from other SERVIR regions.

Lori A Schultz↗
NASA NTRS1981

Advanced space system analysis software. Technical, user, and programmer guide

The LASS computer program provides a tool for interactive preliminary and conceptual design of LSS. Eight program modules were developed, including four automated model geometry generators, an associated mass properties module, an appendage synthesizer module, an rf analysis module, and an orbital transfer analysis module. The existing rigid body controls analysis module was modified to permit analysis of effects of solar pressure on orbital performance. A description of each module, user instructions, and programmer information are included.

Farrell, C. E.↗
DOE OSTI2020

Greggd

greg(g)d - Global runtime for eBPF-enabled gathering (w/ gumption) daemon Recently the linux kernel has added support for low-level kernel monitoring and profiling through a in-kernel virtual machine. The tooling around these new features (the extended Berkley Packet Filter or eBPF for short) is not mature and is difficult to use. Benefits from eBPF are especially hard to realize while trying to do large scale deployments and integrate with existing metric analysis stacks. A tool was needed to enable loading and collecting data from eBPF programs on large scale HPC systems. Given the problems above it was obvious we needed some wrapper program to compile, load, and collect data from eBPF programs running in the kernel. This tool needed to be lightweight without a heavy set of dependencies, relatively stable between different kernel versions, and integrate nicely with existing widely used metric collection tools. We wrote a program that wraps the eBPF tooling and sends data to our metric gathering tool. eBPF programs are either compiled using the host compiler stack, or loaded in the kernel directly from an object file. These programs are then attached to the system calls that we want to profile. Whenever these system calls are run, the eBPF program collects information of interest and writes that to memory. Our wrapper program polls these memory locations, reads and formats the data, then sends the information to a local unix socket. Our other monitoring tools are configured to read from that socket and send it to the rest of our metric monitoring stack for analysis.

Voss, Joseph [Oak Ridge National Lab. (ORNL), Oak ↗
NASA NTRS1981

AIRCL: A programmed system for generating NC tapes for airplane models. User's manual

A computer program is presented which calculates the cutter location file needed to machine models of airplane wings or wing-fuselage combinations on numerically controlled machine tools. Input to the program is a data file consisting of coordinates on the fuselage and wing. From this data file, the program calculates tool offsets, determines the intersection between wing and fuselage tool paths, and generates additional information needed to machine the fuselage and/or wing. Output from the program can be post processed for use on a variety of milling machines. Information on program structure and methodology is given as well as the user's manual for implementation of the program.

Akgerman, N.↗
NASA NTRS2005

Template for Systems Engineering Tools Trade Study

A discussion of Systems Engineering tools brings out numerous preferences and reactions regarding tools of choice as well as the functions those tools are to perform. A recent study of Systems Engineering Tools for a new Program illustrated the need for a generic template for use by new Programs or Projects to determine the toolset appropriate for their use. This paper will provide the guidelines new initiatives can follow and tailor to their specific needs, to enable them to make their choice of tools in an efficient and informed manner. Clearly, those who perform purely technical functions will need different tools than those who perform purely systems engineering functions. And, everyone has tools they are comfortable with. That degree of comfort is frequently the deciding factor in tools choice rather than an objective study of all criteria and weighting factors. This paper strives to produce a comprehensive list of criteria for selection with suggestions for weighting factors based on a number of assumptions regarding the given Program or Project. In addition, any given Program will begin with assumptions for its toolset based on Program size, tool cost, user base and technical needs. In providing a template for tool selection, this paper will guide the reader through assumptions based on Program need; decision criteria; potential weighting factors; the need for a compilation of available tools; the importance of tool demonstrations; and finally a down selection of tools. While specific vendors cannot be mentioned in this work, it is expected that this template could serve other Programs in the formulation phase by alleviating the trade study process of some of its subjectivity.

Michelle D Bailey↗
NASA NTRS1991

Plotting Orbital Trajectories For Maneuvers

Interactive Orbital Trajectory Planning Tool (EIVAN) computer program is forward-looking interactive orbit-trajectory-plotting software tool for use with proximity operations (operations occurring within 1-km sphere of space station) and other maneuvers. Developed to plot resulting trajectories, to provide better comprehension of effects of orbital mechanics, and to help user develop heuristics for planning missions on orbit. Program runs with Microsoft's Excel for execution on MacIntosh computer running MacIntosh OS.

Brody, Adam R.↗
NASA NTRS1988

Ada software productivity prototypes: A case study

A case study of the impact of Ada on a Command and Control project completed at the Jet Propulsion Laboratory (JPL) is given. The data for this study was collected as part of a general survey of software costs and productivity at JPL and other NASA sites. The task analyzed is a successful example of the use of rapid prototyping as applied to command and control for the U.S. Air Force and provides the U.S. Air Force Military Airlift Command with the ability to track aircraft, air crews and payloads worldwide. The task consists of a replicated database at several globally distributed sites. The local databases at each site can be updated within seconds after changes are entered at any one site. The system must be able to handle up to 400,000 activities per day. There are currently seven sites, each with a local area network of computers and a variety of user displays; the local area networks are tied together into a single wide area network. Using data obtained for eight modules, totaling approximately 500,000 source lines of code, researchers analyze the differences in productivities between subtasks. Factors considered are percentage of Ada used in coding, years of programmer experience, and the use of Ada tools and modern programming practices. The principle findings are the following. Productivity is very sensitive to programmer experience. The use of Ada software tools and the use of modern programming practices are important; without such use Ada is just a large complex language which can cause productivity to decrease. The impact of Ada on development effort phases is consistent with earlier reports at the project level but not at the module level.

Hihn, Jairus M.↗
DOE OSTI2019

Neutron imaging analysis using jupyter Python notebook

Abstract Independently of the image modality (x-rays, neutrons, etc), image data analysis requires normalization, a preprocessing step. While the normalization can sometimes easily be generalized, the analysis is, in most cases, specific to an experiment and a sample. Although many tools (MATLAB, ImageJ, VG Studio…) offer a large collection of pre-programmed image analysis tools, they usually require a learning step that can be lengthy depending on the skills of the end user. We have implemented Jupyter Python notebooks to allow easy and straightforward data analysis, along with live interaction with the data. Jupyter notebooks require little programming knowledge and the steep learning curve is bypassed. Most importantly, each notebook can be tailored to a specific experiment and sample with minimized effort. Here, we present the pros and cons of the main methods to analyse data and show the reason why we have found that Jupyter Python notebooks are well suited for imaging data processing, visualization and analysis.

Bilheux, Jean-Christophe (ORCID:0000000321726487)↗
DOE OSTI2021

Building Efficiency Targeting Tool for Energy Retrofits (BETTER) Application Programing Interface (API) (BETTER API) v1.0

The BETTER API allows advanced users and developers to access BETTER's analytical functionalities via HTTP requests from their own software platform without using the BETTER web-interface. API users prepare the input data and analysis configurations in a JSON format and send it to the web application via an HTTP request. The web application runs the analytical workflow on the back end and returns an HTTP response in JSON format. The user can then decide to render the results or further process it.

Szum, Carolyn↗