Search NASA⌕ Search

SEARCH · Search NASA

Results for “start up files”

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

Athena-I CUBIT Journal Files

The Monte Carlo N-Particle (MCNP)1 transport code version 6 (also known as MCNP6) has the capability for tracking particles on unstructured mesh (UM) geometry models embedded into con structive solid geometry (CSG) cells. This feature has been developed for performing calculations of complex geometry models because manually creating CSG models is a time-consuming and error prone process as the complexities of geometries increase. The UM capability was originally designed to work with UM models created with the Abaqus software and ASCII input files that it generates. The MCNP code version 6.0 and later can process UM models formatted as Abaqus input files. Starting with version 6.3, MCNP can also process HDF5 mesh input files. External codes must be used to generate Abaqus input files for MCNP UM calculations. CUBIT, the Sandia National Laboratory automated mesh generation toolkit, can generate a UM model formatted as an Abaqus input file. However, the Abaqus input files exported from CUBIT cannot be used for MCNP simulations because it lacks the proper syntax. A Python script was developed to convert an Abaqus file created by CUBIT to an Abaqus file format that MCNP can process. Creating UM models for complex geometries is not an easy task. The process of creating UM models in CUBIT for MCNP simulations is detailed in. CUBIT provides several user interface options including a graphical user interface (GUI) and a command line interface. A GUI provides an easy way to use CUBIT without learning the CUBIT command syntax. When using CUBIT with either interface option, command lines are written into an ASCII file known as a journal file; this journal file can be edited and archived so that it can be played back in CUBIT to automatically generate a UM model. This report describes the CUBIT journal files of the UM models developed for Athena-I. The Athena platform, an energy-tuning assembly, was developed to spectrally shape the National Ignition Facility (NIF) deuterium-tritium fusion neutron source to a thermonuclear (fusion) plus prompt fission neutron spectrum with capability to act as a short-pulse neutron source. MCNP6 was used for the Athena experiment design analysis.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗

Generating MCNP Input Files for Unstructured Mesh Geometries

The Los Alamos National Laboratory’s (LANL) Monte Carlo N-Particle (MCNP)1 transport code version 6.3 (also known as MCNP6.3) has the capability for tracking particles on unstructured mesh (UM) geometry models embedded into constructive solid geometry (CSG) cells. This feature has been developed for performing calculations of complex geometry models because manually creating CSG models is time-consuming and error-prone as the complexities of geometries increase. A UM geometry model is a collection of finite elements representing a solid geometry. The first step of the MCNP UM calculation is using other software packages to create a finite element mesh representation of a solid 3D geometry because the MCNP code cannot be used to generate a UM model. Computer-aided design (CAD) software is typically used to create a solid geometry model, which is later imported into mesh generation software to create a UM model. Some mesh generation software packages may also be used to create solid geometries and thus CAD files are not needed. The MCNP UM feature was originally designed for models generated by the Abaqus/CAE software suite. The MCNP code version 6.0 and later can process UM models formatted as Abaqus input files. Starting with a 6.3 version, the MCNP code can process HDF5 mesh input files. We only focus on the UM models formatted as Abaqus input files in this report since currently no external software can be used to generate HDF5 mesh input files for MCNP UM calculations. The MCNP code version 6.3 can be used to convert the Abaqus mesh input files into the HDF5 mesh input files, but this option is typically used by the MCNP code development team to test the HDF5 mesh input file feature. Several software packages (such as Abaqus, Attila4MC, or Cubit) can be used to create the Abaqus input files for MCNP UM calculations. An MCNP UM calculation using an Abaqus model requires two input file types: MCNP and Abaqus input files. The Abaqus input files needed for MCNP UM calcu lations must have the correct Abaqus syntax and meet the additional requirements by the MCNP code. The MCNP code can process only Abaqus input files that make use of part and assembly definitions, where elements in each part must be grouped into one or more element sets (i.e., elset) using *Elset keyword lines with specified naming formats. The MCNP and Abaqus input files required for MCNP UM simulations must be related; pseudo-cells in an MCNP input file must be constructed from mesh model data from an Abaqus input file. For large complex UM models, it is tedious to manually create MCNP UM input files. The um pre op (unstructured mesh pre operations) program with the -m option can be used to create a skeleton MCNP input file from an Abaqus input file [6]. Since the um pre op program was written in Fortran and was not written for optimized performance, this program is a deprecated feature in the MCNP code version 6.3 and may be removed in the next release of the code. To improve calculation flow of multiphysics calculations, a Python3 code called write mcnp um input has been developed to generate an MCNP input file instead of using the um_pre_op -m option. This Python code was initially released to the public in 2020. We have updated this Python code for MCNP6.3 and it was used to generate the MCNP input files used to verify the MCNP6.3 code. The write_mcnp_um_input code is included with the MCNP6.3 code package which will be released to the public through the Radiation Safety Information Computational Center (RSICC) at Oak Ridge National Laboratory. This report is a revision of LA-UR-20-27139 report.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗

Massive compression for high data rate macromolecular crystallography (HDRMX): impact on diffraction data and subsequent structural analysis

New higher-count-rate, integrating, large-area X-ray detectors with framing rates as high as 17400 images per second are beginning to be available. These will soon be used for specialized macromolecular crystallography experiments but will require optimal lossy compression algorithms to enable systems to keep up with data throughput. Some information may be lost. Can we minimize this loss with acceptable impact on structural information? To explore this question, we have considered several approaches: summing short sequences of images, binning to create the effect of larger pixels, use of JPEG-2000 lossy wavelet-based compression, and use of Hcompress, which is a Haar-wavelet-based lossy compression borrowed from astronomy. We also explore the effect of the combination of summing, binning, and Hcompress or JPEG-2000. In each of these last two methods one can specify approximately how much one wants the result to be compressed from the starting file size. These provide particularly effective lossy compressions that retain essential information for structure solution from Bragg reflections.

47 OTHER INSTRUMENTATION↗

Model run output for WM-ABM 2024 HESS Publication

Model output for computational experiments introducing WM-ABM. See associated HESS publication here: https://egusphere.copernicus.org/preprints/2023/egusphere-2023-1604/ all_nldas_cdl_data_v3.txt - Cropland Data Layer data aggregated to 1/8 degree resolution for input into the PMP calibration process. Variables include NLDAS ID, crop type, year, the count of pixels in the grid cell of the crop type, CDL crop ID, and GCAM crop ID. 20230115 ABM runs - WM-ABM model outputs for various scenarios described in HESS publication. If multiple versions exist (e.g., v2, v3, etc.) latest version indicates dataset generated for manuscript. The "baseline" run is the primary run, where as the "memXX" runs indicate sensitivity runs testing different parameters of agent memory. Output files starting with "abm_results_" include groundwater irrigated acres and surface water irrigated acres for each farm/agent combination. Other CSV outputs provide summary statistics of various agent and water shortage outcomes, used for generation of figures in the HESS manuscript.

ABM↗

Rapid Model Import Tool (RMIT)

