SEARCH · Search NASA
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.
This viewgraph presentation reviews some of the complications in developing metrics for systems integration. Specifically it reviews a case study of how two programs within NASA try to develop and measure performance while meeting the encompassing organizational goals.
In the HPC area, both hardware and software move quickly. Often new hardware is developed and deployed, the corresponding software stack, including compilers and other tools, are under active development while leading edge software developers are working to port and tune their applications, all at the same time. While the software ecosystem is in flux, one of the key challenges for users is obtaining insight into the state of implementation of key features in the programming languages and models their applications are using – whether they have been implemented, and whether the implementation conforms to the specification, especially for newly implemented features (less tested by widespread use). OpenMP is one of the most prominent shared memory programming models used for on-node programming in HPC. With the shift towards accelerators (such as GPUs and FPGAs) and heterogeneous programming OpenMP features are getting more complex. It is natural to ask whether generative AI approaches, and large language models (LLMs) in particular, can help in producing validation and verification test suites to allow users better and faster insights into the availability and correctness of OpenMP features of interest. In this work, we explore the use of ChatGPT-4 to generate a suite of tests for OpenMP features. We have chosen a set of directives and clauses, a total of 78 combinations, which first appeared in OpenMP 3.0 (released in May 2008) but are also relevant for accelerators. We prompted ChatGPT to generate tests in the C and Fortran languages, for both host (CPU) and device (accelerator). On the Summit super-computer using the GNU implementation, we found that, of the 78 generated tests 67 C tests and 43 Fortran tests compiled successfully and fewer than those executed to completion. On further analysis we show that not all generated tests are valid. We document the process, results, and provide detailed analysis regarding the quality of tests generated. With the aim of providing input to a production quality validation and verification suite, we manually implement the corrections required to make the tests valid according to the current OpenMP specification. We quantify this effort as small, medium, or large, and record the lines of code changed to correct the invalid tests. With the corrected tests we validate recent implementations from HPE, AMD, and GNU on the Frontier supercomputer. Our experiment and subsequent analysis show that although LLMs are capable of producing HPC specific codes, they are limited by their understanding of the deeper semantics and restrictions of programming models such as OpenMP. Unsurprisingly more commonly used features have better support, while some OpenMP 3.0 directives such as sections and tasking are not universally supported on accelerators. We demonstrate that successful compilation and execution to completion are inadequate metrics for evaluating generated code and that, at this time, commodity LLMs require expert intervention for code verification. This points to gaps in the training data that is currently available for HPC. We demonstrate that with "small" effort 37% of generated invalid C tests and 63% of generated invalid Fortran tests could be corrected. This improves productivity of test generation as we circumvent writing from scratch and the common programming errors associated with it.
Progress was made in the hydroclimatology, habitat modeling and inventory, computer analysis, wildlife management, and data comparison programs that utilize LANDSAT and SEASAT data provided to Mississippi researchers through the remote sensing applications program. Specific topics include water runoff in central Mississippi, habitat models for the endangered gopher tortoise, coyote, and turkey Geographic Information Systems (GIS) development, forest inventory along the Mississipppi River, and the merging of LANDSAT and SEASAT data for enhanced forest type discrimination.
NASA's Hall thruster program has base research and focused development efforts in support of the Advanced Space Transportation Program, Space-Based Program, and various other programs. The objective of the base research is to gain an improved understanding of the physical processes and engineering constraints of Hall thrusters to enable development of advanced Hall thruster designs. Specific technical questions that are current priorities of the base effort are: (1) How does thruster life vary with operating point? (2) How can thruster lifetime and wear rate be most efficiently evaluated? (3) What are the practical limitations for discharge voltage as it pertains to high specific impulse operation (high discharge voltage) and high thrust operation (low discharge voltage)? (4) What are the practical limits for extending Hall thrusters to very high input powers? and (5) What can be done during thruster design to reduce cost and integration concerns? The objective of the focused development effort is to develop a 50 kW-class Hall propulsion system, with a milestone of a 50 kW engineering model thruster/system by the end of program year 2006. Specific program wear 2001 efforts, along with the corporate and academic participation, are described.
It can be difficult to identify the specific variables or equations responsible for convergence issues in large mathematical programming models. The Institute for the Design of Advanced Energy Systems Integrated Platform (IDAES-IP) contains a tool to identify poorly scaled constraints and variables by searching for rows and columns of the Jacobian matrix with small L2-norms. A singular value decomposition is then performed to identify degenerate sets of equations and remaining scaling issues. Here, this work presents a flowsheet developed for post-combustion carbon capture using a monoethanolamine (MEA) solvent system as a case study. This work takes the reader through the entire process of model diagnostics and reformulation, from a basic introduction to the mathematics behind these model diagnostics to the reformulations necessary to make the model numerically robust, including a significantly modified enhancement factor model.
As two of the highest trending green technologies, photovoltaic panels and green roofs are proven to be effective practices for energy generation and energy saving. The achievable impact from the widespread installation of such technologies is, however, not clearly established. This is mainly because the degree of this impact highly depends on the inherently uncertain environmental and climate factors, as well as the unknown adoption rates of these technologies, which in turn depend on different characteristics of decision makers and interactions among them. To that end, this study aims to investigate the diffusion rate of these green technologies under uncertainties caused by climate change, characteristics of adopters, and their interactions. An integrated framework is developed to capture the interplay between financial and attitudinal aspects, as well as the uncertainties due to both the stochastic nature of system parameters and the interactions among agents involving human beings. Specifically, this framework consists of a integer programming model to optimize the green roof and/or photovoltaic panel installation settings for a given building under climate change uncertainty, and an agent-based model to factor in the role of human behavior and interactions. A case study for the city of Knoxville, TN, is presented to evaluate the effects of different policies on the diffusion rate of the green technologies of interest. The results show that the affordability of green technologies and public awareness are the key drivers of the adoption of these technologies, which highlight the important role of the decision makers in impacting the diffusion rate.
—This paper proposes an optimization strategy to assist utility operators to recover power distribution systems after large outages. Specifically, a mixed-integer linear programming (MILP) model is developed for co-optimizing crews, resources, and network operations. The MILP model coordinates damage isolation, network reconfiguration, distributed generator re-dispatch, and crew/resource logistics. In addition, a framework for integrating different types of photovoltaic (PV) systems in the restoration process is developed. We consider two different types of crews, namely, line crews for damage repair and tree crews for obstacle removal. We also model the repair resource logistic constraints. Furthermore, a new algorithm is developed for solving the distribution system repair and restoration problem (DSRRP). The algorithm starts by solving DSRRP using an assignmentbased method, then a neighborhood search method is designed to iteratively improve the solution. The proposed method is validated on modified IEEE 123- and 8500-bus distribution test systems.
Optimal multi-impulse trajectories were investigated as a nominal about which asymptotic expansion was used to obtain approximations of optimal low thrust trajectories. The work consisted of the analysis and description of an optimal 3-impulse trajectory program. A patched-conic trajectory model was specifically designed for compatibility with the subsequent addition of the low thrust expansion approximation.
MACPASCO is interactive, graphical preprocessor program designed to make use of Panel Analysis and Sizing Code, PASCO, (COSMIC program numbers LAR-13004, LAR-13164, and LAR-14799) faster, simpler, and less error-prone. Is Macintosh-based preprocessor program that includes graphical user interface (GUI) program to simplify specification of panel geometry, making modeling and analysis of panel designs more efficient and reducing potential for user input errors. Written in Macintosh Programmers Workbench 3.0, MPW Pascal 3.0, and MacAPP 2.0.
Parallel patterns, views, and spaces are promising abstractions to capture the programmer's intent as well as the contextual information that can be used by an underlying runtime to efficiently map software to parallel hardware. These abstractions can be valuable in cases where an algorithm must accommodate requirements of code and performance portability across hardware architectures and vendor programming models. Kokkos is a parallel programming model for host- and accelerator architectures that relies on these abstractions and targets these requirements. It consists of a pure C++ interface, a specification, and a programming library. The programming library exposes patterns and types and maps them to an underlying abstract machine model. The abstract machine model offers a generic view of parallel hardware. While Kokkos is gaining popularity in large-scale HPC applications at some DOE laboratories, we believe that the implemented concepts are of interest to a broader audience including academia as they may contribute to a generic, vendor, and architecture-independent education of parallel programming. In this work, we give an insight into the design considerations of this programming model and list important abstractions. Further, we document best practices obtained from giving virtual classes on Kokkos and give pointers to resources that the reader may consider valuable for a lecture on generic parallel programming for students with preexisting knowledge on this matter.
On February 1st, 2010 U.S. President Barack Obama submitted to Congress his proposed budget request for Fiscal Year 2011. This budget included significant changes to the National Aeronautics and Space Administration (NASA), including the proposed cancellation of the Constellation Program. This change proved to be controversial and Congressional approval of the program's official cancellation would take many months to complete. During this same period an end-to-end discrete event simulation (DES) model of Constellation operations was being built through the joint efforts of Productivity Apex Inc. (PAl) and Science Applications International Corporation (SAIC) teams under the guidance of NASA. The uncertainty in regards to the Constellation program presented a major challenge to the DES team, as to: continue the development of this program-of-record simulation, while at the same time remain prepared for possible changes to the program. This required the team to rethink how it would develop it's model and make it flexible enough to support possible future vehicles while at the same time be specific enough to support the program-of-record. This challenge was compounded by the fact that this model was being developed through the traditional DES process-orientation which lacked the flexibility of object-oriented approaches. The team met this challenge through significant pre-planning that led to the "modularization" of the model's structure by identifying what was generic, finding natural logic break points, and the standardization of interlogic numbering system. The outcome of this work resulted in a model that not only was ready to be easily modified to support any future rocket programs, but also a model that was extremely structured and organized in a way that facilitated rapid verification. This paper discusses in detail the process the team followed to build this model and the many advantages this method provides builders of traditional process-oriented discrete event simulations.
The authors present an initial and elementary investigation of the formal specification and mechanical verification of programs that interact with environments. They describe a mechanical proof that a simple, real time control program keeps a vehicle on a straightline course in a variable crosswind. To formalize the specification they define a mathematical function which models the interaction of the program and its environment. They then state and proved two theorems about this function: the simulated vehicle never gets farther than three units away from the intended course, and it comes to the course if the wind ever remains steady for at least four sampling units.
The Short-Baseline Neutrino (SBN) program features three Liquid Argon Time Projection Chamber (LAr-TPC) detectors positioned along the Booster Neutrino Beam (BNB) axis: the Short Baseline Neutrino Near Detector, MicroBooNE, and the ICARUS T600. As the largest operational LAr-TPC, ICARUS T600 serves as the far detector, located 600 m from the BNB target. While its primary goal is to record neutrino events, it also detects other ionizing events, including cosmic rays. This work focuses on analyzing and modeling detector-specific reconstruction uncertainties in LAr-TPC. These inefficiencies, identified during the Pattern Recognition phase handled by the PANDORA algorithm, impact subsequent Particle Fits and Offline Analysis. Specifically, inaccuracies in track reconstruction can lead to significant physical consequences, such as erroneous particle energy estimates and poor Particle Identification (PID), reducing the efficiency of neutrino event characterization. A key issue addressed is split tracks, caused by missing hits or incomplete track stitching by PANDORA. The aim of this internship is to characterize, model, and quantify the impact of split tracks on track reconstruction.
The International Space Station (ISS) Bipropellant Plume Contamination Model has been a vital tool for characterizing the thruster plume-induced contamination environment at the ISS but was not intended to be used for very short thruster pulse widths. This paper presents an updated model that ensures full start-up and shut-down phases are modeled for each thruster firing, when the majority of liquid phase contaminant mass is released. The updated ISS Bipropellant Plume Contamination Model prevents potential under-prediction of thruster plume-induced contamination due to visiting vehicle proximity operations and provides a way to take advantage of thruster start-up and shut-down data performance data gathered during thruster test programs, if available. The International Space Station (ISS) Bipropellant Plume Contamination Model developed by Boeing Space Environments is a semi-empirical model anchored in flight experiment data and has been a vital tool for characterizing the thruster plume-induced contamination environment at the ISS.[1] The current model utilizes flight experiment data from the Plume Impingement Contamination (PIC) and Shuttle Plume Impingement Flight Experiment (SPIFEX) studies, which include Orbiter 3870 N Primary Reaction Control System (PRCS) and Russian 130 N thrusters operating in pulse mode with 80-100 ms.[2] As the next generation of crew and cargo visiting vehicles are developed and arrive at ISS, minimum pulse widths of vehicle thrusters used for ISS proximity operations have decreased significantly below 80 ms. An update to the ISS Bipropellant Contamination Model is needed to prevent potential under-prediction of thruster plume-induced contamination for these very short pulse widths. Contamination due to thruster plumes occurs in the liquid phase (i.e., unburned or partially burned propellant in the plume). Liquid phase releases primarily occur during thruster start-up and shut-down phases, with the steady state phase contributing a small amount to the total contaminant mass released. The current ISS Bipropellant Plume Contamination Model includes functional dependencies on thruster parameters (thrust, mass flow rate, specific impulse (Isp)), distance to receiver surface, and angle off plume centerline. For modeling purposes, contaminant mass released scales linearly with pulse width. This is a conservative approach for pulse widths greater than 80 ms but could under-predict contamination for very short pulse widths (i.e., with little or no steady state phase). This paper presents a model update to add a functional dependency on commanded pulse width to ensure the portion of the pulse spent in start-up and shut-down phases is appropriately modeled, when the majority of liquid phase contaminant mass is released. The updated model prevents potential under-prediction of thruster plume-induced contamination due to visiting vehicle proximity operations while providing a way to take advantage of thruster start-up and shut-down data gathered during test programs, if available. Developing the plume model for a specific thruster using the ISS Bipropellant Plume Contamination Model must be done in consideration of all available thruster performance data. Example thruster data will be used to illustrate this point and options for implementing the model update with existing ISS Bipropellant Plume Contamination Model code will be discussed.
The operational and research aspects of a subscale, radio-controlled model flight test program are presented. By using low-cost free-flying models, an approach was developed for obtaining research-quality vehicle performance and aerodynamic information. The advantages and limitations learned by applying this approach to a specific flight test program are described. The research quality of the data acquired shows that model flight testing is practical for obtaining consistent and repeatable flight data.
The operational and research aspects of a subscale, radio-controlled model flight test program are presented. By using low-cost free-flying models, an approach was developed for obtaining research-quality vehicle performance and aerodynamic information. The advantages and limitations learned by applying this approach to a specific flight test program are described. The research quality of the data acquired shows that model flight testing is practical for obtaining consistent repeatable flight data.
Ada and the Ada Programming Support Environment (APSE) specifically address the phases of the system/software life cycle which follow after the user's problem was translated into system and software development specifications. The waterfall model of the life cycle identifies the analysis and requirements definition phases as preceeding program design and coding. Since Ada is a programming language and the APSE is a programming support environment, they are primarily targeted to support program (code) development, tecting, and maintenance. The use of Ada based or Ada related specification languages (SLs) and program design languages (PDLs) can extend the use of Ada back into the software design phases of the life cycle. Recall that the standardization of the APSE as a programming support environment is only now happening after many years of evolutionary experience with diverse sets of programming support tools. Restricting consideration to one, or even a few chosen specification and design tools, could be a real mistake for an organization or a major project such as the Space Station, which will need to deal with an increasingly complex level of system problems. To require that everything be Ada-like, be implemented in Ada, run directly under the APSE, and fit into a rigid waterfall model of the life cycle would turn a promising support environment into a straight jacket for progress.
During my internship at NASA, I was a model developer for Ground Support Equipment (GSE). The purpose of a model developer is to develop and unit test model component libraries (fluid, electrical, gas, etc.). The models are designed to simulate software for GSE (Ground Special Power, Crew Access Arm, Cryo, Fire and Leak Detection System, Environmental Control System (ECS), etc. ~.) before they are implemented into hardware. These models support verifying local control and remote software for End-Item Software Under Test (SUT). The model simulates the physical behavior (function, state, limits and 110) of each end-item and it's dependencies as defined in the Subsystem Interface Table, Software Requirements & Design Specification (SRDS), Ground Integrated Schematic (GIS), and System Mechanical Schematic.(SMS). The software of each specific model component is simulated through MATLAB's Simulink program. The intensiv~ model development life cycle is a.s follows: Identify source documents; identify model scope; update schedule; preliminary design review; develop model requirements; update model.. scope; update schedule; detailed design review; create/modify library component; implement library components reference; implement subsystem components; develop a test script; run the test script; develop users guide; send model out for peer review; the model is sent out for verific~tionlvalidation; if there is empirical data, a validation data package is generated; if there is not empirical data, a verification package is generated; the test results are then reviewed; and finally, the user. requests accreditation, and a statement of accreditation is prepared. Once each component model is reviewed and approved, they are intertwined together into one integrated model. This integrated model is then tested itself, through a test script and autotest, so that it can be concluded that all models work conjointly, for a single purpose. The component I was assigned, specifically, was a fluid component, a discrete pressure switch. The switch takes a fluid pressure input, and if the pressure is greater than a designated cutoff pressure, the switch would stop fluid flow.