Search NASA⌕ Search

SEARCH · Search NASA

Results for “Writing”

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 775 records · Page 43

PCF File Format

PCF files are binary files designed to contain gamma spectra and neutron count rates from radiation sensors. It is the native format for the GAmma Detector Response and Analysis Software (GADRAS) package. It can contain multiple spectra and information about each spectrum such as energy calibration. This document outlines the format of the file that would allow one to write a computer program to parse and write such files.

61 RADIATION PROTECTION AND DOSIMETRY↗

Numerical Codes for the DESC-LSST Analysis Pipeline: Core Cosmology Library Standard Modules and Beyond wCDM Modules (Final Technical Report)

The overall objective of the project is to investigate and develop specific software modules and analysis components for the software pipeline of LSST Dark Energy Science Collaboration (DESC). Following the key projects of DESC Science Roadmap (SRM), we will write and test computer codes for the Core Cosmology Library (CCL) in order to complete its modules, functionalities, and interface to work with the analysis pipelines from the five science probes of DESC (parts of SRM deliverables CX4.2TJP, CX6.2CS). We will also code modules for CCL to test models beyond w-Cold-Dark-Matter (wCDM) and modification to gravity (MG). Interfaces for MG models will also be developed for the TJPCOSMO software which is the main pipeline of the Theory and Joint Probe (TJP) working group (deliverable TJP2.3). In order to use the full power of LSST data to constrain MG models, we will also work on constraints from nonlinear regime by running and analyzing MG N-Body simulations using a Parameterized-Post-Friedmann framework into the Gadget-2 simulation package (deliverable TJP2.2). Preliminary results for the simulations were obtained in the past. In collaboration with other DESC groups, we plan to make these simulations feedable to cosmic emulators that are practical for likelihood analyzes (deliverable TJP2.2, parts of CX6.2CS). We will also modify and integrate our current codes for consistency tests between data sets and probes into the pipeline (parts of deliverables CX8.2TJP, TJP2.3). We understand that other groups will contribute to some of these objectives but our team will focus and collaborate with others on the particular part of testing MG and models beyond wCDM and refine the DESC pipeline for this purpose. PI has been coordinating his work with the TJP and CS working groups and the DESC management team. PI is a full member of DESC since June 2013. He and his students have been contributing to LSST-DESC activities and work including TJP telecons, collaboration meetings, hack-weeks, and workshops. PI chaired or co-chaired sessions at collaboration meetings and hack-weeks about testing gravity and models beyond wCDM using LSST. He is coordinating the TJP2 projects for testing models beyond wCDM including the writing of DESC-research-note, development of code for pipeline, and N-Body simulations for MG and beyond wCDM models testable with LSST analyses. As stressed in the DESC white paper, SRM, and P5 report, one of the important questions in understanding cosmic acceleration and dark energy is to be able to distinguish whether the acceleration is due to a dark energy component in the universe or a modification to gravity. Answering these questions will have a significant impact on the question of cosmic acceleration and dark energy. The methods that we will use include analytical work, numerical code, and N-Body simulations. A first approach that that we will use consists of using growth rate parameters that enter the perturbed dynamics equations. These parameters take distinctive values for distinct gravity theories and have potential to distinguish between Dark Energy and Modified Gravity. The second method is to look for inconsistencies in Dark Energy parameter spaces using specific combinations of cosmological data sets. Our investigation addresses the Dark Energy problem that is relevant to the mission of the HEP program to understand how our universe works at its most fundamental level. It will allow us to make progress on the HEP mission to explore the nature of Dark Energy and the basic nature of space and time using future surveys such as LSST. The investigation supports the DOE HEP program Cosmic Frontier as it will contribute to the study and understanding of dark energy and fundamental properties of the universe. The investigation contributes directly to LSST-DESC key projects and their deliverables as described in the Science Road-map document to build analysis pipeline and to test dark energy and beyond wCDM models using LSST.

72 PHYSICS OF ELEMENTARY PARTICLES AND FIELDS↗

UPC++ v1.0 Programmer’s Guide, Revision 2021.9.0