Our project is about developing a tool to implement conversion of 3D Computer Aided Design (CAD) models produced with software such as Delmia, 3DS Max, or Maya, into a size and format compatible with the Unity 3D environment. RMIT will be used to aid KSC engineering personnel in the design, development, testing, operations, and training on spacecraft, launch vehicles, facilities, and ground support equipment. For our project, we are using Blender, a free/open-source 3D graphics software, with the goal of developing, testing, and deploying a 3D CAD model converter tool. I worked on using Blender to import 3D CAD models exported from CATIA software into Collada file format. The Collada file format has file extension DAE. Importing the Collada DAE file as is into Blender, generates dots and dashes. In 3DS Max, there is an existing OpenCollada plugin and with that plugin, 3DS Max can import the DAE file successfully. But, Blender does not seem to have an OpenCollada plugin, so I worked on writing a new OpenCollada plugin for Blender. Since 3DS Max was able to display the image, I looked into comparing differences between the original DAE file and the DAE file exported from 3DS Max using the OpenCollada plugin. As Collada documents describing digital assets are XML files with file extension DAE, Collada files contains XML tags, making them easily modifiable. After some research, it appears that Blender does not like primitive 2D tags like tristrips and trifans. Changing those tags to polygons slightly improved the image, but the pieces were exploded. I found after further research comparing differences between the original file and the file exported from 3DS Max that the values inside the translate tags in the original file are scaled down by a factor of 25.4 in the exported file from 3DS Max, representing the millimeters to inches conversion (1 inch = 25.4 millimeters). After scaling down values inside all of the translate tags by 25.4, the exploded pieces stuck back in, but the image needed further improvement. I have been able to create a new plugin in Blender that takes the original DAE file, replaces the primitive 2D tags tristrips and trifans with polygons, scales down the values inside the translate tags by a factor of 25.4, and saves the changes into a temporary DAE file. After the temporary DAE file is imported into Blender, the temp file is then deleted, keeping the original DAE file intact. Starting with a DAE file that is exported using the NASA Enterprise Visualization Application (NEVA), a Collada exporter, from CATIA gives better results. NEVA is a Design Visualization product that is used for exporting 3D models from CATIA. With NEVA, the up axis is defined in the top-level node if navigation gravity is enabled. With that file, just replacing the primitive tags tristrips and trifans with polygons in yields a much improved image in Blender. As we identify more differences between the original DAE file and the DAE file exported from 3DS Max, this plugin can be improved further. Our goal is to have a model that is formatted and sized for import into Unity, and we are trying out different 3D programs to see which will work best.

Ayyangar, Arjun↗

Evaluation of Best Practices in Mitigating Startup Costs on Leadership-Class Supercomputers

Supercomputers at Department of Energy (DOE) National Laboratories face a widening range of workloads, from traditional modeling and simulation to Artificial Intelligence model training or complex multi-stage workflows, and beyond. At DOE Leadership Computing Facilities like the Oak Ridge Leadership Computing Facility (OLCF), these workloads demand concurrent access to large portions of the supercomputer’s resources. Launching a job across massive supercomputers is challenging from the start; the file system struggles with a large backlog of metadata requests as tens of thousands of processes read thousands of the same files, and the compute job cannot start until this is completed. There are multiple existing approaches to calm this metadata storm, ranging from vendor-developed tools like sbcast to National Laboratory-developed tools like Spindle and Copper. In this paper, we benchmark and discuss three common approaches to improving compute job launch latencies on Frontier: Slurm’s sbcast tool, Spindle, and Copper. We evaluate these tools by measuring the launch latencies of four workloads: OSU Microbenchmark’s osu_init, Pynamic, Python import mpi4py, and Python import torch. We provide discussion of the results, highlighting data that meet expectations and that do not meet expectations.

Hagerty, Nick [ORNL] (ORCID:0000000330014414)↗

Verification and Validation of the Stakeholder Tool for Assessing Radioactive Transportation (START) – 22323

The U.S. Department of Energy (DOE) Office of Integrated Waste Management is planning for the eventual transportation, storage, and disposal of spent nuclear fuel (SNF) and high-level radioactive waste (HLW) from nuclear power plant and DOE sites. The Stakeholder Tool for Assessing Radioactive Transportation (START) is a web-based, geospatial decision-support tool developed for evaluating routing options and other aspects of transporting SNF and HLW, covering rail, truck, barge, and intermodal infrastructure and operations in the continental United States. The verification and validation (V&V) process is intended to independently assess START to provide confidence in the ability of START to accurately provide intended results. The V&V process checks the START tool using a variety of methods, ranging from independent hand calculations to comparison of START performance and results to those of other codes. The V&V activity was conducted independently from the START development team with opportunities to provide feedback and collaborate throughout the process. The V&V analyzed attributes of transportation routes produced by START, including route distance and both population and population density captured within buffer zones around routes. Population in the buffer zone, population density in the buffer zone, and route distance were all identified as crucial outputs of the START code and were subject to V&V tasks. Some of the improvements identified through the V&V process were standardizing the underlying population data in START, changing the projection of the population raster data, and changes to the methodology used for population density to improve its applicability for expected users. This collaboration also led to suggested improvements to some of the underlying shape file segments within START. A formal series of test routes went through the V&V process from START version 3.2.1 following the implementation of the recommended improvements to START. The V&V of the buffer zone population and distance reported in START were achieved by utilizing a custom workflow developed in QGIS. This platform was chosen because it is fully independent of START. The buffer zone population and route distances in START showed excellent agreement to independent V&V test results. Over 200 route test cases were run; in all cases, the percent difference in the population within the buffer zone was less than +/- 5%, and the majority of cases were below +/- 1%. These cases were also duplicated in ArcMap, which is Environmental Systems Research Institute’s (ESRI) GIS desktop application. The ArcMap results also show good agreement; however, they cannot be considered independent of START because START also uses ESRI software. The V&V tasks are currently addressing population density and estimated radiation dose in START as well as implementing further automation of the V&V process to allow larger suites of test routes to be run more easily and quickly by less experienced GIS users. These improvements to the V&V process will make it a valuable tool for the development team and the stakeholders so that each new iteration of START can easily be checked for quality and consistency. This paper and presentation will describe the V&V process, findings and implications, and ongoing V&V activities.

