You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

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:

  1. station size, common metadata
  2. station list with station metadata
  3. 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 LF format contains unnecessarily repeated common metadata in the station list section.

LFHFBB
i4 number of stations  
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 timeseries in array dimensions:
timestep, station, component (9)
f4 timeseries in array dimensions:
station, timestep, component (3)
f4 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
  • No labels