SEARCH · Engineering Papers

Results for “coding standards”

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.

SourceResearch connectionFrom yearThrough year

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

At least 145 records · Page 8

All sources NASA NTRS DOE OSTI

NASA NTRS2001

Code Sharing and Collaboration: Experiences From the Scientist's Expert Assistant Project and Their Relevance to the Virtual Observatory

In the Virtual Observatory (VO), software tools will perform the functions that have traditionally been performed by physical observatories and their instruments. These tools will not be adjuncts to VO functionality but will make up the very core of the VO. Consequently, the tradition of observatory and system independent tools serving a small user base is not valid for the VO. For the VO to succeed, we must improve software collaboration and code sharing between projects and groups. A significant goal of the Scientist's Expert Assistant (SEA) project has been promoting effective collaboration and code sharing among groups. During the past three years, the SEA project has been developing prototypes for new observation planning software tools and strategies. Initially funded by the Next Generation Space Telescope, parts of the SEA code have since been adopted by the Space Telescope Science Institute. SEA has also supplied code for the SIRTF (Space Infrared Telescope Facility) planning tools, and the JSky Open Source Java library. The potential benefits of sharing code are clear. The recipient gains functionality for considerably less cost. The provider gains additional developers working with their code. If enough users groups adopt a set of common code and tools, de facto standards can emerge (as demonstrated by the success of the FITS standard). Code sharing also raises a number of challenges related to the management of the code. In this talk, we will review our experiences with SEA--both successes and failures, and offer some lessons learned that might promote further successes in collaboration and re-use.

Korathkar, Anuradha↗

DOE OSTI2017

Capture and coding of industry and occupation measures: Findings from eight National Program of Cancer Registries states

Background Although data on industry and occupation (I&O) are important for understanding cancer risks, obtaining standardized data is challenging. This study describes the capture of specific I&O text and the ability of a web‐based tool to translate text into standardized codes. Methods Data on 62 525 cancers cases received from eight National Program of Cancer Registries (NPCR) states were submitted to a web‐based coding tool developed by the National Institute for Occupational Safety and Health for translation into standardized I&O codes. We determined the percentage of sufficiently analyzable codes generated by the tool. Results Using the web‐based coding tool on data obtained from chart abstraction, the NPCR cancer registries achieved between 48% and 75% autocoding, but only 12‐57% sufficiently analyzable codes. Conclusions The ability to explore associations between work‐related exposures and cancer is limited by current capture and coding of I&O data. Increased training of providers and registrars, as well as software enhancements, will improve the utility of I&O data.

Freeman, MaryBeth B.↗

DOE OSTI2024

Advanced Manufactured Home Case Study: A Collaboration for High-Efficiency, Affordable Housing

The introduction of Zero Energy Ready Home Manufactured Homes (ZERH MH) qualification for manufactured homes has generated significant attention and interest in the industry to employ advanced manufacturing techniques. VEIC engaged with Titan Homes to create an advanced manufactured home design that employs ZERH standards, other client-driven above-code standards, and manufacturing processes improvements. This case study identifies specific energy-efficient and quality improvement measures that were implemented to achieve certification and take advantage of incentives for home manufacturers.

14 SOLAR ENERGY↗

DOE OSTI2024

Building Performance Standards and Energy Code Alignment: Technical Brief

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

DOE OSTI2025

Building Performance Standards and Energy Code Alignment - Technical Brief

