Metronix Geophysics as developed a new folder structure and file system for their data that tries to mimic MTH5 making the translation relatively straight forward. More information can be found at Metronix Geophysics HDF5.
The data comes in pairs for each channel of a run:
.atssfiles, which are simply the data that can be easily read into a numpy array.jsonmetadata file with the same file basename as the.atssfile
The data are then organized in a folder system that looks like:
Northern Mining
├── config
├── db
├── dump
├── edi
├── filters
├── jle
├── jobs
├── log
├── meta
│ └── Sarıçam
│ ├── run_001
│ │ ├── 084_2009-08-20_13-22-00_2009-08-21_07-00-00_R001_128H.xml
│ │ ├── 084_ADU-07e_C000_TEx_128Hz.json
│ │ ├── 084_ADU-07e_C001_TEy_128Hz.json
│ │ ├── 084_ADU-07e_C002_THx_128Hz.json
│ │ ├── 084_ADU-07e_C003_THy_128Hz.json
│ │ └── 084_ADU-07e_C004_THz_128Hz.json
│ └── run_002
│ ├── 084_2009-08-21_07-01-00_2009-08-21_07-06-00_R001_2048H.xml
│ ├── 084_ADU-07e_C000_TEx_2048Hz.json
│ ├── 084_ADU-07e_C001_TEy_2048Hz.json
│ ├── 084_ADU-07e_C002_THx_2048Hz.json
│ ├── 084_ADU-07e_C003_THy_2048Hz.json
│ └── 084_ADU-07e_C004_THz_2048Hz.json
├── processings
├── reports
│ └── old_cal
│ ├── FGS03E_000_master.txt
│ ├── MFS05141.TXT
│ ├── MFS06024.TXT
│ ├── MFS06026.TXT
│ ├── MFS06032.TXT
│ ├── MFS06E_000_master.txt
│ ├── MFS07E_000_master.txt
│ └── MFS10e0021.TXT
├── shell
│ ├── mkallproc.sh
│ ├── plot_ascii_table_edi.sh
│ └── procall.sh
├── stations
│ └── Sarıçam
│ ├── run_001
│ │ ├── 084_ADU-07e_C000_TEx_128Hz.atss
│ │ ├── 084_ADU-07e_C000_TEx_128Hz.json
│ │ ├── 084_ADU-07e_C001_TEy_128Hz.atss
│ │ ├── 084_ADU-07e_C001_TEy_128Hz.json
│ │ ├── 084_ADU-07e_C002_THx_128Hz.atss
│ │ ├── 084_ADU-07e_C002_THx_128Hz.json
│ │ ├── 084_ADU-07e_C003_THy_128Hz.atss
│ │ ├── 084_ADU-07e_C003_THy_128Hz.json
│ │ ├── 084_ADU-07e_C004_THz_128Hz.atss
│ │ └── 084_ADU-07e_C004_THz_128Hz.json
│ └── run_002
│ ├── 084_ADU-07e_C000_TEx_2048Hz.atss
│ ├── 084_ADU-07e_C000_TEx_2048Hz.json
│ ├── 084_ADU-07e_C001_TEy_2048Hz.atss
│ ├── 084_ADU-07e_C001_TEy_2048Hz.json
│ ├── 084_ADU-07e_C002_THx_2048Hz.atss
│ ├── 084_ADU-07e_C002_THx_2048Hz.json
│ ├── 084_ADU-07e_C003_THy_2048Hz.atss
│ ├── 084_ADU-07e_C003_THy_2048Hz.json
│ ├── 084_ADU-07e_C004_THz_2048Hz.atss
│ └── 084_ADU-07e_C004_THz_2048Hz.json
└── tmpMetadata¶
Metadata is basic, most of the important values are in the .json files. ID’s for run, station, survey are taken from the file structure and folder names.
Filters¶
This is still a work in progress, but the sensor response filters are in the .json files and are included in the MTH5. What is still unclear is any instrument response that may need to be included.
There is no filter for dipole length as the instrument calculates that internally and stores electric channels in mV/km.
Example Data¶
You can find example data here. Download one of the folders, small_example/Northern_Mining is what is used in this example. Just change the file path to your local machine.
Here we are going to create a MTH5 from all the sample rates provided. Note all sample rates are given in units of samples per second.
We are also going to keep the run names as they are in the folder structure. If you want to change that behavior and name the run by sample rate you can change the keyword run_name_zeros to an integer. By doing this the run ID will change from run_001 to sr{sample_rate}_{1:0{run_name_zeros}}, for example a sample rate of 32 will become sr32_001.
from mth5.clients import MakeMTH5m = MakeMTH5.from_metronix(
r"/mth5_files/small_example/Northern_Mining",
sample_rates=[2048, 512, 128, 32, 2, 1./2, 1./8],
mth5_filename="from_metronix_test.h5",
run_name_zeros=0)