Search NASA⌕ Search

SEARCH · Search NASA

Results for “data formats”

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 73 records · Page 4

Bridging the Gap Between LLMs and LNS with Dynamic Data Format and Architecture Codesign

Deep neural networks (DNNs) have achieved tremendous success in the past few years. However, their training and inference demand exceptional computational and memory resources. Quantization has been shown as an effective approach to mitigate the cost, with the mainstream data types reduced from FP32 to FP16/BF16 and recently FP8 in the latest NVIDIA H100 GPUs. With increasingly aggressive quantization, however, the conventional floating-point formats suffer from limited precision in representing numbers around zero. Recently, NVIDIA demonstrated the potential of using a Logarithmic Number System (LNS) for the next generation of tensor cores. While LNS mitigates the hurdles in representing small numbers, in this work we observed a mismatch between LNS and the emerging Large Language Models (LLM), where LLM exhibits significant outliers when directly adopting the LNS format. In this paper, we present a data-format/architecture codesign to bright this gap. On the format side, we propose a dynamic LNS format to flexibly represent outliers at a higher precision, by exploiting asymmetry in the LNS representation and identifying outliers through a per-vector basis. On the architecture side, for demonstration, we realize the dynamic LNS format in a systolic array, which can handle the irregularity of the outliers at runtime. We implement our approach on an Alveo U280 FPGA as a prototype. Experimental results show that our design can effectively handle the outliers and resolve the mismatch between LNS and LLM, contributing to an accuracy improvement of 15.4% and 16% over the floating-point and the original LNS baselines, using four state-of-the-art LLM models. Our observation and design lay a solid foundation for the large-scale adoption of the LNS format in the next-generation deep learning hardware.

Haghi, Pouya↗

PACE Technical Report Series, Volume 12: The PACE Level 1C data format

NASA's Plankton, Aerosol, Cloud, ocean Ecosystem (PACE) mission will make global ocean color and atmospheric measurements to provide extended data records of ocean ecology and global biogeochemistry, along with polarimetric measurements for advanced observations of aerosols, clouds and the ocean. PACE will contain three instruments: the primary Ocean Color Instrument (OCI), and two multi-angle polarimeters (MAPs). The latter instruments are contributed under a ‘Do-No-Harm’ (to the rest of the PACE mission) principle, and the PACE Science Data Processing System (SDPS) is only required to produce Level-1b (geolocated radiances with calibration applied) data without performance requirements. However, there is a strong desire to produce data in a format that merges the disparate spatial resolutions, viewing geometry and sampling nature of the three instruments. Our terminology for this format is Level 1c (L1C). This format will be an input to Level 2 algorithms produced from standalone MAP instrument observations, or from algorithms employing multi-sensor fusion. Creating the L1C format has several components. This includes choice of projection method, the means by which multi-angle views are properly incorporated into that projection (‘aggregation’) the means to represent wavelength and light polarization state, the selection of data to be included within the L1C file, and the handling of ancillary data either required for L1C file generation or needed in that format for L2 processing.

PACE↗

Precision of ENDF and ENDL Formatted Data Files

The purpose is to ensure that today’s processing codes produced output to meet today’s accuracy needs. Since 1958 ENDL and about 1965 ENDF have each used a text format to define nuclear and atomic data in 11 columns for each data field. When these formats originated this was judged to be adequate to reproduce the accuracy of data at the time and to meet the needs of our applications. When these formats originated the dominant computer language of the day was FORTRAN and if written using an E11.4 format it would include only 4 or 5 digits of precision, e.g., 0.1234E-03 or 1.2345E-02, varying from one computer/system to another the result was not even unique. In the case of ENDF the 4 digit precision was not even adequate to uniquely define the atomic weight of the target, e.g., U238 = 92238 = 0.9224E+5 = WRONG! From its inceptions the ENDF format had a precision problem. One of my first tasks when in 1967 fresh out of graduate school I joined what later became the National Nuclear Data Center (NNDC), was to address this precision problem. By working with ENDF producers and users throughout the U.S. we verified, 1) E or D is not required to define FORTRAN readable numbers, e.g., E+4 or +4 are both o.k. 2) With ENDF energy eV and cross section in barns, 2 digit exponents are almost never required. 3) Since energy is never negative we could use the first of the 11 columns for a digit. Knowing this allowed us to produce ENDF/B-II to 6 or 7 digit precision, e.g., blank, decimal point, 2 or 3 digit exponent, e.g., ^1.23456-12 or ^1.234567-3. Below is an example of the actual ENDF/B-II data released. Note, the date 1970 and the atomic weight, ZA, uniquely defined to 6-digit accuracy, ^9.22350+ 4.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗

TAXI Direct-to-Disk Interface Demultiplexes Proprietarily Formatted Data

The TAXI Direct-to-Disk interface is a special-purpose interface circuit for demultiplexing of data from a Racal Storeplex (or equivalent) multichannel recorder onto one or more hard disks that reside in, and/or are controlled by, a personal computer (PC). (The name TAXI as used here is derived from the acronym TAXI, which signifies transparent asynchronous transceiver interface.) The TAXI Direct-to-Disk interface was developed for original use in capturing data from instrumentation on a test stand in a NASA rocket-testing facility. The control, data-recording, and data-postprocessing equipment of the facility are located in a control room at a safe distance from the test stand. Heretofore, the transfer of data from the instrumentation to the postprocessing equipment has entailed post-test downloading via software, requiring many hours to days of post-test reduction before the data could be viewed in a channelized format. The installation of the TAXI Direct-to-Disk interface, in conjunction with other modifications, causes the transfer of data to take place in real time, so that the data are immediately available for review during or after the test. The instrumentation is connected to the input terminals of the signal-processing unit of multichannel recorder by standard coaxial cables. The coaxial output of the signal processing unit is converted to fiber-optic output by means of a commercial coaxial-cable/fiber-optic converter (that is, a fiber-optic transceiver) designed specifically for this application. The fiber-optic link carries the data signals to an identical fiber-optic transceiver in the control room. On the way to the TAXI Direct-to-Disk interface that is the focus of this article, the data signals are processed through a companion special purpose circuit denoted by the similar name parallel TAXI interface.

Newnan, Bruce G.↗

LANDSAT-D data format control book. Volume 6, appendix A: Partially processed thematic mapper High Density Tape (HDT-AT)

One of the outputs of the data management system being developed to provide a variety of standard image products from the thematic mapper and the multispectral band scanners on LANDSAT 4, is the partially processed TM data (radiometric corrections applied and geometric correction matrices for two projections appended) which is recorded on a 28-track high density tape. Specifications are presented for the format of the recorded data as well as for the time code and the major and minor frames of the tape. Major frame types, formats, and field definitions are included.

Jai, A.↗

General-Purpose Data-Formatting Input/Output System

Multiplexable input/output (I/O) system developed as interface between host computer and real-time, fixed-base simulator cockpit. Unit designed to be general-purpose interface and operated through virtually any 8- or 16-bit, transistor/transistor-logic-level, parallel-I/O port with or without handshaking. Accepts byte-coded data in form of data blocks from host computer and routes data to various system I/O modules like discrete outputs, lamp drivers, and seven-segment-display drivers. Formats and routes data from input modules back to host computer. Other modules designed to drive alphanumeric displays and communications interfaces and to serve as analog-to-digital and digital-to-analog converter modules.

Busquets, Anthony M.↗

LANDSAT-D data format control book. Volume 6, appendix K: Unprocessed multispectral scanner high density tape (HDT-RM/HDT-GM)

Unprocessed MSS data which is recorded on HDT-RM (a 28 track, high density tape) and on HDT-GM (a 14 track, nonbias recorded, high density tape) are inputs for the LANDSAT 4 data management system. All MSS data initially recorded on HDT-GM are copied to HDT-RM prior to processing. This specification establishes the requirements for the format of the LANDSAT D HDT-RM/HDT-GM.

Andersen, K. E.↗

Variable length data formats