START, DOE, Transporation, dose, GIS↗

CROCUS Weather Data at Chicago State University Prairie Site

Vaisala WXT sensor is an all-in-one weather instrument that provides 6 of the most important weather parameters: barometric pressure, temperature, relative humidity, rainfall, wind speed and direction. Temperature, pressure, relative humidity, and rainfall are sampled at 1 second frequency, while wind speed/direction is measured at ten per second (10Hz) frequency. These measurements are useful for looking at characterizing local weather, identifying unique weather events, and studying local turbulence, especially given the high temporal resolution of the wind measurements. These measurements are collected at Chicago State University (CSU) at a prarie site on campus in Chicago, Illinois. Data is available in the netCDF data format, we encourage data users review documentation through Project Pythia to understand how to work with netCDF data https://foundations.projectpythia.org/core/data-formats/netcdf-cf.html. The data is aggregated into daily frequency to make it easier to process multiple days, and compress the higher-resolution fields. Each file contains one day's worth of data (24 hours, starting at 0000 UTC). File naming convention includes the project (CROCUS), location (CSU), data level (raw, a1), date (year, month, day), and hour (0000).

54 ENVIRONMENTAL SCIENCES↗

CROCUS Weather Data at Argonne National Laboratory Prairie Site

Vaisala WXT sensor is an all-in-one weather instrument that provides 6 of the most important weather parameters: barometric pressure, temperature, relative humidity, rainfall, wind speed and direction. Temperature, pressure, relative humidity, and rainfall are sampled at 1 second frequency, while wind speed/direction is measured at ten per second (10Hz) frequency. These measurements are useful for looking at characterizing local weather, identifying unique weather events, and studying local turbulence, especially given the high temporal resolution of the wind measurements. These measurements are collected at the Argonne Testbed for Multiscale Observational Science (ATMOS), a prairie field site at Argonne National Laboratory in Lemont, Illinois. Data is available in the netCDF data format, we encourage data users review documentation through Project Pythia to understand how to work with netCDF data https://foundations.projectpythia.org/core/data-formats/netcdf-cf.html. The data is aggregated into daily frequency to make it easier to process multiple days, and compress the higher-resolution fields. Each file contains one day's worth of data (24 hours, starting at 0000 UTC). File naming convention includes the project (CROCUS), location (atmos), data level (raw, a1), date (year, month, day), and hour (0000).

54 ENVIRONMENTAL SCIENCES↗

CROCUS Air Quality Data at University of Illinois - Chicago Tower

The AQT (Vaisala AQT530) instrument provides observations on meteorological conditions, including particulate matter (PM2.5, PM10), gas species concentrations (NO, NO2, O3, CO), and environment temperature and moisture. These measurements are critical for understanding air quality. These measurements are useful for understanding changes in aerosol properties, air quality research, and comparing to model experiments especially in urban environments. These measurements are collected at the University of Illinois in Chicago, Illinois, on the meteorological tower near the greenhouse on campus. Data is available in the netCDF data format, we encourage data users review documentation through Project Pythia to understand how to work with netCDF data https://foundations.projectpythia.org/core/data-formats/netcdf-cf.html. Each file contains one day's worth of data (24 hours, starting at 0000 UTC). File naming convention includes the project (CROCUS), location (UIC), data level (raw, a1), date (year, month, day), and hour (0000).

