Search NASA⌕ Search

SEARCH · Search NASA

Results for “Multiple program”

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 19 records
All sourcesNASA NTRSDOE OSTI
DOE OSTI2023

Extending the thermodynamic form factor bootstrap program: multiple particle-hole excitations, crossing symmetry, and reparameterization invariance

In this study, we further the thermodynamic bootstrap program which involves a set of recently developed ideas used to determine thermodynamic form factors of local operators in integrable quantum field theories. These form factors are essential building blocks for dynamic correlation functions at finite temperatures or non-equilibrium stationary states. In this work we extend this program in three ways. Firstly, we demonstrate that the conjectured annihilation pole axiom is valid in the low energy particle-hole excitations. Secondly, we introduce a crossing relation, which establishes a connection between form factors with different excitation content. Typically, the crossing relation is a consequence of Lorentz invariance, but due to the finite energy density of the considered states, Lorentz invariance is broken. Nonetheless a crossing relation involving excitations with both particles and holes can established using the finite volume representation of the thermodynamic form factors. Finally, we demonstrate that the thermodynamic form factors satisfy a reparameterization invariance, an invariance which encompasses crossing. Reparameterization invariance exploits the fact that the details of the representation of the thermodynamic state are unimportant. In the course of developing these results, we demonstrate the internal consistency of the thermodynamic form factor bootstrap program in a number of ways. Finally, we provide explicit computations of form factors of conserved charges and densities with crossed excitations and show our results can be used to infer information about thermodynamic form factors in the Lieb-Liniger model.

75 CONDENSED MATTER PHYSICS, SUPERCONDUCTIVITY AND↗
DOE OSTI2025

LLM Benchmarking with LLaMA2: Evaluating Code Development Performance Across Multiple Programming Languages

The rapid evolution of large language models (LLMs) has opened new possibilities for automating various tasks in software development. This paper evaluates the capabilities of the LLaMA 2-70B model in automating these tasks for scientific applications written in commonly used programming languages. Using representative test problems, we assess the model's capacity to generate code, documentation, and unit tests, as well as its ability to translate existing code between commonly used programming languages. Our comprehensive analysis evaluates the compilation, runtime behavior, and correctness of the generated and translated code. Additionally, we assess the quality of automatically generated code, documentation, and unit tests. Here, our results indicate that while LLaMA 2-70B frequently generates syntactically correct and functional code for simpler numerical tasks, it encounters substantial difficulties with more complex, parallelized, or distributed computations, requiring considerable manual corrections. We identify key limitations and suggest areas for future improvements to better leverage AI-driven automation in scientific computing workflows.

97 MATHEMATICS AND COMPUTING↗
NASA NTRS1989

Systems engineering and integration of control centers in support of multiple programs

The NASA Johnson Space Center's new Multiprogram Control Center (MPCC) addresses the control requirements of complex STS payloads as well as unmanned vehicles. An account is given of the relationship of the MPCC to the STS Mission Control Center, with a view to significant difficulties that may be encountered and solutions thus far devised for generic problems. Examples of MPCC workstation applications encompass telemetry decommutation, engineering unit conversion, data-base management, trajectory processing, and flight design.

Miller, David N.↗
NASA NTRS2014

Supporting Multiple Programs and Projects at NASA's Kennedy Space Center

With the conclusion of the shuttle program in 2011, the National Aeronautics and Space Administration (NASA) had found itself at a crossroads for finding transportation of United States astronauts and experiments to space. The agency would eventually hand off the taxiing of American astronauts to the International Space Station (ISS) that orbits in Low Earth Orbit (LEO) about 210 miles above the earth under the requirements of the Commercial Crew Program (CCP). By privatizing the round trip journey from Earth to the ISS, the space agency has been given the additional time to focus funding and resources to projects that operate beyond LEO; however, adding even more stress to the agency, the premature cancellation of the program that would succeed the Shuttle Program - The Constellation Program (CxP) -it would inevitably delay the goal to travel beyond LEO for a number of years. Enter the Space Launch System (SLS) and the Orion Multipurpose Crew Vehicle (MPCV). Currently, the SLS is under development at NASA's Marshall Spaceflight Center in Huntsville, Alabama, while the Orion Capsule, built by government contractor Lockheed Martin Corporation, has been assembled and is currently under testing at the Kennedy Space Center (KSC) in Florida. In its current vision, SLS will take Orion and its crew to an asteroid that had been captured in an earlier mission in lunar orbit. Additionally, this vehicle and its configuration is NASA's transportation to Mars. Engineers at the Kennedy Space Center are currently working to test the ground systems that will facilitate the launch of Orion and the SLS within its Ground Services Development and Operations (GSDO) Program. Firing Room 1 in the Launch Control Center (LCC) has been refurbished and outfitted to support the SLS Program. In addition, the Spaceport Command and Control System (SCCS) is the underlying control system for monitoring and launching manned launch vehicles. As NASA finds itself at a junction, so does all of its associated centers across the US. KSC has found itself at the blunt end of change as the entire center has transitioned from an operations mindset to a development mentality. The author of this paper has had the fortunate privilege and opportunity to be part of a transforming NASA during the fall months of 2014. The following is a high level account of projects that he had the chance to work on including the Spaceport Command and Control System, the Advanced Ground System and Maintenance Program Project, Customer Avionics Development & Analysis (CAIDA) Lab and Swamp Works.

