Search NASA⌕ Search

SEARCH · Search NASA

Results for “file format”

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

Interoperability format translation and transformation between IFC architectural design file and simulation file formats

Automatically translating a building architecture file format (Industry Foundation Class) to a simulation file, in one aspect, may extract data and metadata used by a target simulation tool from a building architecture file. Interoperability data objects may be created and the extracted data is stored in the interoperability data objects. A model translation procedure may be prepared to identify a mapping from a Model View Definition to a translation and transformation function. The extracted data may be transformed using the data stored in the interoperability data objects, an input Model View Definition template, and the translation and transformation function to convert the extracted data to correct geometric values needed for a target simulation file format used by the target simulation tool. The simulation file in the target simulation file format may be generated.

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗

Interoperability format translation and transformation between IFC architectural design file and simulation file formats

Automatically translating a building architecture file format (Industry Foundation Class) to a simulation file, in one aspect, may extract data and metadata used by a target simulation tool from a building architecture file. Interoperability data objects may be created and the extracted data is stored in the interoperability data objects. A model translation procedure may be prepared to identify a mapping from a Model View Definition to a translation and transformation function. The extracted data may be transformed using the data stored in the interoperability data objects, an input Model View Definition template, and the translation and transformation function to convert the extracted data to correct geometric values needed for a target simulation file format used by the target simulation tool. The simulation file in the target simulation file format may be generated.

97 MATHEMATICS AND COMPUTING↗

NUM-DAT File Format Specification: Used in M-9 Gun Experiment Data Archiving

The M-9 Shock and Detonation Physics group executes experiments on gun and explosive platforms with large numbers of oscilloscopes used for data acquisition. The data acquisition from these oscilloscopes was automated many years ago using a custom piece of software called RunDig . The default save format from this software is a custom structure referred to as "NUM-DAT" format. This file format includes a text ".DAT" file which is a header file used to interpret the binary ".NUM" file which contains the oscilloscope data. The data save format was originally developed by John Vorthman and has been in use by M-9 personnel for over 20 years. This data format has been used for archiving data from experiments performed by M-9 personnel at TA-40, TA-39, and the TA-55 Impact Test Facility. Numerous custom analysis and visualization programs have also been developed, and continue to be used, that utilize this data format. This document describes the NUM-DAT format and provides code examples for reading the format and converting it to other formats.

47 OTHER INSTRUMENTATION↗

PCF File Format.

PCF files are binary files designed to contain gamma spectra and neutron count rates from radiation sensors. It is the native format for the GAmma Detector Response and Analysis Software (GADRAS) package [1]. It can contain multiple spectra and information about each spectrum such as energy calibration. This document outlines the format of the file that would allow one to write a computer program to parse and write such files.

98 NUCLEAR DISARMAMENT, SAFEGUARDS, AND PHYSICAL P↗

PCF File Format

PCF files are binary files designed to contain gamma spectra and neutron count rates from radiation sensors. It is the native format for the GAmma Detector Response and Analysis Software (GADRAS) package. It can contain multiple spectra and information about each spectrum such as energy calibration. This document outlines the format of the file that would allow one to write a computer program to parse and write such files.

61 RADIATION PROTECTION AND DOSIMETRY↗

Computer-aided design file format for additive manufacturing and methods of file generation

A tessellated output file format describing a computer-aided design (CAD) model including a plurality of vertices, a plurality of curves, a plurality of surfaces, and at least one volume, the tessellated output file format comprising base polygon data, a vertex metadata container, a curve metadata container, and a surface metadata container. The base polygon data defines the CAD model for additive manufacturing and includes a plurality of connected polygons, each polygon including a plurality of nodes, a plurality of edges, and a face. The vertex metadata container includes a listing of CAD model vertices and one polygon node associated with each CAD model vertex. The curve metadata container includes a listing of CAD model curves and at least one polygon edge associated with each CAD model curve. The surface metadata container includes a listing of CAD model surfaces and at least one polygon face associated with each CAD model surface.

Vernon, Gregory John↗

File format for normalizing radiological concentration exposure rate and dose rate data for the effects of radioactive decay and weathering processes

This report specifies the electronic file format that was agreed upon to be used as the file format for normalized radiological data produced by the software tool developed under this TI project. The NA-84 Technology Integration (TI) Program project (SNL17-CM-635, Normalizing Radiological Data for Analysis and Integration into Models) investigators held a teleconference on December 7, 2017 to discuss the tasks to be completed under the TI program project. During this teleconference, the TI project investigators determined that the comma-separated values (CSV) file format is the most suitable file format for the normalized radiological data that will be outputted from the normalizing tool developed under this TI project. The CSV file format was selected because it provides the requisite flexibility to manage different types of radiological data (i.e., activity concentration, exposure rate, dose rate) from other sources [e.g., Radiological Assessment and Monitoring System (RAMS), Aerial Measuring System (AMS), Monitoring and Sampling). The CSV file format also is suitable for the file format of the normalized radiological data because this normalized data can then be ingested by other software [e.g., RAMS, Visual Sampling Plan (VSP)] used by the NA-84’s Consequence Management Program.