Building energy codes focus on building design, construction and renovation and have significantly increased building efficiency since the first national energy code was published in 1975. Most jurisdictions have energy codes based on ANSI/ASHRAE/IES Standard 90.1 (hereto referred to as Standard 90.1) and the International Energy Conservation Code (IECC). Compliance options available in these model energy codes include a prescriptive path, whole building performance paths – including IECC Total Building Performance (TBP), Standard 90.1 Energy Cost Budget (ECB) method and Performance Rating Method (PRM) – and system performance paths for envelope and heating, ventilation, and air-conditioning systems. Building performance standard (BPS) policies are an emerging policy tool used by jurisdictions to reduce the operational energy use or greenhouse gas (GHG) emissions of the existing commercial building stock. BPS policies vary widely between jurisdictions and are tailored to each location’s climate and energy goals. Intuitively, projects that met a recent edition of the energy code should comply with the BPS targets. However, some new buildings may struggle with meeting the BPS for the following reasons: 1. Energy codes focus on the design of the building and its projected ability to perform efficiently, while BPS compliance is dependent on the actual ongoing performance of the building, considering variables like occupancy, operation, and maintenance. 2. There are significant differences in the methodologies used to determine BPS compliance versus code compliance, including how each handles compliance metrics, handling of building amenities, and renewable energy generation. 3. The prescriptive compliance path in the energy code is based on performance of individual building components, as opposed to the performance compliance path which accounts for holistic building design strategies and interdependent building systems. This can result in a significant variability in post-occupancy performance for buildings built using the prescriptive path. Designs on the lower end of the permitted efficiency range may struggle with meeting the BPS.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

NASA NTRS2024

GCAS Visualization Codebase Augmentation Migration to Modern Standards and Feature Enhancements

The Glenn Research Center Communication Analysis Suite (GCAS) includes many analysis tools that can be used to support a wide range of scenarios. It includes a visualization tool that implements the three.js graphics library to display a three-dimensional (3D) representation of its results. This software will enable researchers, engineers, and mission planners to interact intuitively with and understand the results of their analyses, which might not be apparent from raw data. With NASA’s efforts to return humans to the Moon as a part of the Artemis missions, the GCAS has been used extensively for lunar terrain and landing system development analysis, which is vital to ensuring mission achievability and safety. This has created the need to add several significant features to the visualization tool, such as the ability to display the terrain of the lunar surface accurately and to provide information demonstrating how a given region might impact mission objectives. Many of the changes made to the visualization tool can be separated into one of three general advancements: code restructuring to adhere to modern coding standards and practices, new user camera controls for first-person and third-person perspective views, and a terrain generation feature to enable rendering highly accurate terrains based on any celestial body’s digital elevation model (DEM) in GeoTIFF format. These improvements notably elevate the visualization tool's functionality, accuracy, and user interaction while providing a robust foundation for future development.

Visualization↗

NASA NTRS1989

International standards activities in image data compression

Integrated Services Digital Network (ISDN); coding for color TV, video conferencing, video conferencing/telephone, and still color images; ISO color image coding standard; and ISO still picture standard are briefly discussed. This presentation is represented by viewgraphs only.

Haskell, Barry↗

NASA NTRS1976

Coordinated design of coding and modulation systems

The joint optimization of the coding and modulation systems employed in telemetry systems was investigated. Emphasis was placed on formulating inner and outer coding standards used by the Goddard Spaceflight Center. Convolutional codes were found that are nearly optimum for use with Viterbi decoding in the inner coding of concatenated coding systems. A convolutional code, the unit-memory code, was discovered and is ideal for inner system usage because of its byte-oriented structure. Simulations of sequential decoding on the deep-space channel were carried out to compare directly various convolutional codes that are proposed for use in deep-space systems.

Massey, J. L.↗

DOE OSTI2016

Technology Solutions Case Study: Southern Energy Homes, First DOE Zero Energy Ready Manufactured Home

The country’s first Zero Energy Ready manufactured home that is certified by the U.S. Department of Energy (DOE) is up and running in Russellville, Alabama. The manufactured home was built by a partnership between Southern Energy Homes and the Advanced Residential Integrated Energy Solutions Collaborative (ARIES), which is a DOE Building America team. The effort was part of a three-home study including a standard-code manufactured home and an ENERGY STAR® manufactured home. Cooling-season results showed that the building used half the space-conditioning energy of a manufactured home built to the U.S. Department of Housing and Urban Development’s (HUD’s) Manufactured Home Construction and Safety Standards. These standards are known collectively as the HUD Code, which is the building standard for all U.S. manufactured housing.

aries↗

