Search NASA⌕ Search

SEARCH · Search NASA

Results for “Manual S”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 19 records
All sourcesNASA NTRSDOE OSTI
DOE OSTI2020

CO₂ Storage prospeCtive Resource Estimation Excel aNalysis (CO₂-SCREEN) User’s Manual

This user’s manual guides the use of the National Energy Technology Laboratory’s (NETL) CO₂ Storage prospeCtive Resource Estimation Excel aNalysis (CO₂-SCREEN) tool, which was developed to aid users screening geologic formations for prospective CO₂ storage resources. This manual is specific to the CO₂-SCREEN 4.0 version which is based in Python. CO₂-SCREEN applies U.S. Department of Energy (DOE) methods and equations for estimating prospective CO₂ storage resources for saline formations, shale formations, and residual oil zones (ROZ). CO₂-SCREEN was developed to be substantive and user-friendly and provide a consistent method for calculating prospective CO₂ storage resources. CO₂-SCREEN uses a Java based graphical user interface for data inputs and uses Python to calculate prospective CO₂ storage resources.

54 ENVIRONMENTAL SCIENCES↗
DOE OSTI2022

PDQ Users Manual. Manual Version 2, for PDQ Code Version 1.20

PDQ is a tool for the management of the input and execution of batch jobs for simulation codes that use a text based input system. It accomplishes this goal by operating at two levels. First, it takes input file templates (commonly known at LANL as input deck templates) and creates multiple instantiations by performing substitutions of data from table files into symbols (variables) found in the template. Second, it provides commands to submit the created files to the SLURM batch system for execution. These two activities taken together produce a whole that is greater than the sum of its parts and provides an elegant way of executing studies across multiple similar simulations while minimizing the risk of typographical errors in the input files. PDQ was originally developed as a job management system called XVS by Jeff McAninch while he was at LANL. Besides the capabilities described here, XVS had many other features specific for interactions with particular simulation codes. After Jeff’s departure, maintenance of XVS was taken over by Rendell Carver; he added some new features as well as kept it functioning as the batch system at LANL was changed from LSF to MOAB to SLURM. In 2017, Rob Pelak decided to develop a different version that removed the additional features (many of which were rendered obsolete with the retirement of the simulation code or batch system that they supported) and produced a cleaner “bare bones” version of XVS. A few other behaviors of XVS that Rob found irksome were altered. Rob gave the resulting code a new name: PDQ. In 2022 Danielle McDermott developed a version that runs under Python 3.X. As suggested by Rob, she used the python2to3 utility to identify most changes. Given that PDQ continues to operate with Python version 2.7 we have advanced the version number to 1.20.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2020

SIGNAL Game Manual

SIGNAL is a first of its kind experimental wargame developed as part of the Project on Nuclear Gaming (PoNG). In this document we describe the rules and game mechanics associated with the online version of SIGNAL created by team members from the University of California, Berkeley, Sandia National Laboratories, and Lawrence Livermore National Laboratory and sponsored by the Carnegie Corporation of New York. The game was developed as part of a larger research project to develop the experimental wargaming methodology and explore its use on a model scenario: the impact of various military capabilities on conflict escalation dynamics. We discuss the results of this research in a forthcoming paper that will include this manual as an appendix. It is our hope that this manual will both contribute to our players' understanding of the game prior to play and that it will allow for replication of the SIGNAL game environment for future research purposes. The manual begins by introducing the terminology used throughout the document. It then outlines the technical requirements required to run SIGNAL. The following section provides a description of the map, resources, infrastructure, tokens, and action cards used in the game environment. The manual then describes the user interface including the chat functions, trade mechanism, currency and population counts necessary for players to plan their actions. It then turns to the sequence of player actions in the game describing the signaling, action, and upkeep phases that comprise each round of play. It then outlines the use of diplomacy including alliances with minor states and trade between players. The manual also describes the process for scoring the game and determining the winner. The manual concludes with tips for players to remember as they embark upon playing the game.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2021

Sierra/SD - How To Manual - 5.2

The How To Manual supplements the User’s Manual and the Theory Manual. The goal of the How To Manual is to reduce learning time for complex end to end analyses. These documents are intended to be used together. See the User’s Manual for a complete list of the options for a solution case. All the examples are part of the Sierra/SD test suite. Each runs as is. The organization is similar to the other documents: How to run, Commands, Solution cases, Materials, Elements, Boundary conditions, and then Contact. The table of contents and index are indispensable. The Geometric Rigid Body Modes section is shared with the Users Manual.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2021