Advanced Ground System Maintenance↗
DOE OSTI2024

TeMPI Shim

This is the manual for the TeMPI Shim library, whose goal is to facilitate scientific apps being loosely coupled through MPI. TeMPI Shim can be used to create and manage Message Passing Interface (MPI, see [MPI]) Communicators for Single Program, Multiple Data (SPMD, see [SPMD]) and Multiple Programs, Multiple Data (MPMD, see [MPMD]) workflows. MPI provides the MPI_APPNUM command number to each of the processes within its context. This number, starting at 0, is the application number being executed. In a case where 3 applications are being run in MPMD mode, there would be MPI_APPNUM values of 0, 1, and 2. TeMPI Shim creates intra- and inter-communicators between each pair of MPI_APPNUM values. In the aforementioned case, application 0 would have intra- and inter-communicators to speak to itself, application 1, and application 2. This is replicated for each of the applications. Additionally, TeMPI Shim creates intra- and inter-communicators for the first MPI rank of each application to directly communicate only with each other. Finally, TeMPI Shim creates its own copy of the default world communicator, i.e., MPI_COMM_WORLD. In the case where there is only a single application, it will have the communicators to only speak with itself. TeMPI Shim is useful in this case since it is considered good practice for MPI applications to copy the default world communicator and reference this copy (see [Duplicate World]_) anyways. Ultimately, it provides value independent of the number of applications present.

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗
NASA NTRS1992

Structural design using equilibrium programming

Multiple nonlinear programming methods are combined in the method of equilibrium programming. Equilibrium programming theory has been appied to problems in operations research, and in the present study it is investigated as a framework to solve structural design problems. Several existing formal methods for structural optimization are shown to actually be equilibrium programming methods. Additionally, the equilibrium programming framework is utilized to develop a new structural design method. Selected computational results are presented to demonstrate the methods.

Scotti, Stephen J.↗
DOE OSTI2024

An MPMD approach coupling electromagnetic continuum mechanics approximations in ALEGRA

In this work, two complementary approximations for describing aspects of continuum electromagnetics in moving media are discussed: electroquasistatic and magnetoquasistatic. Each has been implemented in the finite element shock code ALEGRA for modeling dynamic electromechanical phenomena on typical engineering time scales, with fully integrated circuit coupling. The approximations can be obtained by consistent asymptotic balancing of Maxwell’s equations relative to timescales associated with magnetic diffusion, charge relaxation, and electromagnetic wave propagation. In ALEGRA, the electroquasistatic approximation is used for ferroelectric (FE) modeling, while the magnetoquasistatic approximation is used for magnetohydrodynamic (MHD) modeling. In this paper we introduce for the first time a detailed derivation of a useful quasi-steady “low-R m ” variant of the MHD approximation applicable for cases, such as with detonators, where the thermodynamic pressure arising from Joule heating dominates over magnetic forces. An additional purpose of this paper is to present a coupling mode using Multiple Program-Multiple Data (MPMD) message passing communication that allows the user to run 3D FE problems together with 2D and/or 3D MHD problems with the respective simulation domains coupled through a common circuit equation. The MPMD coupling capability is used here to model the dynamic coupling of a notional ferroelectric generator with an RP-87 exploding bridgewire detonator. The simulated bridgewire heats up and bursts under current generated by simulated depoling of the ferroelectric generator, as a demonstration of the MPMD capability.

42 ENGINEERING↗
DOE OSTI2021