UPC++ is a C++ library that provides Partitioned Global Address Space (PGAS) programming. It is designed for writing parallel programs that run efficiently and scale well on distributed-memory parallel computers. The PGAS model is single program, multiple-data (SPMD), with each separate constituent process having access to local memory as it would in C++. PGAS additionally provides one-sided Remote Memory Access (RMA) to a global address space, which is allocated in shared segments that are distributed over the processes. UPC++ also features Remote Procedure Call (RPC) communication, making it easy to move computation to operate on data that resides on remote processes. In UPC++, all communication operations are explicit, which encourages programmers to be aware of the cost of communication and data movement. Moreover, all communication operations are asynchronous by default, to enable programmers to write code that scales well even on hundreds of thousands of cores.

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗

Large Program Design [Slides]

A slideshow presentation describing how different writing small software coding projects is from writing large software coding projects. It can be OK to just throw together code that is small, single-purpose, and short-lived, but there's more need for good design if the code has to live longer, give highly reliable results, be easy to use, get bigger/cover more physics, cover more application domains. Larger projects also need good code if they are to have more widely-distributed users, have more developers work on it, run larger problems, or run on new architectures.

97 MATHEMATICS AND COMPUTING↗

Initial CEED API (CEED-MS10)

Key components of CEED software development involve fast finite element operator storage and evaluation, architecture optimizations, performant algorithms for all orders, global kernels for finite element operators, efficient use of the memory sub-system, optimal data locality and motion, enhanced scalability and parallelism, and fast tensor contractions. As ultimate goals of the project, CEED is exploring and identifying the best algorithms for the full range of discretizations and applying algorithmic and software development to support ECP applications’ needs. In this milestone, we initiated the development and implementation of a common CEED API consisting of two main components: low-level and high-level APIs. We accomplished the goal of having the low-level component ready for the release of CEED v1.0 in the next quarter, see CEED-MS13. In this report we also provide a highlight from CEED’s integration with the MARBL app and the corresponding Laghos miniapp. A main theme in this work has been the systematic transition of advanced algorithms, developed and tested in Laghos, to the large-scale multi-physics settings of the MARBL code. The low-level CEED API provides a set of FE kernels and components for writing new low-level kernels. Examples include: vector and sparse linear algebra, element matrix assembly over a batch of elements, partial assembly and action for efficient high-order operators like mass, diffusion, advection, etc. The main goal of the low-level API is to establish the basis for the high-level API. Also, identifying such low-level kernels and providing a reference implementation for them serves as the basis for collaboration with vendors and STs. Another goal for the low-level API is to make it easy for applications with their own discretization infrastructure, who do not want to switch directly to using the high-level CEED API, to still evaluate and use the core operations provided by the low-level API. One of the challenges with high-order methods is that a global sparse matrix is no longer a good representation of a high-order linear operator, both with respect to the FLOPs needed for its evaluation, as well as the memory transfer needed for a matvec. Thus, another important question we tried to address while developing the low-level API is: is it possible to abstract out in a natural and efficient way the different implementations and data structures that arise when dealing with various computational device types: CPUs, GPUs, etc. Fully answering this question is beyond the scope of this particular milestone, since that requires longer time as we develop and expand the devices we support. The future high-level API will be the frontend provided by CEED consisting of high-level abstractions such as meshes, finite element spaces and solutions, bilinear forms, solvers, etc. At this high-level, an important aspect of the API will be to provide a uniform abstraction layer for writing code in a portable manner. To achieve that, we plan to utilize the MPI programming model combined with a device abstraction layer (DAL) for finite element computations that we will develop. The DAL will serve as the bridge between the low- and the high-level APIs, allowing a variety of programming models to be used for the low-level kernel implementations. The software artifacts delivered as part of this milestone include an initial CEED API software implementation (libCEED) provided through the CEED website, http://ceed.exascaleproject.org and the CEED GitHub organization, http://github.com/ceed. In addition to details and results from the above R&D efforts, in this document we are also reporting on other project-wide activities performed in Q1 of FY18, including: the Nek5000 v17.0 MFEM v3.3.2 and PETSc v3.8 releases, collaborations with ECP/ST and SciDAC projects, the inaugural Nek5000 hackathon and various outreach activities.

