Search NASA⌕ Search

SEARCH · Search NASA

Results for “COMPUTER PROGRAM DOCUMENTATION”

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 937 records · Page 52
All sourcesNASA NTRSDOE OSTI
DOE OSTI2016

SAPHIRE 8 Basics An Introduction to Probabilistic Risk Assessment via the Systems Analysis Program for Hands-On Integrated Reliability Evaluations (SAPHIRE) Software P-201

The SAPHIRE Basics course material is intended to both (1) provide guidance for learning SAPHIRE during the Basics class and (2) become a stand-alone reference document after finishing the class. Thus, the format for the class material is a combination of the traditional “overhead-type” of presentation information with a structured, reference-type document.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2022

Bayesian Monte-Carlo Framework: New Methods for Resonance Parameter Evaluation [Slides]

BMC evaluation is a tool to address imperfect data & models, non-linear models, and non-normal PDFs. ENDF-6 format does not allow non-normal parameter PDFs. Storing posterior sets allow for variance, covariance, skewness, etc. To better predict criticality, we could document non-normal parameter PDFs (i.e. asymmetric uncertainty), consider non-linear sensitivity of $\kappa$ eff to resonance parameters, and reduce uncertainty in key resonance parameters.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗
DOE OSTI2018

Software Requirements of SNAP for Editing MELCOR 2.2 Models

Applications of the severe accident analysis code MELCOR, developed for the U.S. Nuclear Regulatory Commission (NRC) by Sandia National Laboratories (SNL), have been supported by the graphical user-interface and post-processing suite Symbolic Nuclear Analysis Package (SNAP), developed for the NRC by Applied Programming Technology (APT). With the release of MELCOR 2.2, new user functionality and models have been introduced and an update to the SNAP MELCOR plugin user interface is necessary to access these new features. This document relates all new features introduced into MELCOR to the development team at APT as well as the NRC.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗
NASA NTRS1975

Finite element solution of low bond number sloshing

The dynamics of liquid propellant in a low Bond number environment which are critical to the design of spacecraft systems with respect to orbital propellant transfer and attitude control system were investigated. Digital computer programs were developed for the determination of liquid free surface equilibrium shape, lateral slosh natural vibration mode shapes, and frequencies for a liquid in a container of arbitrary axisymmetric shape with surface tension forces the same order of magnitude as acceleration forces. A finite volume element representation of the liquid was used for the vibration analysis. The liquid free surface equilibrium shapes were computed for several tanks at various contact angles and ullage volumes. A configuration was selected for vibration analysis and lateral slosh mode shapes and natural frequencies were obtained. Results are documented.

Wohlen, R. L.↗
NASA NTRS1987

RB-ARD: A proof of concept rule-based abort

The Abort Region Determinator (ARD) is a console program in the space shuttle mission control center. During shuttle ascent, the Flight Dynamics Officer (FDO) uses the ARD to determine the possible abort modes and make abort calls for the crew. The goal of the Rule-based Abort region Determinator (RB/ARD) project was to test the concept of providing an onboard ARD for the shuttle or an automated ARD for the mission control center (MCC). A proof of concept rule-based system was developed on a LMI Lambda computer using PICON, a knowdedge-based system shell. Knowdedge derived from documented flight rules and ARD operation procedures was coded in PICON rules. These rules, in conjunction with modules of conventional code, enable the RB-ARD to carry out key parts of the ARD task. Current capabilities of the RB-ARD include: continuous updating of the available abort mode, recognition of a limited number of main engine faults and recommendation of safing actions. Safing actions recommended by the RB-ARD concern the Space Shuttle Main Engine (SSME) limit shutdown system and powerdown of the SSME Ac buses.

Smith, Richard↗
NASA NTRS2004

Space Communications Emulation Facility