DOE OSTI2015

Designs for Risk Evaluation and Management

The Designs for Risk Evaluation and Management (DREAM) tool was developed as part of the effort to quantify the risk of geologic storage of carbon dioxide (CO 2 ) under the U.S. Department of Energy's National Risk Assessment Partnership (NRAP). DREAM is an optimization tool created to identify optimal monitoring schemes that minimize the time to first detection of CO 2 leakage from a subsurface storage formation. DREAM acts as a post-processer on user-provided output from subsurface leakage simulations. While DREAM was developed for CO 2 leakage scenarios, it is applicable to any subsurface leakage simulation of the same output format. The DREAM tool is comprised of three main components: (1) a Java wizard used to configure and execute the simulations, (2) a visualization tool to view the domain space and optimization results, and (3) a plotting tool used to analyze the results. A secondary Java application is provided to aid users in converting common American Standard Code for Information Interchange (ASCII) output data to the standard DREAM hierarchical data format (HDF5). DREAM employs a simulated annealing approach that searches the solution space by iteratively mutating potential monitoring schemes built of various configurations of monitoring locations and leak detection parameters. This approach has proven to be orders of magnitude faster than an exhaustive search of the entire solution space. The user's manual illustrates the program graphical user interface (GUI), describes the tool inputs, and includes an example application.

(Ruprecht) Yonkofski, Catherine↗

NASA NTRS1992

Multi-mode modem/codec designs

The design of an integrated modem/codec unit which can receive coded and uncoded BPSK an QPSK using de facto standard coding schemes as well as 8PSK-TCM and 16PSK-TCM is examined. The design is totally compatible with today's modulation schemes and capable of processing tomorrow's TCM codes. This is accomplished in the modem by using quadrature channel carrier recovery processing and a version of the MAP phase detector algorithm. The symbol synchronization is accomplished with a derivative of an early-late gate designed to accommodate multilevel signals.

Osborne, William↗

DOE OSTI2026

Field and Model Data Associated with the Manuscript “Drivers of Streamflow Intermittency in Humid Regions: 2. Evaluating Controls on Flow Persistence in an Urbanized Catchment”

This package contains field data, modeling files, and scripts supporting the investigation of the drivers of streamflow intermittency in an urbanized catchment. It includes the field data collected from electrical resistivity tomography (ERT) surveys, distributed temperature sensing (DTS), continuous self-potential (SP) monitoring, groundwater and stilling well. In addition, it contains the data and results of the coupled water- and electrical-flow model developed using the COMSOL Multiphysics and Advanced Terrestrial Simulator (ATS), as well as software files and Jupyter notebooks used to process the data and generate figures in the manuscript submitted for peer review. The data archive is organized in the following directories: 1) Climate Includes hourly precipitation and daily evapotranspiration time series (2024 – 2025) provided as CSV files, alongside a text file detailing dataset units. 2) Coupled_model Field_Application subfolder contains the ATS XML input scripts, data files, output data for the SP site. It also contains the Jupyter notebook (Plot_final_calib.ipynb) to visualize the results of the modeled SP, stream-groundwater exchange and moisture content. The flow model simulation is executed using the ATS XML scripts and the included Python script (generate_data_set.py) to convert ATS output to COMSOL-ready input. COMSOL Multiphysics template (.m can only be used with COMSOL with MATLAB) is executed using the ATS output data to simulate the potential field. 3) Discharge Includes the electrical conductivity (EC) time series (provided as CSV files) from salt slug injections. It also includes the Jupyter notebook (Discharge_process.ipynyb) used to estimate discharge. All discharge measurements collated into rating_curve_processed.csv 4) DTS Contains collated DTS data including raw Stokes and anti-Stokes measurement (provided as .h5 file). It also includes DTS processing.ipynb, a Jupyter notebook for calibrating the DTS data using dts_calibration Python package. cooler_calibration.csv is the DTS calibration CSV used in the calibration sequence. 5) ERT Contains raw resistivity data (provided as CSV files), spatial location of each of the electrodes (provided as CSV files), and files used for the resistivity inversion. 6) Slug_test Includes the slug test data at all the groundwater wells provided as CSV files, as well as the Jupyter notebook (Slug_test.ipynb) for calculating hydraulic conductivity. 7) SP Contains the SP data collected in field at the SP sites (provided as CSV files). 8) Well_data Contains two subfolders: 1) Raw, which provides unprocessed pressure, electrical conductivity and temperature timeseries downloaded from the loggers in all the groundwater and stilling wells, and 2) Processed, which contains sorted, QA/QC timeseries data for each well. The data archive also contains data_process.ipynb, a Jupyter notebook used for field data analysis and generating figures (plotting well, SP, climate, and discharge data, as well as calculating head gradient at sites with nested groundwater wells). Note: Code files (.ipynb, .py, .xml) can be opened in any standard code editor, .exo file can be viewed using Paraview, .h5 files can be opened using HDFView software and h5py Python package, and .resipy file can be opened with the open-source ResIPy software.