97 MATHEMATICS AND COMPUTING↗

TNSL improvements in FUDGE [Slides]

FUDGE TNSL processing capabilities are improving. New development focuses on reading and writing GNDS, but FUDGE also supports writing to ACE and ENDL. Work provides a chance to compare in-depth with other codes. TNSL processing is mostly complete, but MCGIDI sampling has room for improvement. There are plans to revisit interpolation and to improve strategies for sampling coherent/incoherent elastic.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗

Software Verification Toolkit (SVT): Survey on Available Software Verification Tools and Future Direction

Writing software is difficult. However, writing complex, well tested and designed, and functionally correct software is incredibly difficult. An entire field of study is devoted to the validation and verification of software to address this problem, and in this paper we analyze the landscape of currently available third party software. We have divided our analyses into three separate subsections with regards to software validation: formal methods, static analysis, and test generation. Formal verification is the most complex method in which to validate software correctness, but also the most thorough as it truly validates the mathematical validity of the source code. Static analysis generally is relegated to abstract syntax tree traversal techniques to find errors related to faulty software such as memory leaks or stack overflow issues. Automatic test generation is similar in implementation to static analysis, but pushes a bit further in verifying the boundedness of function inputs and outputs with regards to annotated or parsed criteria. The crux of this report is to analyze and describe the software tools that implement these techniques to validate and verify software. Pros and cons related to installation, utilization, and capabilities of the frameworks are described, and reproducible examples are provided with a focus on usability. The initial survey concluded that the most interesting tools of note are Z3, Isabelle/HOL, and TLA+ with regards to formal verification; and Infer, Frama-C, and SonarQube with regards to static analysis. With these tools in mind, a final conjecture is provided that describes future avenues of utilizing these tools for developing a verification framework to assist in validating existing software at Sandia National Laboratories.

97 MATHEMATICS AND COMPUTING↗

Nanoscale Ferroelectric Control of Novel Electronic States in Layered Two-Dimensional Materials (Final Report)

In this DOE Early Career project “Nanoscale Ferroelectric Control of Novel Electronic States in Layered Two-Dimensional Materials,” the PI’s group has combined ferroelectric field effect with nanoscale domain imaging and writing to design the electronic and optical properties of two-dimensional (2D) van der Waals materials, including graphene and transition metal dichalcogenides MoS2 and ReS2. The van der Waals materials have been prepared into field effect transistor (FET) devices with ferroelectric gates. Through domain patterning in a ferroelectric polymer PVDF-TrEF top-gate via conductive atomic force microscopy, the team has created programmable Schottky junctions in monolayer MoS 2 , where both barrier height and I-V rectifying polarity can be reconfigured. The transport anisotropy of monolayer to few-layer ReS 2 has been mapped out by defining the entire channel into an insulating state and creating nanoscale conducting paths along different directions through domain writing in the ferroelectric top-gate. The result shows that the conductivity along and perpendicular to the Re-chain can differ by >5.5x10 4 . Theoretical modeling points to the band origin of the transport anomaly and reveals the emergence of a flat band in few-layer ReS 2 . The interfacial epitaxial relation between ReS 2 and PVDF-TrFE further promotes the formation of close-packed, highly ordered PVDF-TrFE nanowires with width of 35 nm and 10 nm. Nonvolatile modulation of quantum Hall effect has been achieved in graphene FETs with a ferroelectric oxide Ba 0.4 Sr 0.6 TiO 3 back-gate. Scattering from the remote surface optical phonon in Ba 0.4 Sr 0.6 TiO 3 limits the room temperature mobility of graphene to be about 3x10 4 cm 2 /Vs. Steep-slope switching has been achieved in MoS 2 FETs back-gated by polycrystalline Pb(Zr,Ti)O 3 , which signals a static-state negative capacitance mode without involving an additional dielectric layer. Piezoresponse force microscopy studies show that the sub-threshold swing can be well correlated with the domain wall density in Pb(Zr,Ti)O 3 . The team also observes an unconventional filtering effect of the second harmonic generation response at the MoS 2 /Pb(Zr,Ti)O 3 heterointerface, which can be accounted for by the alignment between one of the polar axes of MoS 2 and the chiral dipole rotation at the surface of domain wall in Pb(Zr,Ti)O 3 . The research supported by this DOE grant has significantly advanced the fundamental understanding and functional design of ferroelectric/2D van der Waals heterostructures for their implementation towards energy applications.