Sierra/SD - How To Manual - 5.4

The How To Manual supplements the User’s Manual and the Theory Manual. The goal of the How To Manual is to reduce learning time for complex end to end analyses. These documents are intended to be used together. See the User’s Manual for a complete list of the options for a solution case. All the examples are part of the Sierra/SD test suite. Each runs as is. The organization is similar to the other documents: How to run, Commands, Solution cases, Materials, Elements, Boundary conditions, and then Contact. The table of contents and index are indispensable. The Geometric Rigid Body Modes section is shared with the Users Manual.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2022

Sierra/SD - How To Manual - 5.6

The How To Manual supplements the User’s Manual and the Theory Manual. The goal of the How To Manual is to reduce learning time for complex end to end analyses. These documents are intended to be used together. See the User’s Manual for a complete list of the options for a solution case. All the examples are part of the Sierra/SD test suite. Each runs as is. The organization is similar to the other documents: How to run, Commands, Solution cases, Materials, Elements, Boundary conditions, and then Contact. The table of contents and index are indispensable. The Geometric Rigid Body Modes section is shared with the Users Manual.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2022

Sierra/SD - How To Manual - 5.8

The How To Manual supplements the User’s Manual and the Theory Manual. The goal of the How To Manual is to reduce learning time for complex end to end analyses. These documents are intended to be used together. See the User’s Manual for a complete list of the options for a solution case. All the examples are part of the Sierra/SD test suite. Each runs as is. The organization is similar to the other documents: How to run, Commands, Solution cases, Materials, Elements, Boundary conditions, and then Contact. The table of contents and index are indispensable. The Geometric Rigid Body Modes section is shared with the Users Manual.

42 ENGINEERING↗
DOE OSTI2022

Sierra/SD - How To Manual - 5.10

The How To Manual supplements the User’s Manual and the Theory Manual. The goal of the How To Manual is to reduce learning time for complex end to end analyses. These documents are intended to be used together. See the User’s Manual for a complete list of the options for a solution case. All the examples are part of the Sierra/SD test suite. Each runs as is. The organization is similar to the other documents: How to run, Commands, Solution cases, Materials, Elements, Boundary conditions, and then Contact. The table of contents and index are indispensable. The Geometric Rigid Body Modes section is shared with the Users Manual.

42 ENGINEERING↗
DOE OSTI2022

MPACT Theory Manual (V.4.3)

This manual presents the theory underlying the three-dimensional (3D) whole-core, pin-resolved neutron transport calculation methodologies employed in the MPACT code. MPACT’s primary goal is to provide accurate sub-pin power distributions in a computationally efficient manner. To accomplish this, MPACT offers several different transport method options. The 2D/1D method, in which 3D problems are decomposed into an axial stack of radial “slices,” is currently the most commonly used. In this option, two-dimensional (2D) planar solutions are provided by the method of characteristics (MOC), and axial solutions are provided via one-dimensional (1D) approximate diffusion, or P3 solutions. The radial and axial solutions are coupled by (i) axial and radial transverse leakages, and (ii) a global 3D coarse mesh finite difference (CMFD) solve, which provides both acceleration and stability to the solution iteration scheme. The subsequent chapters of this manual present a range of topics, including MOC, CMFD, axial nodal transport solvers, 2D/1D, self-shielding, depletion, thermal-hydraulics, and transient methods. Development of the underlying theory of the 2D/1D method is presented, diagrams are included to highlight important algorithmic flow, and important concepts are discussed as appropriate. This manual is intended to be self-sufficient, but references to published articles and other materials are included for further reading. MPACT is a relatively new code, with new capabilities and many computational methods that did not exist until recently. This manual is an even newer document, with chapters written by several different code contributors working under time constraints. For these reasons, the manual is not yet complete and finalized. Future versions of this manual will address current deficiencies.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2025

Sierra/SD – Example Problems Manual – (V5.26)

The Example Problems Manual supplements the User’s Manual and the Theory Manual. The goal of the Example Problems Manual is to reduce learning time for complex end to end analyses. These documents are intended to be used together. See the User’s Manual for a complete list of the options for a solution case. All the examples are part of the Sierra/SD test suite. Each runs as is. The organization is similar to the other documents: How to run, Commands, Solution cases, Materials, Elements, Boundary conditions, and then Contact. The table of contents and index are indispensable. The Geometric Rigid Body Modes section is shared with the Users Manual.

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗
DOE OSTI2026

