Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “tracking code”

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 199 records · Page 11
All sourcesNASA NTRSDOE OSTI
NASA NTRS2014

One Dimensional Analysis Model of a Condensing Spray Chamber Including Rocket Exhaust Using SINDA/FLUINT and CEA

Modeling droplet condensation via CFD codes can be very tedious, time consuming, and inaccurate. CFD codes may be tedious and time consuming in terms of using Lagrangian particle tracking approaches or particle sizing bins. Also since many codes ignore conduction through the droplet and or the degradating effect of heat and mass transfer if noncondensible species are present, the solutions may be inaccurate. The modeling of a condensing spray chamber where the significant size of the water droplets and the time and distance these droplets take to fall, can make the effect of droplet conduction a physical factor that needs to be considered in the model. Furthermore the presence of even a relatively small amount of noncondensible has been shown to reduce the amount of condensation [Ref 1]. It is desirable then to create a modeling tool that addresses these issues. The path taken to create such a tool is illustrated. The application of this tool and subsequent results are based on the spray chamber in the Spacecraft Propulsion Research Facility (B2) located at NASA's Plum Brook Station that tested an RL-10 engine. The platform upon which the condensation physics is modeled is SINDAFLUINT. The use of SINDAFLUINT enables the ability to model various aspects of the entire testing facility, including the rocket exhaust duct flow and heat transfer to the exhaust duct wall. The ejector pumping system of the spray chamber is also easily implemented via SINDAFLUINT. The goal is to create a transient one dimensional flow and heat transfer model beginning at the rocket, continuing through the condensing spray chamber, and finally ending with the ejector pumping system. However the model of the condensing spray chamber may be run independently of the rocket and ejector systems detail, with only appropriate mass flow boundary conditions placed at the entrance and exit of the condensing spray chamber model. The model of the condensing spray chamber takes into account droplet conduction as well as the degrading effect of mass and heat transfer due to the presence of noncondensibles. The one dimension model of the condensing spray chamber makes no presupposition on the pressure profile within the chamber, allowing the implemented droplet physics of heat and mass transfer coupled to the SINDAFLUINT solver to determine a transient pressure profile of the condensing spray chamber. Model results compare well to the RL-10 engine pressure test data.

Condensing Spray Model↗
NASA NTRS2014

One Dimensional Analysis Model of a Condensing Spray Chamber Including Rocket Exhaust Using SINDA/FLUINT and CEA

Modeling droplet condensation via CFD codes can be very tedious, time consuming, and inaccurate. CFD codes may be tedious and time consuming in terms of using Lagrangian particle tracking approaches or particle sizing bins. Also since many codes ignore conduction through the droplet and or the degradating effect of heat and mass transfer if noncondensible species are present, the solutions may be inaccurate. The modeling of a condensing spray chamber where the significant size of the water droplets and the time and distance these droplets take to fall, can make the effect of droplet conduction a physical factor that needs to be considered in the model. Furthermore the presence of even a relatively small amount of noncondensible has been shown to reduce the amount of condensation. It is desirable then to create a modeling tool that addresses these issues. The path taken to create such a tool is illustrated. The application of this tool and subsequent results are based on the spray chamber in the Spacecraft Propulsion Research Facility (B2) located at NASA's Plum Brook Station that tested an RL-10 engine. The platform upon which the condensation physics is modeled is SINDAFLUINT. The use of SINDAFLUINT enables the ability to model various aspects of the entire testing facility, including the rocket exhaust duct flow and heat transfer to the exhaust duct wall. The ejector pumping system of the spray chamber is also easily implemented via SINDAFLUINT. The goal is to create a transient one dimensional flow and heat transfer model beginning at the rocket, continuing through the condensing spray chamber, and finally ending with the ejector pumping system. However the model of the condensing spray chamber may be run independently of the rocket and ejector systems detail, with only appropriate mass flow boundary conditions placed at the entrance and exit of the condensing spray chamber model. The model of the condensing spray chamber takes into account droplet conduction as well as the degrading effect of mass and heat transfer due to the presence of noncondensibles. The one dimension model of the condensing spray chamber makes no presupposition on the pressure profile within the chamber, allowing the implemented droplet physics of heat and mass transfer coupled to the SINDAFLUINT solver to determine a transient pressure profile of the condensing spray chamber. Model results compare well to the RL-10 engine pressure test data.