IRIS: A Portable Runtime System Exploiting Multiple Heterogeneous Programming Systems

Across embedded, mobile, enterprise, and HPC systems, computer architectures are becoming more heterogeneous and complex. This complexity is causing a crisis in programming systems and performance portability. Several programming systems are working to address these challenges, but the increasing architectural diversity is forcing software stacks and applications to specialize for each architecture. As we show, all of these approaches critically depend on their runtime system for discovery, execution, scheduling, and data orchestration. To address this challenge, we believe that a more agile and proactive runtime system is essential to increase performance portability and improve user productivity. In this regard, we have designed and implemented IRIS: a portable runtime system exploiting multiple heterogeneous programming systems. IRIS can discover available resources, manage multiple diverse programming systems (e.g., CUDA, Hexagon, HIP, Level Zero, OpenCL, OpenMP) simultaneously in the same execution, respect data dependencies, orchestrate data movement proactively, and provide for user-configurable scheduling. Our evaluation on three architectures, ranging from Qualcomm Snapdragon to a Summit supercomputer node, shows that IRIS improves portability across a wide range of diverse heterogeneous architectures with negligible overhead.

Kim, Jungwon↗
NASA NTRS1994

Discrete sensitivity derivatives of the Navier-Stokes equations with a parallel Krylov solver

This paper solves an 'incremental' form of the sensitivity equations derived by differentiating the discretized thin-layer Navier Stokes equations with respect to certain design variables of interest. The equations are solved with a parallel, preconditioned Generalized Minimal RESidual (GMRES) solver on a distributed-memory architecture. The 'serial' sensitivity analysis code is parallelized by using the Single Program Multiple Data (SPMD) programming model, domain decomposition techniques, and message-passing tools. Sensitivity derivatives are computed for low and high Reynolds number flows over a NACA 1406 airfoil on a 32-processor Intel Hypercube, and found to be identical to those computed on a single-processor Cray Y-MP. It is estimated that the parallel sensitivity analysis code has to be run on 40-50 processors of the Intel Hypercube in order to match the single-processor processing time of a Cray Y-MP.

Ajmani, Kumud↗
NASA NTRS1981

The extension of the thermal-vacuum test optimization program to multiple flights

The thermal vacuum test optimization model developed to provide an approach to the optimization of a test program based on prediction of flight performance with a single flight option in mind is extended to consider reflight as in space shuttle missions. The concept of 'utility', developed under the name of 'availability', is used to follow performance through the various options encountered when the capabilities of reflight and retrievability of space shuttle are available. Also, a 'lost value' model is modified to produce a measure of the probability of a mission's success, achieving a desired utility using a minimal cost test strategy. The resulting matrix of probabilities and their associated costs provides a means for project management to evaluate various test and reflight strategies.

Williams, R. E.↗
NASA NTRS2012

An MBSE Approach to Space Suit Development

The EVA/Space Suit Development Office (ESSD) Systems Engineering and Integration (SE&I) team has utilized MBSE in multiple programs. After developing operational and architectural models, the MBSE framework was expanded to link the requirements space to the system models through functional analysis and interfaces definitions. By documenting all the connections within the technical baseline, ESSD experienced significant efficiency improvements in analysis and identification of change impacts. One of the biggest challenges presented to the MBSE structure was a program transition and restructuring effort, which was completed successfully in 4 months culminating in the approval of a new EVA Technical Baseline. During this time three requirements sets spanning multiple DRMs were streamlined into one NASA-owned Systems Requirement Document (SRD) that successfully identified requirements relevant to the current hardware development effort while remaining extensible to support future hardware developments. A capability-based hierarchy was established to provide a more flexible framework for future space suit development that can support multiple programs with minimal rework of basic EVA/Space Suit requirements. This MBSE approach was most recently applied for generation of an EMU Demonstrator technical baseline being developed for an ISS DTO. The relatively quick turnaround of operational concepts, architecture definition, and requirements for this new suit development has allowed us to test and evolve the MBSE process and framework in an extremely different setting while still offering extensibility and traceability throughout ESSD projects. The ESSD MBSE framework continues to be evolved in order to support integration of all products associated with the SE&I engine.

Cordova, Lauren↗
DOE OSTI2021

Nondestructive Assay Technical Infrastructure Program Mission and Vision