Establishing space communication between ground facilities and other satellites is a painstaking task that requires many precise calculations dealing with relay time, atmospheric conditions, and satellite positions, to name a few. The Space Communications Emulation Facility (SCEF) team here at NASA is developing a facility that will approximately emulate the conditions in space that impact space communication. The emulation facility is comprised of a 32 node distributed cluster of computers; each node representing a satellite or ground station. The objective of the satellites is to observe the topography of the Earth (water, vegetation, land, and ice) and relay this information back to the ground stations. Software originally designed by the University of Kansas, labeled the Emulation Manager, controls the interaction of the satellites and ground stations, as well as handling the recording of data. The Emulation Manager is installed on a Linux Operating System, employing both Java and C++ programming codes. The emulation scenarios are written in extensible Markup Language, XML. XML documents are designed to store, carry, and exchange data. With XML documents data can be exchanged between incompatible systems, which makes it ideal for this project because Linux, MAC and Windows Operating Systems are all used. Unfortunately, XML documents cannot display data like HTML documents. Therefore, the SCEF team uses XML Schema Definition (XSD) or just schema to describe the structure of an XML document. Schemas are very important because they have the capability to validate the correctness of data, define restrictions on data, define data formats, and convert data between different data types, among other things. At this time, in order for the Emulation Manager to open and run an XML emulation scenario file, the user must first establish a link between the schema file and the directory under which the XML scenario files are saved. This procedure takes place on the command line on the Linux Operating System. Once this link has been established the Emulation manager validates all the XML files in that directory against the schema file, before the actual scenario is run. Using some very sophisticated commercial software called the Satellite Tool Kit (STK) installed on the Linux box, the Emulation Manager is able to display the data and graphics generated by the execution of a XML emulation scenario file. The Emulation Manager software is written in JAVA programming code. Since the SCEF project is in the developmental stage, the source code for this type of software is being modified to better fit the requirements of the SCEF project. Some parameters for the emulation are hard coded, set at fixed values. Members of the SCEF team are altering the code to allow the user to choose the values of these hard coded parameters by inserting a toolbar onto the preexisting GUI.

Hill, Chante A.↗
NASA NTRS2011

Hypervelocity Impact Test Fragment Modeling: Modifications to the Fragment Rotation Analysis and Lightcurve Code

Hypervelocity impact tests on test satellites are performed by members of the orbital debris scientific community in order to understand and typify the on-orbit collision breakup process. By analysis of these test satellite fragments, the fragment size and mass distributions are derived and incorporated into various orbital debris models. These same fragments are currently being put to new use using emerging technologies. Digital models of these fragments are created using a laser scanner. A group of computer programs referred to as the Fragment Rotation Analysis and Lightcurve code uses these digital representations in a multitude of ways that describe, measure, and model on-orbit fragments and fragment behavior. The Dynamic Rotation subroutine generates all of the possible reflected intensities from a scanned fragment as if it were observed to rotate dynamically while in orbit about the Earth. This calls an additional subroutine that graphically displays the intensities and the resulting frequency of those intensities as a range of solar phase angles in a Probability Density Function plot. This document reports the additions and modifications to the subset of the Fragment Rotation Analysis and Lightcurve concerned with the Dynamic Rotation and Probability Density Function plotting subroutines.

Gouge, Michael F.↗
DOE OSTI2026

(U)Vendor Sanitization Requirements – SIEMENS Control

This document defines the software requirements for the sanitization of the IPC and or the controller. The system is intended to manage part programs and associated data (e.g. simulations, probing data) by capturing metadata, securely sanitizing files, logging operations, backing up data to a defined path, deploying a user defined program to a controller, and restoring part programs and associated data when required.

42 ENGINEERING↗
NASA NTRS1991

Developing and utilizing an Euler computational method for predicting the airframe/propulsion effects for an aft-mounted turboprop transport. Volume 1: Theory document

An Euler flow solver was developed for predicting the airframe/propulsion integration effects for an aft-mounted turboprop transport. This solver employs a highly efficient multigrid scheme, with a successive mesh-refinement procedure to accelerate the convergence of the solution. A new dissipation model was also implemented to render solutions that are grid insensitive. The propeller power effects are simulated by the actuator disk concept. An embedded flow solution method was developed for predicting the detailed flow characteristics in the local vicinity of an aft-mounted propfan engine in the presence of a flow field induced by a complete aircraft. Results from test case analysis are presented. A user's guide for execution of computer programs, including format of various input files, sample job decks, and sample input files, is provided in an accompanying volume.