Chemical Equilibrium↗
DOE OSTI2019

Prototype Distributed Ledger Technology of UF 6 Cylinder Tracking in Ethereum

We have created a demonstration permissioned Distributed Ledger Technology (DLT) datastore for the UF 6 cylinder tracking safeguards use-case utilizing the Ethereum DLT framework and using Solidity for smart contract code. Our demonstration creates a simulated dataset representing tracking of 75,000 UF 6 cylinders across 11 example nuclear facilities worldwide. Our DLT system allows for easy input and reading of shipping and receiving data, including a Graphical User Interface (GUI). Sandia’s Emulytics capability was leveraged to help create the DLT node network and assess performance. We find that our DLT prototype can easily handle to ~150,000 UF 6 cylinder shipments per year worldwide, without any excessive computational or storage burden on the IAEA or Member States. Next steps could include a demonstration to the IAEA and potentially demonstrating integration with TradeLens, a DLT in use by a consortium of international shipping companies representing over half of world shipping trade.

98 NUCLEAR DISARMAMENT, SAFEGUARDS, AND PHYSICAL P↗
NASA NTRS1967

The organization of skilled response.

Skilled response organization, discussing stimulus coherence, tracking task, spatial and temporal coherence, secondary task, sequence length and task coding

STIMULUS↗
DOE OSTI2023

The History of MCNP and about 20 Related Programs

The history of the MCNP code is a long and complicated one that touches a huge number of other software packages over the decades. This document will attempt to place the direct lineage of the MCNP code into a single document and track the people who worked on and around the software. This report is necessarily incomplete. The author only has access to the LANL archives, which have gaps in key areas. Speculation will be used to fill gaps where necessary. It is hoped that future revisions will have more detail than this report, especially as others come forward with their knowledge. The history will be broken into a few segments. Sec. 1 will go through the low-energy history from MCS to MCNP version 4. In Sec. 2, the history of high-energy physics from Oak Ridge’s NTC to MCNP version 6 will be discussed. Sec. 3 will go through some important notes to complete this history. Finally, Sec. 4 contains a chart of the lineage of the code.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2023

Coupled neutronics and species transport simulation of the Molten Salt Reactor Experiment

This paper presents the development of coupling between the molten salt reactor species transport code Mole and the reactor physics code Griffin. Here, in this study, tracking of delayed neutron precursors was investigated in the Molten-Salt Reactor Experiment (MSRE), accounting for changes in fuel flow velocity as a function of position in the primary loop. The neutron transport calculations in Griffin were performed using 11 energy groups, and the species advection calculations in Mole used 6 delayed neutron precursor groups to predict spatial distribution of the neutron flux and neutron precursors in the MSRE. Mole–Griffin was used to calculate $k$ eff and $β$ eff in the reactor as a function of different volumetric flow rates.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗
DOE OSTI2023

Spectroscopic quadrupole moments in 124 $\mathrm{Xe}$

The Xe isotopic chain with four valence protons above the Z=50 shell closure is an ideal laboratory for the study of the evolution of nuclear deformation. At the N=82 shell closure, 136 Xe presents all characteristics of a doubly closed shell nucleus with a spherical shape. In the very neutron-deficient isotopes close to N=50, the α-decay chain of Xe was investigated to probe the radioactive decay properties near the drip-line and the magicity of 100 Sn. Additionally, the Xe isotopes present higher order symmetries in the nuclear deformation such as the octupole degree of freedom near N=60 and N=90 or O(6) symmetry in stable isotopes. The relevance of the O(6) symmetry has been investigated by measuring the spectroscopic quadrupole moment of the first excited states in 124 Xe. In the O(6) symmetry limit, the spectroscopic quadrupole moment of collective states is expected to be null. A stable 124 Xe beam with energies of 4.03A MeV and 4.11 A MeV was used to bombard a nat W target at the GANIL facility. Excited states were populated via the safe Coulomb excitation reaction. The collision of the heavy ions with a large Z at low energy make this reaction sensitive to the diagonal E2 matrix element of the excited states. The recoils were detected in the VAMOS++ magnetic spectrometer and the γ rays in the AGATA tracking array. The least squares fitting code gosia was used for the analysis to extract both E2 and M1 transitional and E2 diagonal matrix elements. The rotational ground state band was populated up to the 8$^{+}_{1}$ state as well as the 2$^{+}_{2}$ and 4$^{+}_{2}$ states. Using high precision spectroscopic data to constrain the gosia fit, the spectroscopic quadrupole moments of the 2$^{+}_{1}$, 4$^{+}_{1}$, and 6$^{+}_{1}$ states were determined for the first time. The spectroscopic quadrupole moments were found to be negative, large, and constant in the ground state band underlining the prolate axially deformed ground state band of 124 Xe. Here, the present experimental data confirm that the O(6) symmetry is substantially broken in 124 Xe .

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗
DOE OSTI2020