54 ENVIRONMENTAL SCIENCES↗

Precision Asteroid Astrometry

Among the methods used to guide spacecraft to their destinations, Optical Navigation (OpNav) remains an effective option. OpNav makes use of star fields and small body ephemerides to precisely locate spacecraft. To facilitate accurate OpNav, the small body ephemerides must be constantly updated; asteroid orbits accumulate errors each year of a few milliarcseconds. Through extended exposures, taken with strategic offsets, a least-squares solution can be found that determines updated ephemeris data. This updated data can also be used by occultation astronomers to gain further information about the small bodies, including their size and shape. Using the 24-inch telescope at the Caltech Table Mountain Observatory (TMO), we capture two or more 180 second exposures of each target. These images, combined with a file for the predicted background star field and two reference files, are then processed through a series of scripts and programs. Starting with a prediction file and two to five exposures of the asteroid, the data is processed. This original data is about 32MB per observation. Once the data are reduced to only Right Ascension and Declination for each target, the data are ready for delivery. This consists of text only, and for each target takes about 80 bytes; this resulting data reduction is about five orders of magnitude. This method produces observed positions that are refined by about 12 milliarcseconds, a refinement that is accomplished almost nowhere else. The occultation observations that are facilitated by the ephemerides being refined also produce results that are not possible in any other way from ground-based observations.

Dial, Jason↗

MISR Browse data (MISBR_V5)

A MISR Browse Tool is available to allow easy access to ellipsoid-derived, true-color images for each camera reduced to 2.2 km resolution. The MISR red, green and blue bands are used to create the true-color image in JPEG format. The image is intentionally clipped and gamma-stretched to make cloud, ocean and land features visible. The user may find the Browse Tool helpful before ordering data. The tool's purpose is to search and view images in the on-line user interface. However, the browse product can be ordered separately. The Browse Tool page has Orbit-to-Date and Lat/Lon-to-Path/Block conversion tools to help identify particular MISR geographic locations and data files. [Temporal_Coverage: Start_Date=2000-02-24; Stop_Date=] [Spatial_Coverage: Southernmost_Latitude=-90; Northernmost_Latitude=90; Westernmost_Longitude=-180; Easternmost_Longitude=180] [Data_Resolution: Latitude_Resolution=2.2 km; Longitude_Resolution=2.2 km; Horizontal_Resolution_Range=1 km - < 10 km or approximately .01 degree - < .09 degree; Temporal_Resolution=about 15 orbits/day; Temporal_Resolution_Range=Daily - < Weekly].

EOSDIS↗

Rapid Calculation of Spacecraft Trajectories Using Efficient Taylor Series Integration

A variable-order, variable-step Taylor series integration algorithm was implemented in NASA Glenn's SNAP (Spacecraft N-body Analysis Program) code. SNAP is a high-fidelity trajectory propagation program that can propagate the trajectory of a spacecraft about virtually any body in the solar system. The Taylor series algorithm's very high order accuracy and excellent stability properties lead to large reductions in computer time relative to the code's existing 8th order Runge-Kutta scheme. Head-to-head comparison on near-Earth, lunar, Mars, and Europa missions showed that Taylor series integration is 15.8 times faster than Runge- Kutta on average, and is more accurate. These speedups were obtained for calculations involving central body, other body, thrust, and drag forces. Similar speedups have been obtained for calculations that include J2 spherical harmonic for central body gravitation. The algorithm includes a step size selection method that directly calculates the step size and never requires a repeat step. High-order Taylor series integration algorithms have been shown to provide major reductions in computer time over conventional integration methods in numerous scientific applications. The objective here was to directly implement Taylor series integration in an existing trajectory analysis code and demonstrate that large reductions in computer time (order of magnitude) could be achieved while simultaneously maintaining high accuracy. This software greatly accelerates the calculation of spacecraft trajectories. At each time level, the spacecraft position, velocity, and mass are expanded in a high-order Taylor series whose coefficients are obtained through efficient differentiation arithmetic. This makes it possible to take very large time steps at minimal cost, resulting in large savings in computer time. The Taylor series algorithm is implemented primarily through three subroutines: (1) a driver routine that automatically introduces auxiliary variables and sets up initial conditions and integrates; (2) a routine that calculates system reduced derivatives using recurrence relations for quotients and products; and (3) a routine that determines the step size and sums the series. The order of accuracy used in a trajectory calculation is arbitrary and can be set by the user. The algorithm directly calculates the motion of other planetary bodies and does not require ephemeris files (except to start the calculation). The code also runs with Taylor series and Runge-Kutta used interchangeably for different phases of a mission.