The purpose of this paper is to discuss a number of variable length floating point and integer formats and to give the various advantages and disadvantages of their use. Often it is known in advance that a given integer will not exceed a certain magnitude or that a particular floating point number is accurate to only 'n' places of accuracy. Faced with this, it is good engineering to choose variable length floating point and integer formats which require the least amount of hardware or the minimum amount of software or which have some other dominant advantage. The formats discussed have the advantage that length change algorithms are invariant with respect to data types (unsigned, signed, floating point, integers, and complex numbers). The STARAN associative array processor, which uses a completely variable fixed point and floating point formats, is described.

Brakefield, J. C.↗

LANDSAT-D data format control book. Volume 6: (Products)

Four basic product types are generated from the raw thematic mapper (TM) and multispectral scanner (MSS) payload data by the NASA GSFC LANDSAT 4 data management system: (1) unprocessed data (raw sensor data); (2) partially processed data, which consists of radiometrically corrected sensor data with geometric correction information appended; (3) fully processed data, which consists of radiometrically and geometrically corrected sensor data; and (4) inventory data which consists of summary information about product types 2 and 3. High density digital recorder formatting and the radiometric correction process are described. Geometric correction information is included.

Kabat, F.↗

SG50 Data-format Requirement Document for an Automatically Readable, Comprehensive and Curated Experimental Reaction Database MEDUSA

This report constitutes the requirement document that guides the development of the experimental reaction database, MEDUSAL (Machine-readable Experimental Data User App & Library), created by OECD/NEA/WPEC SubGroup 50. Experimental reaction data are usually stored in the EXFOR library in EXFOR format. With MEDUSAL, the WPEC sub-group 50 wants to go beyond the EXFOR format and database to generate a library that is (a) automatically readable, (b) comprehensive, and (c) curated.

Nuclear Criticality Safety Program (NCSP)↗

SG50 Data-format Specifications Document for the Automatically Readable, Comprehensive, and Curated Experimental Reaction Database MEDUSAL

The aim of this document is to lay out a first draft of the specifications for the MEDUSAL database (Machine-readable Experimental Data User App & Library) that is being described by OECD/NEA/WPEC SG-50. The EXFOR database (Otuka et al., 2014) has a format that is based on code-value pairs, and a significant portion of the information in the EXFOR entry is contained in free text sections. Several high-level requirements for the MEDUSAL database, as laid out in the Use Cases and Requirements Working Paper (citation), relate to the definition of the specifications

Nuclear Criticality Safety Program (NCSP)↗

LANDSAT-D data format control book. Volume 5: (Payload)

The LANDSAT-D flight segment payload is the thematic mapper and the multispectral scanner. Narrative and visual descriptions of the LANDSAT-D payload data handling hardware and data flow paths from the sensing instruments through to the GSFC LANDSAT-D data management system are provided. Key subsystems are examined.

Andrew, H.↗

Hierarchical Data Formats (HDF) Update

In this presentation, we will talk about the latest releases of HDF4 and HDF5 software and tools, new features available in HDF5, and roadmap for the HDF software. We will also solicit feedback from the users of HDF data and HDF application developers on new features and new tools. The talk will cover: Difference between 1.8 and 1.10 releases and how and when to move to the latest release Features of the recent HDF5 1.8.19, 1.10.1 and HDF 4.2.13 Overview of HDF View 3.0 and other enhancements to tools Supported compilers and systems Open discussion of new requirements and wish list of the HDF features Compression library for interoperability with h5py and Pandas and better floating-point data compression.

HDFView↗

International Satellite Cloud Climatology Project (ISCCP) Stage D1 3-Hourly Cloud Product - Revised Algorithm in Hierarchical Data Format (ISCCP_D1)