Chen, H. C.↗
DOE OSTI2018

Safety Requirement Management System (SRMS) - Improved Documented Safety Analyses Implementation - 18476

Savannah River Remediation (SRR) developed a new software application, Safety Requirement Management System (SRMS), to improve Documented Safety Analysis (DSA) safety requirement implementation in the Savannah River Site's Liquid Waste facilities. Technical Safety Requirement (TSR) Limited Conditions of Operations (LCOs) and related surveillances were previously tracked using four different applications. Due to their differences and their age, the applications introduced a number of operational challenges and vulnerabilities, including outdated platforms, usage demands beyond original design, and different organizational work processes. SRMS was developed to resolve these issues by using a single web-based approach that provides consistency, wider accessibility, simpler maintenance, and a platform for additional functionality. Other SRS facilities are evaluating the application for its applicability as a standard practice across the site. The new SRMS application decreased the administrative overhead for application maintenance, provided the needed TSR change management functionality, and reduced error precursors with the following advantages: - Consistent process/application across all SRR facilities - More efficient way to track and communicate compliance with DSA time-related requirements (i.e., TSR LCOs and surveillances). - Web-based search capability for LCO entries/exits and a record of surveillance performances. - TSR change management and independent reviews through electronic approvals. For example, the application provides the ability to bundle and stage LCO and surveillance changes associated with a TSR revision. The approval process involves multiple roles from the facility to ensure validity. - Formal configuration management program, fully supported by software life cycle documents. SRMS was implemented at Defense Waste Processing Facility (DWPF) in June 2017, with implementation in all Liquid Waste facilities expected by the end of 2017. Next, SRR plans to expand SRMS functionality to include a linking document database (LDD) to support the DSA requirements. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗
DOE OSTI2025

Progress Towards NQA-1 for Cardinal in FY25

Cardinal is a wrapping of the GPU-oriented spectral element Computational Fluid Dynamics (CFD) code NekRS and the Monte Carlo particle transport code OpenMC within the Multiphysics Object-Oriented Simulation Environment (MOOSE). Cardinal provides high-resolution thermal-hydraulics and/or radiation transport feedback to MOOSE multiphysics simulations. Multiphysics feedback is implemented in a geometry-agnostic manner which eliminates the need for rigid one-to-one mappings. A generic data transfer implementation also allows NekRS and OpenMC to couple to any MOOSE application, enabling a broad set of multiphysics capabilities. Cardinal simulations can also leverage combinations of MPI, OpenMP, and GPU resources. Cardinal continuous development and improvement efforts have led to the software being considered as a high-fidelity design and licensing tool for key areas of nuclear reactor relevant physics, including neutron transport, fluid flow, heat transfer, and mechanical processes. The fast development and expansion of the software from a pure R&D framework towards its application in the nuclear industry and regulation require a focus on developing, enhancing,and maintaining Cardinal’s software quality through strict adherence to a Software Quality Assurance (SQA) framework and SQA program. To facilitate compliance with SQA standards, the Cardinal SQA Program was initiated during Fiscal Year 2023 (FY23). During the development of the Cardinal SQA Program, multiple gaps have been identified. These gaps are primarily related to model verification and code pedigree as they relate to the use of Cardinal as an analysis tool. These gaps were captured in a report published in 2023. A second report highlighted the progress made during Fiscal Year 2024 (FY24) and described Argonne’s effort to document and integrate software verification within Cardinal’s software development process. This report documents the progress made towards NQA-1 for Cardinal in the Fiscal Year 2025 (FY25). All cases in the expanded Continuous Integration (CI) suite of NekRS are included in this report which test the solvers and modules available in NekRS exhaustively. The NekRS tests are integrated with the Cardinal CI suite and made available in publicly accessible Github documentation. Following the CI practice permits integrating of source code changes frequently and ensuring that the integrated codebase clears the verification testing for the software. Also in this report is a brief overview of the development of the Cardinal Software Quality Assurance Plan (SQAP) that was done in FY25, though it should be noted that the rest of the documentation for the SQA program needs to be developed in a future step of this task.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗
NASA NTRS1972