Scott, James R.↗

Transportation and Systems Analysis Collaborations in Support of a Federal Consolidated Interim Storage Facility

The U.S. Department of Energy’s Integrated Waste Management (IWM) program under the Office of Nuclear Energy is planning for the future transportation, storage, and eventual disposal of spent nuclear fuel (SNF) and high-level radioactive waste (HLW) from nuclear power plant sites across the United States. To better enable informed decision-making regarding the back end of the nuclear fuel cycle, the IWM program has been sponsoring the development and application of system analysis tools capable of analyzing various options for managing SNF and HLW. With these tools, integrated waste management system (IWMS) architecture analyses are being conducted to support the future deployment of a comprehensive nuclear waste management system that considers all major back-end aspects of the nuclear fuel cycle (i.e., transportation, storage, and disposal). System analyses and assessments typically use these modeling and simulation tools to investigate implications of changes in various assumptions and parameters such as acceptance rates, receipt logic, facility capacities and capabilities, use of standardized canisters, start and stop dates of facilities, etc. The Next Generation System Analysis Model (NGSAM) is an agent-based simulation toolkit that is used for a system-level simulation and analysis focused on SNF management in the United States. An analyst using NGSAM has the ability to define several factors like the number of storage facilities, capacity at each facility, transportation schedules, shipment rates, and other conditions. NGSAM’s primary purpose is to provide a system analyst with capabilities to model the IWMS and gain insights into SNF and HLW management alternatives including the impact of system choices, associated cost estimates, and development of integrated yet flexible approaches. IWM is also developing the Stakeholder Tool for Assessing Radioactive Transportation (START). START is a web-based geospatial tool developed to provide visualization and initial evaluation of transportation options associated with future SNF and HLW shipment planning and operations. This includes characterizing safety, economic, and environmental conditions on and in proximity to shipment origins as well as along prospective transportation routes. Information from the START tool can be presented/shared as maps, graphics, geospatial files, and tabular form to enable easy data representation and export functionality. The system analysis, NGSAM, and START teams had been working closely for several years before formalizing this collaboration. START provides the SNF routing information for use in NGSAM. System analysts use the NGSAM tool to generate results (schedule, costs, infrastructure acquisitions, shipment rates, etc.). Subject-matter experts and system analysts work together to inform how NGSAM should model the waste management system. Specifically, this paper discusses the collaborations between the system analysis, NGSAM, and START teams and their accomplishments over the past year. Some examples of these efforts include calibrating and adding data to the START output files to meet NGSAM needs, gaining a better understanding of START data used in NGSAM, as well as how updates in START data could result in an improved NGSAM analysis. Detailed examples of various tasks that have been performed by the team will be discussed in the full paper. Continued efforts in this direction are expected in the coming years.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

Transportation and System Analysis Collaborations in Support of a Federal Consolidated Interim Storage Facility

