Search NASA⌕ Search

SEARCH · Search NASA

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.

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

At least 19 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2002

Automated Code Standard Checker 2002

Coding standards are typically levied on flight software in order to help ensure that the code is testable, maintainable, and modifiable. Visually checking software source against a set of coding standards is time consuming and may be prone to error. Software inspection is typically costly and may require large amounts of highly skilled labor. The objective of this center initiative is to develop an automated method to ensure that mission critical software follows the required coding practices and standards.

Trevino, Luis↗
NASA NTRS2005

C++ Coding Standards and Style Guide

This document is based on the "C Style Guide" (SEL-94-003). It contains recommendations for C++ implementations that build on, or in some cases replace, the style described in the C style guide. Style guidelines on any topics that are not covered in this document can be found in the "C Style Guide." An attempt has been made to indicate when these recommendations are just guidelines or suggestions versus when they are more strongly encouraged. Using coding standards makes code easier to read and maintain. General principles that maximize the readability and maintainability of C++ are: (1) Organize classes using encapsulation and information hiding techniques. (2) Enhance readability through the use of indentation and blank lines. (3) Add comments to header files to help users of classes. (4) Add comments to implementation files to help maintainers of classes. (5) Create names that are meaningful and readable.

Hughes, Steven↗
NASA NTRS1992

Bandwidth efficient CCSDS coding standard proposals

The basic concatenated coding system for the space telemetry channel consists of a Reed-Solomon (RS) outer code, a symbol interleaver/deinterleaver, and a bandwidth efficient trellis inner code. A block diagram of this configuration is shown. The system may operate with or without the outer code and interleaver. In this recommendation, the outer code remains the (255,223) RS code over GF(2 exp 8) with an error correcting capability of t = 16 eight bit symbols. This code's excellent performance and the existence of fast, cost effective, decoders justify its continued use. The purpose of the interleaver/deinterleaver is to distribute burst errors out of the inner decoder over multiple codewords of the outer code. This utilizes the error correcting capability of the outer code more efficiently and reduces the probability of an RS decoder failure. Since the space telemetry channel is not considered bursty, the required interleaving depth is primarily a function of the inner decoding method. A diagram of an interleaver with depth 4 that is compatible with the (255,223) RS code is shown. Specific interleaver requirements are discussed after the inner code recommendations.

Costello, Daniel J., Jr.↗
NASA NTRS1977

The proposed coding standard at GSFC

As part of the continuing effort to introduce standardization of spacecraft and ground equipment in satellite systems, NASA's Goddard Space Flight Center and other NASA facilities have supported the development of a set of standards for the use of error control coding in telemetry subsystems. These standards are intended to ensure compatibility between spacecraft and ground encoding equipment, while allowing sufficient flexibility to meet all anticipated mission requirements. The standards which have been developed to date cover the application of block codes in error detection and error correction modes, as well as short and long constraint length convolutional codes decoded via the Viterbi and sequential decoding algorithms, respectively. Included are detailed specifications of the codes, and their implementation. Current effort is directed toward the development of standards covering channels with burst noise characteristics, channels with feedback, and code concatenation.

Morakis, J. C.↗
NASA NTRS1985

Standard Codes for Telemetry and Telecommand

Different systems communicate and development costs reduced. Report discusses efforts to standardize telemetry and telecommand codes of various space programs. Used to detect and correct bit errors in communication channels with low signal-to-noise ratios, codes proliferated in recent years. Each coding/decoding system developed to solve specific problem, but some systems are similar and exhibit similar performance.

Macmedan, M. L.↗
DOE OSTI2026

V2XConnect: Harmonizing the Landscape of Bidirectional Charging Codes, Standards, and Communication Protocols

The utility grid is constantly evolving with new generation sources and diverse loads from backup generators, backup batteries, rooftop photovoltaics (PV), and flexible charging loads. Each of these technologies presents consumers with an opportunity to work with their local utility to promote grid stability, reliability, and affordability. Through a wide range of programs, utilities are incentivizing the use of these resources to benefit the grid. However, especially for devices with inverters that supply power back to the grid, it is important that these assets comply with local grid codes to ensure human safety, power quality, and grid reliability. One of the most promising of these new technologies is the bidirectional electric vehicle (EV) coupled with bidirectional electric vehicle supply equipment (EVSE). This report introduces the technologies that enable bidirectional charging and how these systems operate. It then outlines the necessary interconnection codes and industry standards that govern the operations of grid-tied inverters, including those in bidirectional charging. A key challenge is then outlined from the complex landscape of communication protocols and proprietary systems designed to coordinate these grid assets. Finally, a single gateway solution is proposed to harmonize communications between all assets across an entire site for a cohesive response to grid codes and utility programs that is flexible enough to support a range of market options.

