This page will have a summary of the file formats that we use in the simulations and workflow.
LF/HF/BB binary format
All formats follow a style derived from the LF seis format produced by EMOD3D:
- station size, common metadata
- station list with station metadata
- timeseries
Numbers are 4 bytes in length and may be little or big endian. You can see or use the existing interfaces that also take care of endianness at github:ucgmsim/qcore/qcore/timeseries.py::LFSeis, HFSeis, BBSeis.
File size can be derived knowing the format and the number of stations, and shape of time-series (all necessary values are at the beginning of the file).
The second (station) section is repeated for each station.
The LF format contains unnecessarily repeated common metadata in the station list section.
| LF | HF | BB |
|---|---|---|
| i4 number of stations | i4 number of stations | i4 number of stations i4 number of timesteps f4 duration of timeseries f4 timestep of timeseries f4 start time of timeseries s256 LF directory path used s256 LF VM directory path used s256 HF file path used possibly add vsite file path used here? |
| i4 index of station in input file i4 x gridpoint of station i4 y gridpoint of station i4 z gridpoint of station i4 simulation number of timesteps f4 simulation timestep f4 simulation grid spacing f4 simulation grid rotation f4 latitude of station f4 longitude of station s8 name of station | f4 longitude of station f4 latitude of station s8 name of station f4 epicentre distance to station f4 vs30 at station | f4 longitude of station f4 latitude of station s8 name of station i4 x gridpoint of station i4 y gridpoint of station i4 z gridpoint of station f4 epicentre distance to station f4 HF vs30 f4 LF vs30 f4 BB vs30 |
| f4 velocity timeseries in array dimensions: timestep, station, component (9) | f4 acceleration timeseries in array dimensions: station, timestep, component (3) | f4 acceleration timeseries in array dimensions: station, timestep, component (3) |
Intensity Measure calculation
The IM calculation code will produce a number of text files (decided as of 25/05/2018). We will summarize them in the following.
Intensity measure files
There are two types of IM files: per station and aggregate. The per station one has the following format:
component, IM_1, IM_2, ...., IM_N
Note: The per station file does not have the station name, as it is the file name.
The aggregate one has all the stations on a single place:
station, component, IM_1, IM_2, ...., IM_N
Rrup file
The file format for this is:
station, lat, lon, rrup, rjbs, rx
Note: we don't have rx calculations yet, so we may dump an invalid value just to conform with the format.
Metadata file
So far the requirements indicate that we need:
identifier, rupture, type, date