The U.S. Department of Energy’s Integrated Waste Management (IWM) program under the Office of Nuclear Energy is planning for the future transportation, storage, and eventual disposal of spent nuclear fuel (SNF) and high-level radioactive waste (HLW) from nuclear power plant and waste custodian sites across the United States. To better enable informed decision-making regarding the back end of the nuclear fuel cycle, the IWM program has been sponsoring the development and application of system analysis tools capable of analyzing various options for managing SNF and HLW. With these tools, integrated waste management system (IWMS) architecture analyses are being conducted to support the future deployment of a comprehensive nuclear waste management system that considers all major back-end aspects of the nuclear fuel cycle (i.e., transportation, storage, and disposal). System analyses and assessments typically use these modeling and simulation tools to investigate implications of changes in various assumptions and parameters such as acceptance rates, receipt logic, facility capacities and capabilities, use of standardized canisters, start and stop dates of facilities, etc. The Next Generation System Analysis Model (NGSAM) is an agent-based simulation toolkit that is used for a system-level simulation and analysis focused on SNF management in the United States. NGSAM’s primary purpose is to provide a system analyst with capabilities to model the IWMS and gain insights into SNF and HLW management alternatives including the impact of system choices, associated cost estimates, and development of integrated yet flexible approaches. An analyst using NGSAM can define several factors like the number of storage facilities, capacity at each facility, transportation schedules, shipment rates, and other conditions. IWM is also developing the Stakeholder Tool for Assessing Radioactive Transportation (START). START is a web-based geospatial tool developed to provide the visualization and initial evaluation of transportation options associated with future SNF and HLW shipment planning and operations. This includes characterizing safety, economic, and environmental conditions at and in proximity to shipment origins as well as along prospective transportation routes. Information from the START tool can be presented/shared as maps, graphics, geospatial files, and tabular form to enable easy data representation and export functionality. The system analysis, NGSAM, and START teams have been working closely for several years before formalizing this collaboration. START provides the SNF transportation routing information for use in NGSAM. System analysts use the NGSAM tool to generate results (schedule, costs, infrastructure acquisitions, shipment rates, etc.). Subject-matter experts and system analysts work together to inform how NGSAM should model the waste management system. Specifically, this paper discusses the collaborations between the system analysis, NGSAM, and START teams and their accomplishments over the past year. Some examples of these efforts include calibrating and adding data to the START output files to meet NGSAM needs, gaining a better understanding of START data used in NGSAM as well as how updates in START data could result in an improved NGSAM analysis. Detailed examples of various tasks that have been performed by the team will be discussed in the full paper. Continued efforts in this direction are expected in the coming years.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

Parallel NPARC: Implementation and Performance

Version 3 of the NPARC Navier-Stokes code includes support for large-grain (block level) parallelism using explicit message passing between a heterogeneous collection of computers. This capability has the potential for significant performance gains, depending upon the block data distribution. The parallel implementation uses a master/worker arrangement of processes. The master process assigns blocks to workers, controls worker actions, and provides remote file access for the workers. The processes communicate via explicit message passing using an interface library which provides portability to a number of message passing libraries, such as PVM (Parallel Virtual Machine). A Bourne shell script is used to simplify the task of selecting hosts, starting processes, retrieving remote files, and terminating a computation. This script also provides a simple form of fault tolerance. An analysis of the computational performance of NPARC is presented, using data sets from an F/A-18 inlet study and a Rocket Based Combined Cycle Engine analysis. Parallel speedup and overall computational efficiency were obtained for various NPARC run parameters on a cluster of IBM RS6000 workstations. The data show that although NPARC performance compares favorably with the estimated potential parallelism, typical data sets used with previous versions of NPARC will often need to be reblocked for optimum parallel performance. In one of the cases studied, reblocking increased peak parallel speedup from 3.2 to 11.8.

Townsend, S. E.↗

Data for: Climatic Imprint on Interfacially-Controlled Platinum-Palladium Resources