Reliability history of the Apollo guidance computer

The Apollo guidance computer was designed to provide the computation necessary for guidance, navigation and control of the command module and the lunar landing module of the Apollo spacecraft. The computer was designed using the technology of the early 1960's and the production was completed by 1969. During the development, production, and operational phase of the program, the computer has accumulated a very interesting history which is valuable for evaluating the technology, production methods, system integration, and the reliability of the hardware. The operational experience in the Apollo guidance systems includes 17 computers which flew missions and another 26 flight type computers which are still in various phases of prelaunch activity including storage, system checkout, prelaunch spacecraft checkout, etc. These computers were manufactured and maintained under very strict quality control procedures with requirements for reporting and analyzing all indications of failure. Probably no other computer or electronic equipment with equivalent complexity has been as well documented and monitored. Since it has demonstrated a unique reliability history, it is important to evaluate the techniques and methods which have contributed to the high reliability of this computer.

Hall, E. C.↗
NASA NTRS1995

TADS: A CFD-based turbomachinery and analysis design system with GUI. Volume 1: Method and results

The primary objective of this study was the development of a computational fluid dynamics (CFD) based turbomachinery airfoil analysis and design system, controlled by a graphical user interface (GUI). The computer codes resulting from this effort are referred to as the Turbomachinery Analysis and Design System (TADS). This document describes the theoretical basis and analytical results from the TADS system. TADS couples a throughflow solver (ADPAC) with a quasi-3D blade-to-blade solver (RVCQ3D) in an interactive package. Throughflow analysis capability was developed in ADPAC through the addition of blade force and blockage terms to the governing equations. A GUI was developed to simplify user input and automate the many tasks required to perform turbomachinery analysis and design. The coupling of various programs was done in a way that alternative solvers or grid generators could be easily incorporated into the TADS framework. Results of aerodynamic calculations using the TADS system are presented for a highly loaded fan, a compressor stator, a low-speed turbine blade, and a transonic turbine vane.

Topp, D. A.↗
NASA NTRS2001

Publicly Available Numerical Codes for Modeling the X-ray and Microwave Emissions from Solar and Stellar Activity

We have posted numerical codes on the Web for modeling the bremsstrahlung x-ray emission and the a gyrosynchrotron radio emission from solar and stellar activity. In addition to radiation codes, steady-state and time-dependent Fokker-Planck codes are provided for computing the distribution and evolution of accelerated electrons. A 1-D hydrodynamics code computes the response of the stellar atmosphere (chromospheric evaporation). A code for modeling gamma-ray line spectra is also available. On-line documentation is provided for each code. These codes have been developed for modeling results from the High Energy Solar Spectroscopic Imager (HESSI) along related microwave observations of solar flares. Comprehensive codes for modeling images and spectra of solar flares are under development. The posted codes can be obtained on NASA/Goddard's HESSI Web Site at http://hesperia.gsfc.nasa.gov/hessi/modelware.htm. This work is supported in part by the NASA Sun-Earth Connection Program.

Holman, Gordon D.↗
NASA NTRS2012

Electronic Handbooks Simplify Process Management

Getting a multitude of people to work together to manage processes across many organizations for example, flight projects, research, technologies, or data centers and others is not an easy task. Just ask Dr. Barry E. Jacobs, a research computer scientist at Goddard Space Flight Center. He helped NASA develop a process management solution that provided documenting tools for process developers and participants to help them quickly learn, adapt, test, and teach their views. Some of these tools included editable files for subprocess descriptions, document descriptions, role guidelines, manager worksheets, and references. First utilized for NASA's Headquarters Directives Management process, the approach led to the invention of a concept called the Electronic Handbook (EHB). This EHB concept was successfully applied to NASA's Small Business Innovation Research (SBIR) and Small Business Technology Transfer (STTR) programs, among other NASA programs. Several Federal agencies showed interest in the concept, so Jacobs and his team visited these agencies to show them how their specific processes could be managed by the methodology, as well as to create mockup versions of the EHBs.