33 ADVANCED PROPULSION SYSTEMS↗
DOE OSTI2025

Code Standard Evaluation for ASME AG-1-2019, Section FL

ASME AG-1 Section FL Deep Bed Sand Filters includes a requirement to use Special Test Sections to provide a representative assessment of the filter efficiency. The SRPPF project design basis is to test the entire filter bed (versus a representative sample) following the same basis methodology to test the existing filters at the Savannah River Site. Using a combination of: 1) the filter testing experience at SRS since the early 1970’s, 2) the methodology found in ASME AG-1 for testing high capacity HEPA filter housings and 3) requirements for stack or duct sampling systems published by the Environmental Protection Agency (EPA), the Special Test Sections methodology for Deep Bed Sand (DBS) filters in ASME AG-1 Section FL has been replaced with a methodology to test the entire DBS filter system.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗
NASA NTRS1996

Lossless Coding Standards for Space Data Systems

The International Consultative Committee for Space Data Systems (CCSDS) is preparing to issue its first recommendation for a digital data compression standard. Because the space data systems of primary interest are employed to support scientific investigations requiring accurate representation, this initial standard will be restricted to lossless compression.

digital data compression digital data compression ↗
NASA NTRS2014

Complete Decoding and Reporting of Aviation Routine Weather Reports (METARs)

Aviation Routine Weather Report (METAR) provides surface weather information at and around observation stations, including airport terminals. These weather observations are used by pilots for flight planning and by air traffic service providers for managing departure and arrival flights. The METARs are also an important source of weather data for Air Traffic Management (ATM) analysts and researchers at NASA and elsewhere. These researchers use METAR to correlate severe weather events with local or national air traffic actions that restrict air traffic, as one example. A METAR is made up of multiple groups of coded text, each with a specific standard coding format. These groups of coded text are located in two sections of a report: Body and Remarks. The coded text groups in a U.S. METAR are intended to follow the coding standards set by National Oceanic and Atmospheric Administration (NOAA). However, manual data entry and edits made by a human report observer may result in coded text elements that do not follow the standards, especially in the Remarks section. And contrary to the standards, some significant weather observations are noted only in the Remarks section and not in the Body section of the reports. While human readers can infer the intended meaning of non-standard coding of weather conditions, doing so with a computer program is far more challenging. However such programmatic pre-processing is necessary to enable efficient and faster database query when researchers need to perform any significant historical weather analysis. Therefore, to support such analysis, a computer algorithm was developed to identify groups of coded text anywhere in a report and to perform subsequent decoding in software. The algorithm considers common deviations from the standards and data entry mistakes made by observers. The implemented software code was tested to decode 12 million reports and the decoding process was able to completely interpret 99.93 of the reports. This document presents the deviations from the standards and the decoding algorithm. Storing all decoded data in a database allows users to quickly query a large amount of data and to perform data mining on the data. Users can specify complex query criteria not only on date or airport but also on weather condition. This document also describes the design of a database schema for storing the decoded data, and a Data Warehouse web application that allows users to perform reporting and analysis on the decoded data. Finally, this document presents a case study correlating dust storms reported in METARs from the Phoenix International airport with Ground Stops issued by Air Route Traffic Control Centers (ATCSCC). Blowing widespread dust is one of the weather conditions when dust storm occurs. By querying the database, 294 METARs were found to report blowing widespread dust at the Phoenix airport and 41 of them reported such condition only in the Remarks section of the reports. When METAR is a data source for an ATM research, it is important to include weather conditions not only from the Body section but also from the Remarks section of METARs.

METAR Decoder/Parser↗
DOE OSTI2024

Safety Codes and Standards Review and Gap Analysis for Applicability to Hydrogen Rail Refueling, Defueling, Maintenance, and Storage