Data package for manuscript "Climatic Imprint on Interfacially-Controlled Platinum-Palladium Resources" by Emily G. Wright, Ivey Wang, Yihang Fang, Elaine D. Flynn, and Jeffrey G. Catalano. This dataset contains adsorption results from experiments designed to investigate the effect of chloride on Pd(II) adsorption to goethite and Pt(II) adsorption to hematite and goethite, including lab experiments, X-ray absorption fine structure spectroscopy, and models of retention within a laterite. See the associated manuscript for full methods information. The file "Wright2025_PtAds_data.csv" contains the target starting Pt concentration (uM), final aqueous Pt and associated error (in uM), calculated adsorbed Pt and associated error (in umol/m2), target and measured aqueous chloride (mM), target aqueous nitrate (mM), final pH, and mineral concentration/loading (g/L). Associated mineral-free controls (mineral loading = 0 g/L) are included; the aqueous Pd error was not calculated and chloride was not measured in every sample. These data appear in Figures 1, S3, S4, S5, S20, and S22 in the associated manuscript. The file "Wright2025_PdAds_data.csv" contains the target starting Pd concentration (uM), final aqueous Pd and associated error (in uM), calculated adsorbed Pd and associated error (in umol/m2), target and measured aqueous chloride (mM), and mineral concentration/loading (g/L). Associated mineral-free controls (mineral loading = 0 g/L) are included; the aqueous Pd error was not calculated and chloride was not measured in every sample. These data appear in Figures 1, S3, S4, S5, and S20 in the associated manuscript. The file "Wright2025_MineralBatches_data.csv" contains the mineral identity and BET specific surface area (m2/g) for every mineral batch synthesized and used in experiments. The annealing time used is listed for hydrothermally annealed goethite. These data appear in Table S2 in the associated manuscript. The file "Wright2025_XRD_data.csv" contains the XRD patterns for every mineral batch synthesized as the counts as a function of two theta (in degrees). See "Wright2025_MineralBatches_data.csv" for more details on specific mineral batches. These data appear in Figure S2 in the associated manuscript. The file "Wright 2025_ZetaPotential_data.csv" contains the measured zeta potentials for samples of goethite (batch G2) at pH 4 the presence of varying amounts of sodium chloride. These data appear in Table S3 in the associated manuscript. The file "Wright2025_XAFSSamples_data.csv" contains the specific mineral batch, measured final aqueous Pd or Pt (uM), measured final aqueous chloride (mM), and estimated adsorbed Pd or Pt (umol/m2) of all XAFS samples. These data appear in Tables S4, S7, S8, and S10 in the associated manuscript. The files "Wright2025_PdXAFS_data.csv" and "Wright2025_PtXAFS_data.csv" contain the normalized spectra of Pd and Pt, respectively, adsorbed to minerals at varying chloride concentrations. See "Wright2025_XAFSSamples_data.csv" for a guide to sample names. Note that "05" in a sample name is equivalent to "0.5". These data appear in Figures 2, S6, S7, S8, S12, S13, and S14 in the associated manuscript. The file "Wright2025_LateriteProfileProfileModelParameters_data.csv" include the ratio of hematite to hematite and goethite in two synthetic, modeled profiles, as well as the modeled surface areas of goethite and hematite as a function of relative depth within the modeled weathering zone. These data were used, in conjunction with equations presented in the paper, to calculate the theoretical concentrations of Pd and Pt (and the resulting Pt/Pd ratio) within the profiles. These data appear in Figure 3 in the associated manuscript. The file "Wright2025_Imagery_data.zip" is a zipped folder containing the TEM and STEM images appear in Figures S18 and S19. Individual files are labeled as either STEM (Fig. S18) or TEM (Fig. S19) with a letter representing the part of the multipart figure.

58 GEOSCIENCES↗

PKI solar thermal plant evaluation at Capitol Concrete Products, Topeka, Kansas

A system feasibility test to determine the technical and operational feasibility of using a solar collector to provide industrial process heat is discussed. The test is of a solar collector system in an industrial test bed plant at Capitol Concrete Products in Topeka, Kansas, with an experiment control at Sandia National Laboratories, Albuquerque. Plant evaluation will occur during a year-long period of industrial utilization. It will include performance testing, operability testing, and system failure analysis. Performance data will be recorded by a data acquisition system. User, community, and environmental inputs will be recorded in logs, journals, and files. Plant installation, start-up, and evaluation, are anticipated for late November, 1981.

Hauger, J. S.↗