XPlacer/Tracer

XPlacer/Tracer is a dynamic analysis tool that finds bad memory access patterns in heterogeneous codes. XPlacer/Tracer consists of two components. (1) A configurable ROSE plugin for source code instrumentation of heterogeneous code written in the C/C++ and CUDA programming languages. (2) A sample configuration that instruments memory accesses to dynamic memory in CPU and GPU codes, and a runtime library that tracks these memory accesses at runtime. The collected information is reported in form of a textual summary or as memory map that can be converted to images.

Pirkelbauer, PeterM.↗
NASA NTRS1980

The Build System - Integration and management of large software avionic systems

The Build System comprises the software tools and procedures creating the flight memory load for the Space Shuttle Backup Flight System. The system has six functions: (1) configuration management, which insures that the memory load contains the proper modules, all clearly marked; (2) source translation, which translates the source code into a relocatable machine code; (3) module integration, which combines and assigns memory locations to all the object modules produced in source translation; (4) static code analysis, which verifies the integration process; (5) deliverables generation, which yields release documentation and deliverable items; and (6) release maintenance, which controls all system patches subsequent to release. Further developments will include more automation in the producing of patches from source-code updates and system requirements for tracking.

Mayer, J. T. B.↗
NASA NTRS1990

Numerical simulation of particle-wave interaction in boundary layers

The effects of wall injection and particle motion on the spatial stability of two-dimensional plane channel flow are investigated. For this purpose, an accurate Navier-Stokes solver to simulate the space-time evolution of disturbances in three-dimensional flows has been developed. The code is operational on the NASA Langley CRAY2 and can be ported to any other supercomputer. The code has been tested extensively in tracking the spatial evolution of two-dimensional disturbances in plane channel flow and provided excellent agreement with the linear theory including at the inflow/outflow boundaries. Preliminary calculations have been performed to investigate the effects of stationary and moving sources of vortical disturbances simulating a particle traveling in the flow field. Results suggest that even at very low amplitudes, vortical disturbances act as amplifiers on the Tollmien-Schlichting waves promoting rapid instability. It is also found that slow moving particles are more dangerous than both stationary and fast moving particles for the same disturbance levels.

Biringen, S.↗
NASA NTRS1992

Overview of the relevant CFD work at Thiokol Corporation

An in-house developed proprietary advanced computational fluid dynamics code called SHARP (Trademark) is a primary tool for many flow simulations and design analyses. The SHARP code is a time dependent, two dimensional (2-D) axisymmetric numerical solution technique for the compressible Navier-Stokes equations. The solution technique in SHARP uses a vectorizable implicit, second order accurate in time and space, finite volume scheme based on an upwind flux-difference splitting of a Roe-type approximated Riemann solver, Van Leer's flux vector splitting, and a fourth order artificial dissipation scheme with a preconditioning to accelerate the flow solution. Turbulence is simulated by an algebraic model, and ultimately the kappa-epsilon model. Some other capabilities of the code are 2-D two-phase Lagrangian particle tracking and cell blockages. Extensive development and testing has been conducted on the 3-D version of the code with flow, combustion, and turbulence interactions. The emphasis here is on the specific applications of SHARP in Solid Rocket Motor design. Information is given in viewgraph form.

Chwalowski, Pawel↗
NASA NTRS1996

STS-79 Flight Day 3