97 MATHEMATICS AND COMPUTING↗

...And Eat it Too: High Read Performance in Write-Optimized HPC I/O Middleware File Formats

As HPC applications run on increasingly high process counts on larger and larger machines, both the frequency of checkpoints needed for fault tolerance and the resolution and size of Data Analysis Dumps are expected to increase proportionally. In order to maintain an acceptable ratio of time spent performing useful computation work to time spent performing I/O, write bandwidth to the underlying storage system must increase proportionally to this increase in the checkpoint and computation size. Unfortunately, popular scientific self-describing file formats such as netCDF and HDF5 are designed with a focus on portability and flexibility. Extra care and careful crafting of the output structure and API calls is required to optimize for write performance using these APIs. To provide sufficient write bandwidth to continue to support the demands of scientific applications, the HPC community has developed a number of I/O middleware layers, that structure output into write-optimized file formats. However, the obvious concern with any write optimized file format would be a corresponding penalty on reads. In the log-structured filesystem, for example, a file generated by random writes could be written efficiently, but reading the file back sequentially later would result in very poor performance. Simulation results require efficient read-back for visualization and analytics, and though most checkpoint files are never used, the efficiency of a restart is very important in the face of inevitable failures. The utility of write speed improving middleware would be greatly diminished if it sacrificed acceptable read performance. In this paper we examine the read performance of two write-optimized middleware layers on large parallel machines and compare it to reading data natively in popular file formats. The two I/O middleware layer examined in this paper are the Adaptable IO System (ADIOS), a library-based approach developed at Oak Ridge National Laboratory to provide a high-level IO API that can be used in place of netCDF or HDF5 to do much more aggressive write-behind and efficient reordering of data locations within the file; and the Parallel Log-structured Filesystem (PLFS), a stackable FUSE filesystem approach developed at Los Alamos National Laboratory that decouples concurrent writes to improve the speed of checkpoints. Since ADIOS is an I/O componentization that affords selection of different I/O methods at or during runtime, through a single API, users can have access to MPI-IO, Posix-IO, HDF5, netCDF, and staging methods. The ADIOS BP file format is a new log-file format that has a superset of the features of both HDF5 and netCDF, but is designed to be portable and flexible while being optimized for writing. PLFS, on the other hand, is mounted as a stackable filesystem on top of an existing parallel filesystem. Reads or writes to the PLFS filesystem are transparently translated into operations on per-process log files stored in the underlying parallel filesystem. Since PLFS performs this translation without application modification, users can write in HDF5, netCDF, or app-specific file formats and PLFS will store the writes in a set of efficiently written log-formatted files, while presenting the user with a logical 'flat' file on reads. Despite their different approaches, the commonality behind both of these middleware systems is that they both write to a log file format. As shown in previous publications, writes are fully optimized in both systems, sometimes resulting in 100x improvements over writing data in popular file formats. But as mentioned above, writing is only one part of the story. In this paper we examine the read performance of our middleware layers on large parallel machines and compare these to reading data either natively or from other popular file formats. We compare the reading performance in two different scenarios: (1) Reading back restarts from the same number of processors as wrote the data and (2) Reading back restart data from a different number of processors. We observe that not only can write-optimized I/O middleware be built to not penalize read speeds, but for important workloads, techniques that improve write performance can, perhaps counterintuitively, improve read speeds over reading from a contiguously organized file format. In the remainder of this paper, we investigate this further through case studies of PLFS and ADIOS on simulation checkpoint restarts.

99 GENERAL AND MISCELLANEOUS↗

The MELCOR Plot File Format

This work provides a detailed explanation of the MELCOR Plot File format. MELCOR is a fully integrated, engineering-level computer code that models the progression of severe accidents in light water reactor nuclear power plants, and it primarily exports its simulation data to a binary file in the Plot File format. This work documents the Plot File's overall structure and the data types of exported information. The process of interpreting and associating time series information with MELCOR's Plot Variables for complete time histories is also presented. The format and meaning of time-independent information, called Special information, is also discussed.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗

Portable File Format (PFF) specifications

Created at Sandia National Laboratories, the Portable File Format (PFF) allows binary data transfer across computer platforms. Although this capability is supported by many other formats, PFF files are still in use at Sandia, particularly in pulsed power research. This report provides detailed PFF specifications for accessing data without relying on legacy code.

97 MATHEMATICS AND COMPUTING↗

Photon-HDF5: an open file format for single-molecule fluorescence experiments using photon-counting detectors

We introduce Photon-HDF5, an open and efficient file format to simplify exchange and long term accessibility of data from single-molecule fluorescence experiments based on photon-counting detectors such as single-photon avalanche diode (SPAD), photomultiplier tube (PMT) or arrays of such detectors. The format is based on HDF5, a widely used platform- and language-independent hierarchical file format for which user-friendly viewers are available. Photon-HDF5 can store raw photon data (timestamp, channel number, etc) from any acquisition hardware, but also setup and sample description, information on provenance, authorship and other metadata, and is flexible enough to include any kind of custom data. The format specifications are hosted on a public website, which is open to contributions by the biophysics community. As an initial resource, the website provides code examples to read Photon-HDF5 files in several programming languages and a reference python library (phconvert), to create new Photon-HDF5 files and convert several existing file formats into Photon-HDF5. As a result, to encourage adoption by the academic and commercial communities, all software is released under the MIT open source license.