ATS↗

DOE OSTI2017

Standardized Definitions for Code Verification Test Problems

This document contains standardized definitions for several commonly used code verification test problems. These definitions are intended to contain sufficient information to set up the test problem in a computational physics code. These definitions are intended to be used in conjunction with exact solutions to these problems generated using Exact- Pack, www.github.com/lanl/exactpack.

97 MATHEMATICS AND COMPUTING↗

DOE OSTI2017

Integrity Assessment of Hanford 242-A Evaporator Facility E-A-1 Re-boiler Vessel via Fluorescein Liquid Tracer Test Methods - 17357

The 242-A Evaporator Facility is critical to the United States Department of Energy's (DOE) Hanford Site clean-up mission due to limited space within the existing Double-Shell Tanks (DSTs) used to store nuclear and chemical waste until future processing. The 242-A Evaporator Facility is currently the sole waste volume reduction process used at Hanford, and the E-A-1 Re-boiler is essential to the Evaporator process. Due to the potential for cross-contamination between the Re-boiler tubes through which waste passes and the tube sheets of uncontaminated steam, an assessment of the Re-boiler vessel's integrity is required for continuing operations of the facility. In order to meet these requirements, an independent integrity assessment was designed to use fluorescein liquid tracer (LT) to verify the leak-tightness of the Re-boiler vessel in accordance with Washington River Protection Solutions, LLC (WRPS) tightness test standards, as well as, the ASME Boiler and Pressure Vessel (B and PV) Code, Section III, Division 1, NB-6300. LT test methodologies were evaluated and determined to be appropriate for a vessel with restricted access, such as the E-A-1 Re-boiler, as it provided the needed sensitivity, reliability, and cost; as well as, exceeded the leak-tightness specifications required by both WRPS and ASME B and PV Code standards. The integrity test requires water laced with fluorescein be circulated through the waste processing loop of the 242-A Evaporator and samples of steam condensate be collected and analyzed for traces of fluorescein to determine leak-tightness. Liquid condensate sampling was conducted prior to and during testing and the samples were analyzed for fluorescein tracer to determine the amount of fluorescein that flowed out of the tubes of the Re-boiler into the steam side of the vessel. Given the established criteria for 'leak-tight,' test results determined that the Re-boiler passed the integrity assessment. After further scrutiny of the 2014 test and data results, it was determined that although the Re-boiler was 'leak-tight,' as established by the test criteria, there was concern of future leakage. The DOE and the DOE Office of River Protection (ORP) requested that WRPS repeat the integrity assessment in two and a half years to determine if the potential leak was growing, which could threaten continuing operations of the 242-A Evaporator. The 2017 test has been redesigned using lessons learned from the 2014 test and was modified to account for ergonomic and safety considerations, ease of repeatability, and accuracy of results. The liquid tracer methodology and test plan developed for the Re-boiler will continue to be implemented in 5 year increments to monitor current and future integrity. The method may also prove useful for other aging components across the Hanford Site, where appropriate. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

NASA NTRS1994