36 MATERIALS SCIENCE↗

Site Ambient Temperatures and Operating Schedules for EIC - Utility CW Considerations

The heat dissipated by the EIC accelerator system and components is ultimately removed by the conventional water-cooling systems that will be ultimately dissipated the waste heat to the atmosphere. An estimated 45 MW of heat will be dissipated to water during full beam operation and that will need to be effectively rejected to the atmosphere. Approximately 50% of the heat is required to be rejected to a low temperature heat sink that cannot be achieved by an evaporative cooling tower during summer. To operate during these summer months, a secondary chilled water refrigeration system will be required that would increase the cost of the cooling water system. Further, operating chiller compressor in the summer months will increase the energy consumption of the machine. This analysis is being prepared to evaluate the impact on operating and capital costs on the cooling system for various summer operating schedules while utilizing the most cost-effective scenario of an evaporative cooling system. The technology selection for the various heat sinks is addressed in a separate write-up and are not expected to change the conclusions of this write-up.

43 PARTICLE ACCELERATORS↗

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↗

UPC++ v1.0 Programmer’s Guide (Rev. 2023.9.0)

UPC++ is a C++ library that supports Partitioned Global Address Space (PGAS) programming. It is designed for writing efficient, scalable parallel programs on distributed-memory parallel computers. The key communication facilities in UPC++ are one-sided Remote Memory Access (RMA) and Remote Procedure Call (RPC). The UPC++ control model is single program, multiple-data (SPMD), with each separate constituent process having access to local memory as it would in C++. The PGAS memory model additionally provides one-sided RMA communication to a global address space, which is allocated in shared segments that are distributed over the processes. UPC++ also features Remote Procedure Call (RPC) communication, making it easy to move computation to operate on data that resides on remote processes. UPC++ was designed to support exascale high-performance computing, and the library interfaces and implementation are focused on maximizing scalability. In UPC++, all communication operations are syntactically explicit, which encourages programmers to consider the costs associated with communication and data movement. Moreover, all communication operations are asynchronous by default, encouraging programmers to seek opportunities for overlapping communication latencies with other useful work. UPC++ provides expressive and composable abstractions designed for efficiently managing aggressive use of asynchrony in programs. Together, these design principles are intended to enable programmers to write applications using UPC++ that perform well even on hundreds of thousands of cores.

97 MATHEMATICS AND COMPUTING↗

IER 484: AFRRI Field Characterization Measurements [Slides]

This lecture includes discussion on the future work of finalizing the data analysis with dose as a function of radial distance and ion chamber integral. Further on agenda is to write manuscript of AFRRI dose characterization and write manuscripts of all NCSP-funded NAD work. Finally, it talks on the goal to publish in Radiation Measurements special issue.

46 INSTRUMENTATION RELATED TO NUCLEAR SCIENCE AND ↗

Finite Element Analysis System Workflow Tools

A collection of MATLAB functions and class definitions called System Workflow Tools (SWFT) are available to semi-automate steps in the simulation process. Some of these steps are often simple and routine for smaller finite element models, but if done directly by an analyst can quickly become labor intensive, cumbersome, and error prone for larger, system level models. Some of SWFT’s capabilities demonstrated in this report includes writing Sierra input decks and processing Quantities of Interest (QOI) from results files. SWFT also writes scripts in order to utilize other software programs such as Cubit (separating system level CAD into subassemblies and components, creating nodesets and sidesets), DAKOTA (ensemble management), and ParaView (contour plots and animations). Detailed commands and workflows from mesh generation to report generation are provided as examples for analysts to utilize SWFT capabilities.

97 MATHEMATICS AND COMPUTING↗

Out of the Lab: 3D Printing on Non-Ideal Surfaces