Sierra/SD – Example Problems Manual – 5.28

Describes the set of example problems, input decks, and meshes that are distributed with Sierra/SD. The Example Problems Manual supplements the User’s Manual and the Theory Manual. The goal of the Example Problems Manual is to reduce learning time for complex end to end analyses. These documents are intended to be used together. See the User’s Manual for a complete list of the options for a solution case. All the examples are part of the Sierra/SD test suite. Each runs as is. The organization is similar to the other documents: How to run, Commands, Solution cases, Materials, Elements, Boundary conditions, and then Contact. The table of contents and index are indispensable. The Geometric Rigid Body Modes section is shared with the Users Manual.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2020

Using online tools at the Bovine Genome Database to manually annotate genes in the new reference genome

With the availability of a new highly contiguous Bos taurus reference genome assembly (ARS-UCD1.2), it is the opportune time to upgrade the bovine gene set by seeking input from researchers. Furthermore, advances in graphical genome annotation tools now make it possible for researchers to leverage sequence data generated with the latest technologies to collaboratively curate genes. For many years the Bovine Genome Database (BGD) has provided tools such as the APOLLO genome annotation editor to support manual bovine gene curation. The goal of this paper is to explain the reasoning behind the decisions made in the manual gene curation process while providing examples using the existing BGD tools. We will describe the sources of gene annotation evidence provided at the BGD, including RNAseq and Iso-Seq data. We will also explain how to interpret various data visualizations when curating gene models, and will demonstrate the value of manual gene annotation. The process described here can be applied to manual gene curation for other species with similar tools. With a better understanding of manual gene annotation, researchers will be encouraged to edit gene models and contribute to the enhancement of livestock gene sets.

59 BASIC BIOLOGICAL SCIENCES↗
DOE OSTI2024

Sierra/SD Example Problems Manual 5.20

The Example Problems Manual supplements the User's Manual and the Theory Manual. The goal of the Example Problems Manual is to reduce learning time for complex end to end analyses. These documents are intended to be used together. See the User's Manual for a complete list of the options for a solution case. All the examples are part of the salinas test suite. Each runs as is.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2024

Sierra/SD – Example Problems Manual – 5.18

The Example Problems Manual supplements the User's Manual and the Theory Manual. The goal of the Example Problems Manual is to reduce learning time for complex end to end analyses. These documents are intended to be used together. See the User's Manual for a complete list of the options for a solution case. All the examples are part of the Sierra/SD test suite. Each runs as is.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2026

Sierra/SD Example Problems Manual - 5.30

The Example Problems Manual supplements the User’s Manual and the Theory Manual. The goal of the Example Problems Manual is to reduce learning time for complex end to end analyses. These documents are intended to be used together. See the User’s Manual for a complete list of the options for a solution case. All the examples are part of the Sierra/SD test suite. Each runs as is.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2020

Sierra/SD - Theory Manual 4.58

Sierra/SD provides a massively parallel implementation of structural dynamics finite element analysis, required for high fidelity, validated models used in modal, vibration, static and shock analysis of structural systems. This manual describes the theory behind many of the constructs in Sierra/SD. For a more detailed description of how to use Sierra/SD, we refer the reader to User's Manual. Many of the constructs in Sierra/SD are pulled directly from published material. Where possible, these materials are referenced herein. However, certain functions in Sierra/SD are specific to our implementation. We try to be far more complete in those areas. The theory manual was developed from several sources including general notes, a programmer notes manual, the user's notes and of course the material in the open literature.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2021

Sierra/SD - Theory Manual

Sierra/SD provides a massively parallel implementation of structural dynamics finite element analysis, required for high fidelity, validated models used in modal, vibration, static and shock analysis of structural systems. This manual describes the theory behind many of the constructs in Sierra/SD. For a more detailed description of how to use Sierra/SD, we refer the reader to User’s Manual. Many of the constructs in Sierra/SD are pulled directly from published material. Where possible, these materials are referenced herein. However, certain functions in Sierra/SD are specific to our implementation. We try to be far more complete in those areas. The theory manual was developed from several sources including general notes, a programmer_notes manual, the user’s notes and of course the material in the open literature.

97 MATHEMATICS AND COMPUTING↗