Source record↗
DOE OSTI2017

Portable Radiation Package (PRP) Instrument Handbook

The Portable Radiation Package (PRP) was developed to provide basic radiation information in locations such as ships at sea where proper exposure is remote and difficult, the platform is in motion, and azimuth alignment is not fixed. Development of the PRP began at Brookhaven National Laboratory (BNL) in the mid-1990s and versions of it were deployed on ships in the U.S. Department of Energy (DOE) Atmospheric Radiation Measurement (ARM) Climate Research Facility’s Nauru-99 project. The PRP was deployed on ships in support of the National Aeronautics and Space Administration (NASA) Sensor Intercomparison for Marine Biological and Interdisciplinary Ocean Studies (SIMBIOS) program. Over the years the measurements have remained the same while the post-processing data analysis, especially for the FRSR, has evolved. This document describes the next-generation Portable Radiation Package (PRP2) that was developed for the DOE ARM Facility, under contract no. 9F-31462 from Argonne National Laboratory (ANL). The PRP2 has the same scientific principles that were well validated in prior studies, but has upgraded electronic hardware. The PRP2 approach is completely modular, both in hardware and software. Each sensor input is treated as a separate serial stream into the data collection computer. In this way the operator has complete access to each component of the system for purposes of error checking, calibration, and maintenance. The resulting system is more reliable, easier to install in complex situations, and more amenable to upgrade.

46 INSTRUMENTATION RELATED TO NUCLEAR SCIENCE AND ↗
DOE OSTI2024

Verification of RESRAD-OFFSITE Code (V.4)

This report documents the verification of RESRAD-OFFSITE Version 4.0 and describes, where necessary, the verification of the following: • The data comprising the standard dose and risk coefficient libraries in the RESRAD database files Master_dcf_ICRP07.mdb and Master_dcf_2k.mdb. • The extraction and transfer of the data from the selected database file to the computational code by the RESRAD-OFFSITE 4.0 interface, ResOWin.exe. • The different processes that are modeled by the main computational code in RESRAD OFFSITE 4.0, ResOMain.exe. • The data displayed in the graphical and text reports. Many verifications were performed as part of the quality assurance quality control program associated with the development and release of RESRAD-OFFSITE 4.0, namely: • developer testing, • internal independent testing, and • release testing. Some were also performed in response to questions from users regarding the performance of the code. The main text of the report focuses on summarizing a subset of those tests, both independent and developer tests that verified the computations performed by the code. The verifications included in this report served as the basis for the development of the release tests of the computational executables and provided the quantitative results to be compared with the code output. The input and output interfaces and the data transfers between the various executables of the code were tested while performing the verification testing. They were tested intentionally during release testing. This report also provides some basic information to help in understanding the activities that were verified. The report: • outlines the components of RESRAD-OFFSITE 4.0 and the interconnections between these components, • outlines the processes modeled by the computational code, • provides summary figures and tables to offer confirmation of the verification of the computational components of the code, • reproduces the verifiers’ reports, if available, in individual appendices, • refers to the previous verification report (Yu et al. 2011) for more details about some of the verifications, and • reproduces the test cases and the testers’ reports from the release testing in individual appendices, when possible.

54 ENVIRONMENTAL SCIENCES↗
NASA NTRS1973

Interdisciplinary research on the application of ERTS-1 data to the regional land use planning process.

Although the degree to which ERTS-1 imagery can satisfy regional land use planning data needs is not yet known, it appears to offer means by which the data acquisition process can be immeasurably improved. This paper documents the initial experiences of an interdisciplinary group attempting to formulate ways of analyzing the effectiveness of ERTS-1 imagery as a base for environmental monitoring and the resolution of regional land allocation problems. Because of the need to describe and depict regional resource complexity in an interrelatable state, certain resources within the geographical regions have been inventoried and stored in a two-dimensional computer-based map form. Computer oriented processes were developed to provide for the economical storage, analysis and spatial display of natural and cultural data for regional land use planning purposes. Statistical programs have been developed that correlate interpreted data with stored data, both spatially and numerically.

Clapp, J. L.↗