Hydrogen-powered locomotives may present an alternative to diesel for achieving transportation-related decarbonization, energy security, and resilience goals. As an emerging technology, hydrogen locomotives may not have adequate representation in current safety codes and standards. NFPA 2 and other appropriate codes and standards were reviewed to identify technical gaps in the code for hydrogen rail defueling, refueling, maintenance, and storage. Several technical gaps pertaining to setback distances, allowable quantities, ventilation rates, and grounding have been identified. Fueling requirements can be informed by road vehicle standards but may need to be revised for larger quantity hydrogen locomotive systems. Since there are no hydrogen-specific locomotive design and safety standards, some aspects of diesel-based locomotive standards may apply. CGA G- 5.5 currently provides the most guidance on height, placement, orientation, and design of vent systems, while other standards emphasize the importance of shielding vent stacks and provide requirements for orientation of their discharge.

08 HYDROGEN↗
NASA NTRS1988

A new code for Galileo

Over the past six to eight years, an extensive research effort was conducted to investigate advanced coding techniques which promised to yield more coding gain than is available with current NASA standard codes. The delay in Galileo's launch due to the temporary suspension of the shuttle program provided the Galileo project with an opportunity to evaluate the possibility of including some version of the advanced codes as a mission enhancement option. A study was initiated last summer to determine if substantial coding gain was feasible for Galileo and, is so, to recommend a suitable experimental code for use as a switchable alternative to the current NASA-standard code. The Galileo experimental code study resulted in the selection of a code with constant length 15 and rate 1/4. The code parameters were chosen to optimize performance within cost and risk constraints consistent with retrofitting the new code into the existing Galileo system design and launch schedule. The particular code was recommended after a very limited search among good codes with the chosen parameters. It will theoretically yield about 1.5 dB enhancement under idealizing assumptions relative to the current NASA-standard code at Galileo's desired bit error rates. This ideal predicted gain includes enough cushion to meet the project's target of at least 1 dB enhancement under real, non-ideal conditions.

Dolinar, S.↗
DOE OSTI2025

A Review of Regulations, Codes, and Standards for Hydrogen Fuel Cell Electric Bus Use on Airports

This report reviews regulations, codes, and standards to be considered for FCEB operations on airports governing vehicle safety, hydrogen infrastructure, and airport operations. Overall, the review found the existing regulatory framework largely suitable for FCEB operations on airports, with only minor gaps identified pertaining to heavy-duty vehicle fueling, operation and fire safety on airport aprons, and authorization for emergency power use.

08 HYDROGEN↗
NASA NTRS1986

Single-Chip VLSI Reed-Solomon Encoder

Reed-Solomon (RS) encoder based on Berlekamp bit-serial multiplier algorithm. RS code standard, based on code words of 255 8-bit symbols, of which 223 symbols convey information and remaining 32 are check symbols. This code enables correction of up to 16 erroneous information symbols per word. Berlekamp algorithm based on code-generating polynomial with 32 roots that occur in reciprocal pairs. Choice of algorithm permits compact design.

Truong, T. K.↗
NASA NTRS1993

A simulation study of the performance of the NASA (2,1,6) convolutional code on RFI/burst channels

In an earlier report, the LINKABIT Corporation studied the performance of the (2,1,6) convolutional code on the radio frequency interference (RFI)/burst channel using analytical methods. Using an R(sub 0) analysis, the report concluded that channel interleaving was essential to achieving reliable performance. In this report, Monte Carlo simulation techniques are used to study the performance of the convolutional code on the RFI/burst channel in more depth. The basic system model under consideration is shown. The convolutional code is the NASA standard code with generators g(exp 1) = 1+D(exp 2)+D(exp 3)+D(exp 5)+D(exp 6) and g(exp 2) = 1+D+D(exp 2)+D(exp 3)+D(exp 6) and d(sub free) = 10. The channel interleaver is of the convolutional or periodic type. The binary output of the channel interleaver is transmitted across the channel using binary phase shift keying (BPSK) modulation. The transmitted symbols are corrupted by an RFI/burst channel consisting of a combination of additive white Gaussian noise (AWGN) and RFI pulses. At the receiver, a soft-decision Viterbi decoder with no quantization and variable truncation length is used to decode the deinterleaved sequence.

Perez, Lance C.↗
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 between 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 SOFIA, the SIRTF 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, defacto 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 may promote further successes in collaboration and re-use.

Jones, Jeremy↗