On this third day of the STS-79 mission, the flight crew, Cmdr. William F. Readdy, Pilot Terrence W. Wilcutt, Mission Specialists, Thomas D. Akers, John E. Blaha, Jay Apt, and Carl E. Walz, start another busy day on orbit activating experiments in the Spacehab module. Readdy and Wilcutt are seen conducting two rendezvous burns while other crew members are seen working in the Spacehab module. The Active Rack Isolation System, or ARIS, is tended to by Walz, who performs a minor maintenance procedure on one of ARIS' vibration-damping pushrods while Akers works with an inventory management system using a bar code reader to more effectively keep track of items that will be transferred back and forth between the Shuttle and the Mir. Apt continues work with a furnace which heats to nearly 1,600 degrees centigrade to melt metal samples for study after the flight. Apt also provides a television tour of the Spacehab, which is twice its normal size for this flight to allow extra room for science experiments and logistical items slated for transfer to Mir.

Source record↗
DOE OSTI2025

Benchmark Tracking System for Performance Monitoring

Benchmarking is essential for high-performance software development, particularly for monitoring performance across code iterations. This project focused on enhancing the benchmarking process for Lamellar, an asynchronous runtime for High-Performance Computing (HPC) systems developed at Pacific Northwest National Laboratory. Prior to this work, benchmark results were difficult to track and compare across code versions, presenting significant challenges in identifying performance regressions and long-term trends. The primary objective was to establish a systematic, reproducible approach for measuring performance and detecting regressions following code commits. Our methodology involved three key components: standardizing benchmark outputs, implementing data versioning, and developing analysis tools. We standardized the benchmark output format to JSON Line records containing specific fields (execution time, hardware specifications, and environmental variables). To address data management challenges, we evaluated several options and eventually chose a git repository dedicated to benchmark data. We developed a suite of Python tools that processed benchmark results, enriched them with metadata, and facilitated search in the repository. The resulting system enables more efficient filtering and comparison of performance metrics across commit histories, hardware configurations, and benchmark variants through a unified query interface. Our implementation reduces computational overhead by first checking for existing results through configuration matching before initiating new benchmark runs, thereby conserving resources. The system has been validated by Lamellar developers. It organizes results by benchmark type and build configurations for efficient retrieval. Future developments include a planned Large Language Model interface for predicting benchmark performance, incorporating the criterion package for statistical analysis, which will enable automated detection of statistically significant performance changes, and integration with continuous integration pipelines. Despite these enhancements being reserved for future work, this project has successfully provided the Lamellar development team with a framework for maintaining consistent performance standards and identifying optimization opportunities across workloads and hardware environments.

97 MATHEMATICS AND COMPUTING↗
NASA NTRS1991

Cellular track model of biological damage to mammalian cell cultures from galactic cosmic rays

The assessment of biological damage from the galactic cosmic rays (GCR) is a current interest for exploratory class space missions where the highly ionizing, high-energy, high-charge ions (HZE) particles are the major concern. The relative biological effectiveness (RBE) values determined by ground-based experiments with HZE particles are well described by a parametric track theory of cell inactivation. Using the track model and a deterministic GCR transport code, the biological damage to mammalian cell cultures is considered for 1 year in free space at solar minimum for typical spacecraft shielding. Included are the effects of projectile and target fragmentation. The RBE values for the GCR spectrum which are fluence-dependent in the track model are found to be more severe than the quality factors identified by the International Commission on Radiological Protection publication 26 and seem to obey a simple scaling law with the duration period in free space.

Cucinotta, Francis A.↗
DOE OSTI2021

Path-synchronous performance monitoring of interconnection networks based on source code attribution

Examples disclosed herein relate to path-synchronous performance monitoring of an interconnection network based on source code attribution. A processing node in the interconnection network has a profiler module to select a network transaction to be monitored, determine a source code attribution associated with the network transaction to be monitored, and issue a network command to execute the network transaction to be monitored. A logger module creates, in a buffer, a node temporal log associated with the network transaction and the network command. A drainer module periodically captures the node temporal log. The processing node has a network interface controller to receive the network command and mark a packet generated for the network command to be temporally tracked and attributed back to the source code attribution at each hop of the interconnection network traversed by the marked packet.

Chabbi, Milind M.↗