The Nondestructive Assay Program (NDAP) mission and vision is achieved by identifying and accomplishing a set of programmatic goals that correspond with eight broad technical program elements. The NDAP was created as a result of Defense Nuclear Facility Safety Board Recommendation 2007-1, entitled “Safety-Related In Situ Nondestructive Assay of Radioactive Materials,” which emphasized the need to improve in situ measurements of radioactive material at US Department of Energy (DOE) defense nuclear facilities. An NDAP five-year plan will define tasks to accomplish specific goals identified in the NDAP mission and vision. This mission and vision is applicable for eight technical program elements: Hardware/Software Development, Algorithm Development and Nuclear Data, Uncertainty Quantification, Nuclear Materials, Staffing, Personnel, And Training, Data Management, Requirement and Standards, and Information Preservation and Dissemination. An additional program element is technical support, which provides daily execution management support for the NDAP, site scope, and deliverable tracking via site task managers, along with technical advisement and support from the technical support group. The NDAP mission and vision provides attributes with specific goals for each program element, and some goals benefit multiple program elements. The goals and attributes defined herein are implemented via an NDAP five-year execution plan that defines site work scope, budget, and deliverables, all of which are updated annually. The NDAP is designed to benefit nondestructive assay (NDA) needs to support DOE nuclear criticality safety programs, ensuring that NDA technology is sufficiently capable of guaranteeing the safety of those who handle, store, process, or transport fissionable materials in the complex. Especially important for the NDAP is to maximize capabilities to identify, characterize, and manage in situ fissile material deposits in process equipment to ensure nuclear criticality safety at processing facilities.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗
NASA NTRS2006

NavP: Structured and Multithreaded Distributed Parallel Programming

This slide presentation reviews some of the issues around distributed parallel programming. It compares and contrast two methods of programming: Single Program Multiple Data (SPMD) with the Navigational Programming (NAVP). It then reviews the distributed sequential computing (DSC) method and the methodology of NavP. Case studies are presented. It also reviews the work that is being done to enable the NavP system.

parallel programming↗
NASA NTRS2024

Moon to Mars (M2M) Cross Program Utilization Payload Safety Process

It is the goal of Moon to Mars (M2M) to establish a single consolidated set of safety requirements and a safety review process for utilization payloads that will cross program vehicle hatches or operate externally on multiple program vehicles during transport or operation that satisfies Exploration Ground Systems (EGS), Orion, EVA, and Human Surface Mobility Program (EHP), Gateway (GW), and Human Landing System (HLS) programs. This document defines the Cross Program Utilization Payload (xPUP) safety review process for mission effectivity of Artemis III and beyond. This review process will help ensure protection of the overall Moon to Mars integrated system from potential hazards created by cross program payloads that either cross a program vehicle hatch or can interface with more than one M2M lunar exploration program vehicle. The process will identify payload hazards and controls that will protect ground personnel, flight crew, the integrated vehicle, ground equipment, or facilities. This process is also applicable to samples that cross hatches between vehicles including for return to Earth. The xPUP safety review process will be led by one of the M2M programs' integration safety panels, chosen on a per-payload basis. After the lead integration safety panel is determined, the common safety process is established, based on pre-determined criteria, which includes ad-hoc members from other stakeholder programs. Stakeholder programs are those that interface with the utilization payload in any way (e.g., operating on a lunar exploration vehicle or crossing program vehicle hatches). The xPUP will execute this safety review process for flight and ground utilization payload hardware design, its ground support equipment, and landing and recovery in accordance with the applicable safety requirements as specified in M2M-30043: Moon to Mars Cross Program Utilization Payload Safety Requirements. The xPUP safety process will follow the lead integration safety panel’s safety process requirements. Formal agreements will be communicated with the payload developer using the payload integration processes documented in M2M-30037, Artemis Payload Integration Implementation Plan.

payloads↗
NASA NTRS1993

Dynamic data distributions in Vienna Fortran

Vienna Fortran is a machine-independent language extension of Fortran, which is based upon the Single-Program-Multiple-Data (SPMD) paradigm and allows the user to write programs for distributed-memory systems using global addresses. The language features focus mainly on the issue of distributing data across virtual processor structures. Those features of Vienna Fortran that allow the data distributions of arrays to change dynamically, depending on runtime conditions are discussed. The relevant language features are discussed, their implementation is outlined, and how they may be used in applications is described.

Chapman, Barbara↗
NASA NTRSDate not supplied

Aggregate Risk Tool for Human Space Flight

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

Patrick Huckaby↗