Since 1983 an international group of institutions has collected and analyzed satellite radiance measurements from up to five geostationary and two polar orbiting satellites to infer the global distribution of cloud properties and their diurnal, seasonal and interannual variations. The primary focus of the first phase of the project (1983-1995) was the elucidation of the role of clouds in the radiation budget (top of the atmosphere and surface). In the second phase of the project (1995 onwards) the analysis also concerns improving understanding of clouds in the global hydrological cycle. [Location=TROPOSPHERE] [Temporal_Coverage: Start_Date=1983-07-01; Stop_Date=] [Spatial_Coverage: Southernmost_Latitude=-90; Northernmost_Latitude=90; Westernmost_Longitude=-180; Easternmost_Longitude=180] [Data_Resolution: Latitude_Resolution=280 Km; Longitude_Resolution=280 Km; Temporal_Resolution=3 Hourly].

CLOUD LIQUID WATER PATH↗

International Satellite Cloud Climatology Project (ISCCP) Stage D2 Monthly Cloud Product - Revised Algorithm in Hierarchical Data Format (ISCCP_D2)

Since 1983 an international group of institutions has collected and analyzed satellite radiance measurements from up to five geostationary and two polar orbiting satellites to infer the global distribution of cloud properties and their diurnal, seasonal and interannual variations. The primary focus of the first phase of the project (1983-1995) was the elucidation of the role of clouds in the radiation budget (top of the atmosphere and surface). In the second phase of the project (1995 onwards) the analysis also concerns improving understanding of clouds in the global hydrological cycle. [Location=TROPOSPHERE] [Temporal_Coverage: Start_Date=1983-07-01; Stop_Date=] [Spatial_Coverage: Southernmost_Latitude=-90; Northernmost_Latitude=90; Westernmost_Longitude=-180; Easternmost_Longitude=180] [Data_Resolution: Latitude_Resolution=280 Km; Longitude_Resolution=280 Km; Temporal_Resolution=Monthly].

CLOUD TOP PRESSURE↗

International Satellite Cloud Climatology Project (ISCCP) Stage D2 Monthly Cloud Product - Revised Algorithm in Native (NAT) Data Format (ISCCP_D2_NAT)

Since 1983 an international group of institutions has collected and analyzed satellite radiance measurements from up to five geostationary and two polar orbiting satellites to infer the global distribution of cloud properties and their diurnal, seasonal and interannual variations. The primary focus of the first phase of the project (1983-1995) was the elucidation of the role of clouds in the radiation budget (top of the atmosphere and surface). In the second phase of the project (1995 onwards) the analysis also concerns improving understanding of clouds in the global hydrological cycle. [Location=TROPOSPHERE] [Temporal_Coverage: Start_Date=1983-07-01; Stop_Date=] [Spatial_Coverage: Southernmost_Latitude=-90; Northernmost_Latitude=90; Westernmost_Longitude=-180; Easternmost_Longitude=180] [Data_Resolution: Latitude_Resolution=280 Km; Longitude_Resolution=280 Km; Temporal_Resolution=Monthly].

CLOUD OPTICAL THICKNESS↗

Vehicle Design Data Format and Process for a Complete TARIS and OLTARIS Radiation Analysis for Designers and Engineers

Protecting astronauts from space radiation is a complex task when it comes to modeling and simulation. This document shows what information is needed from a spacecraft designer using CAD (Computer-Assisted Design) at each phase of the design to enable the engineers to evaluate the design phase against space radiation limits to determine the suitability of the design for space flight. The current personal exposure limits are listed in NASA STD-3001. A proxy to determine the REID (Radiation Exposure Induced Death) in NASA STD-3001 is the whole body effective dose equivalent (E or effective dose). For short-term tissue effects, organ-averaged gray equivalent (G (sub T)) is used. The TARIS (Tool for the Assessment of Radiation In Space - for LaRC (Langley Research Center) engineers) and OLTARIS (On-Line TARIS) - for designers) systems are used to generate these response functions. The E can use ICRP60 or NASA Q-values. A possible space radiation design basis environment for short-term tissue effects is described and used in all analyses. A single space vehicle was designed with three astronaut configurations and two of those configurations were used in a storm shelter thickness perturbation analysis. Conversion of the data from the CAD model to input necessary for TARIS and OLTARIS is also discussed in detail with relevant examples.

Singleterry, Robert C.↗