In this work, coaxial direct ink writing is utilized to print sensitive or encapsulated materials onto heterogeneous and rough substrates. By enclosing the core fluid within a rigid ceramic shell, continuity is maintained even when printing on substrates traditionally considered challenging. This work presents the development of a coaxial ceramic direct ink writing system and investigates co-flow dynamics through microfluidic principles. A specially designed coaxial nozzle enables the co-extrusion of an alumina shell, with indium-tin-oxide inks serving as the core material. This approach allows the fabrication of core-shell ceramic structures suitable for future high-temperature applications on rough surfaces. The colloidal inks are tailored to achieve the necessary rheological properties and sintering performance. Additionally, flow simulations, guided by microfluidic co-flow principles, are employed to define the processing parameters for coaxial printing, ensuring precise control over the core-shell architectures. Physical modeling is further applied to study core deformation and eccentricity. These simulations are experimentally validated, supporting the successful deposition of coaxial ceramic features on heterogeneous, high-temperature ceramic substrates.

20 FOSSIL-FUELED POWER PLANTS↗

End of (3rd) Month Progress Report - PhD Committee

For the months of (May-August), the focus has been to: ● Comply and attend all mandatory LLNL training(s). ● Practice & gain experience, using a 3D printer for direct-ink writing application. ● Construct & Test Cu-Si anodes for battery application: - Si nanoparticles (<100 nm) is alloyed within a Cu-based current collector, via direct-ink writing. - Tuning the overall architecture of the current collector (to accommodate the volume expansion of Si more efficiently/ stabilize its kinetics - of active Si loss). - Based on the following designed configurations: tape-casted, 2D (spiral-square), and 3D (spiral-square/ zig-zag) structures; utilizing commercial-based Cu paste. - Fabricated (half-cell) coin-cells are currently cycling long-term. ● Synthesize new Cu-Si paste, to further tune the rheology properties, for further comparison with commercial Cu-based paste.

99 GENERAL AND MISCELLANEOUS↗

ICSBEP Benchmarking Tutorial for DNCSH

As part of the DOE/NRC Collaboration for Criticality Safety Support for Commercial-Scale HALEU for Fuel Cycles and Transportation (DNCSH), a workshop was held on Teams on how to write a ICSBEP benchmark that meets modern standards. The workshop prepared people performing experiments and writing benchmarks so that they have an increased chance of submitting a benchmark that will be accepted. The workshop was led by experts from LANL, LLNL and Sandia.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

DAOS Benchmarks and Findings

We benchmark DAOS on a 127-node, 4,064-target pool using fio, IOR, IO500, and mdtest, comparing the DFS API against DFuse+POSIX. Single-client fio sweeps show larger block sizes and writes yield higher bandwidth, with similar random/sequential performance. Multi-node IOR (1–32 nodes, 6–48 tasks/node) shows bandwidth saturating around 32 tasks/node, with large transfer sizes hurting read throughput at high concurrency and write latency growing faster than read latency. An 8-node IO500 run shows DFS achieving ~5x higher bandwidth and ~190x higher IOPS than POSIX. We also detail operational issues: SCM target-filling under mdtest, intermittent NA_HOSTUNREACH errors, fio CPU-affinity failures, and a pool error storm resolved by recreation.

George, Rebecca [Thomas Jefferson National Acceler↗

Benchmarking DAOS Filesystem on Aurora

We benchmark the DAOS filesystem on Argonne's Aurora supercomputer (127 nodes, 4,064 targets) using fio, IOR, mdtest, and IO500 to characterize I/O and metadata performance across the DFS API and DFuse+POSIX. Single-client fio shows POSIX bandwidth saturating at 1–2 MiB I/O sizes, with write-heavy workloads outperforming reads. Multi-node IOR shows DFS bandwidth scaling well up to ~32 tasks/node, with write latency growing faster than read latency. An 8-node IO500 evaluation shows DFS achieving ~5x higher bandwidth and ~190x higher IOPS than POSIX. Results indicate DAOS is well-suited to read-heavy workloads like AI training data loading, given appropriately sized transfers and concurrency.

George, Rebecca [College of William and Mary, Will↗