Time synchronized video systems

The idea of synchronizing multiple video recordings to some type of 'range' time has been tried to varying degrees of success in the past. Combining this requirement with existing time code standards (SMPTE) and the new innovations in desktop multimedia however, have afforded an opportunity to increase the flexibility and usefulness of such efforts without adding costs over the traditional data recording and reduction systems. The concept described can use IRIG, GPS or a battery backed internal clock as the master time source. By converting that time source to Vertical Interval Time Code or Longitudinal Time Code, both in accordance with the SMPTE standards, the user will obtain a tape that contains machine/computer readable time code suitable for use with editing equipment that is available off-the-shelf. Accuracy on playback is then determined by the playback system chosen by the user. Accuracies of +/- 2 frames are common among inexpensive systems and complete frame accuracy is more a matter of the users' budget than the capability of the recording system.

Burnett, Ron↗

NASA NTRS1994

An experiment to assess the cost-benefits of code inspections in large scale software development

This experiment (currently in progress) is designed to measure costs and benefits of different code inspection methods. It is being performed with a real development team writing software for a commercial product. The dependent variables for each code unit's inspection are the elapsed time and the number of defects detected. We manipulate the method of inspection by randomly assigning reviewers, varying the number of reviewers and the number of teams, and, when using more than one team, randomly assigning author repair and non-repair of detected defects between code inspections. After collecting and analyzing the first 17 percent of the data, we have discovered several interesting facts about reviewers, about the defects recorded during reviewer preparation and during the inspection collection meeting, and about the repairs that are eventually made. (1) Only 17 percent of the defects that reviewers record in their preparations are true defects that are later repaired. (2) Defects recorded at the inspection meetings fall into three categories: 18 percent false positives requiring no author repair, 57 percent soft maintenance where the author makes changes only for readability or code standard enforcement, and 25 percent true defects requiring repair. (3) The median elapsed calendar time for code inspections is 10 working days - 8 working days before the collection meeting and 2 after. (4) In the collection meetings, 31 percent of the defects discovered by reviewers during preparation are suppressed. (5) Finally, 33 percent of the true defects recorded are discovered at the collection meetings and not during any reviewer's preparation. The results to date suggest that inspections with two sessions (two different teams) of two reviewers per session (2sX2p) are the most effective. These two-session inspections may be performed with author repair or with no author repair between the two sessions. We are finding that the two-session, two-person with repair (2sX2pR) inspections are the most expensive, taking 15 working days of calendar time from the time the code is ready for review until author repair is complete, whereas two-session, two-person with no repair (2sX2pN) inspections take only 10 working days, but find about 10 percent fewer defects.

Porter, A.↗

DOE OSTI2023

MARVEL Project Code of Record, COR-0011

MARVEL Project Code of Record identifies the codes, standards, and procedures necessary to design, develop, construct, and startup the Microreactor Applications Research Validation and Evaluation (MARVEL) Project. No code exceptions to construction of the MARVEL reactor in the traditional sense were identified, meaning there are no technical aspects that fail to meet a code requirement. However, due to the novel design of the MARVEL reactor, not every aspect or system can be precisely covered by the existing ASME Boiler and Pressure Vessel Code. In those cases, the document identifies (with concurrences received) how the ASME Boiler and Pressure Vessel Code is applied in an equivalent or analogous manner.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗

NASA NTRS1990

GCS programmer's manual

A variety of instructions to be used in the development of implementations of software for the Guidance and Control Software (GCS) project is described. This document fulfills the Radio Technical Commission for Aeronautics RTCA/DO-178A guidelines, 'Software Considerations in Airborne Systems and Equipment Certification' requirements for document No. 4, which specifies the information necessary for understanding and programming the host computer, and document No. 12, which specifies the software design and implementation standards that are applicable to the software development and testing process. Information on the following subjects is contained: activity recording, communication protocol, coding standards, change management, error handling, design standards, problem reporting, module testing logs, documentation formats, accuracy requirements, and programmer responsibilities.

Lowman, Douglas S.↗