59 BASIC BIOLOGICAL SCIENCES↗

Historical NTS digitizer file format

The historical NTS *.dig data formal is not widely known. I document the proper *.dig file format. I include the MATLAB code used to read *.dig files with the historical data analysis software, "eXreme Las Vegas".

97 MATHEMATICS AND COMPUTING↗

Computer-aided design file format for additive manufacturing and methods of file generation

A method of generating a tessellated output file comprising receiving a computer-aided design (CAD) model file defining a CAD model including a plurality of vertices, a plurality of curves, a plurality of surfaces, and at least one volume; generating base polygon data defining the CAD model for additive manufacturing, the base polygon data including a plurality of connected polygons, each polygon including a plurality of nodes, a plurality of edges, and a face; generating data for a vertex metadata container including a listing of CAD model vertices and one polygon node associated with each CAD model vertex; generating data for a curve metadata container including a listing of CAD model curves and at least one polygon edge associated with each CAD model curve; and generating data for a surface metadata container including a listing of CAD model surfaces and at least one polygon face associated with each CAD model surface.

Vernon, Gregory John↗

CTN-004: Rubin Observatory Raw Data File Format

At the NSF-DOE Vera C. Rubin Observatory we write data from the LSSTCam and LATISS instruments using FITS format with one file written per detector. Here we discuss the layout of those FITS files and describe the FITS headers.

79 ASTRONOMY AND ASTROPHYSICS↗

Radiation portal monitor data file format for comprehensive background radiation monitoring

Radiation portal monitors (RPMs) are widely used at border security checkpoints to detect the presence of radioactive materials in people, vehicles, and cargo. Typically, RPM detection systems consist of two pillars equipped with gamma and neutron detectors. To improve detection efficiency, RPMs employ techniques such as a limited energy window, dynamic alarm thresholds, and lead shielding. However, without continuous monitoring of background radiation, signal interpretation can be compromised, because environmental factors and mechanical failures can cause fluctuations. Here, we introduce a daily file format that logs gamma background and neutron background radiation levels continuously over a 24 h period; this format is different from traditional formats that record data only when the RPM is active or occupied. The approach enables RPM operators and analysts to (1) identify and diagnose malfunctioning components, (2) adjust system settings to account for dynamic environmental factors, and (3) use the recorded data to characterize outer space phenomena. Continuous background reporting is essential for identifying issues such as faulty connections, voltage divider failures, and errors in background updates. Continuous background reporting also enables the detection of external influences, including nearby X-ray scanners, temperature fluctuations, rainfall, cosmic radiation, and lunar phase changes. These data files are designed to be easily evaluated and parsed using common tools, and a quick review by an expert is often sufficient for problem diagnosis. We anticipate that continuous background radiation monitoring and these new strategies will significantly improve the accuracy and reliability of RPM systems, reducing the rate of false alarms and enhancing overall system performance.

Background radiation monitoring↗

Sesame ASCII File Format Version 1.21

The intended audience for this document is a Sesame IO library developer or anyone trying to write or parse Sesame ASCII files with no regards to the meaning of the actual content. LA-UR-92-3407 “SESAME: The Los Alamos National Laboratory Equation Of States Database” is the current document for describing the data contained in Sesame Database. This document describes the physical format in Sesame’s ASCII files. It may have a little information about the data in these files. However, this data is only cursory. Historically Sesame ASCII files are fixed format based on old 80-character punch cards. A stack of punch cards is called a card deck. Card decks were read into a computer using card readers and the first version(s) of FORTRAN had fixed file formats. Sesame ASCII files originate from this. Each ASCII File Format file represents a card deck.

97 MATHEMATICS AND COMPUTING↗

Covariance Data File Formats for Whisper-1.0 & Whisper-1.1

Whisper is a statistical analysis package developed in 2014 to support nuclear criticality safety (NCS) validation. It uses the sensitivity profile data for an application as computed by MCNP6 along with covariance files for the nuclear data to determine a baseline upper-subcritical-limit (USL) for the application. Whisper version 1.0 was first developed and used at LANL in 2014. During 2015-2016, Whisper was updated to version 1.1 and is to be included with the upcoming release of MCNP6.2. This report describes the file formats used for the covariance data in both Whisper-1.0 and Whisper-1.1.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

A File Format and API for Dynamic Radar Cross Section Data

Often the Radar Cross-Section (RCS) of a target is incorrectly assumed to be a single number by those unfamiliar with electromagnetic scattering. In actuality, a target's RCS depends on many factors. These factors include radar signal frequency, radar observation angle, as well as target orientation. Another possible parameter (often not considered) is time. The RCS of targets may change over time due to movement, environmental changes, etc. In order to accurately represent the dynamic RCS of a target in a time-stepped analysis, the ability to interface with large RCS datasets efficiently is desired. To this end, a file format and API (written in C++) were developed and are described in this report.

42 ENGINEERING↗