ERTLab employs keywords (tags) to indicate subsets of a data
file and configuration information. In version one, the schedule file should
contain electrode and quadrapole information. Later versions will ultimately
permit this information to be input from different files or conversely other
information such as topography and mesh configuration may be recordable in the
schedule file. Each keyword starts with the # symbol. The comment character is
!. Any information placed between ! and the end of a file line is
ignored. Blank lines are also ignored.
Electrode format
The Electrode format requires an #elec_start keyword to
indicate the start of the electrode listing and an #elec_end
keyword to indicate the end of the list.
In absence of further tags, the electrodes are loaded, in the Inversion or
Forward modeling workspace, on the basis of the I/O format parameters specified
in the configuration settings list.
Electrodes input format can be included in the data file
by using the appropriate configuration tags. The configuration information
may include:
#elec_no_cable, a flag indicating the presence
of cable identifiers (1 present; -1 not present);
#elec_cable_col, column identifier for the cable group (cable
number);
#elec_id_col, column identifier for the electrode number;
#elec_x_col, column identifier for the electrode X location;
#elec_y_col, column identifier for the electrode Y
location;
#elec_z_col, column identifier for the electrode Z
location;
#elec_elev_col, column identifier for the electrode Z
terrain elevation;
#elec_type_col, column identifier for the type of electrode.
At a minimum columns must include #elec_cable_col or cable
number, #elec_id_col or electrode number, #elec_x_col or X location,
#elec_y_col and #elec_z_col for Y and Z locations.
Flag -1 stands for information not present.
If the electrode type is not specified in the input file, ERTLab will derive it
for each electrode. "Remote" flags will be attributed to the cables
having one or two electrodes. If the electrode z terrain
elevation is not specified in the input file, ERTLab will derive it for
each electrode.
The complete list of possible commands is documented in the example below:
!Electrodes input/output format
#elec_no_cable= 1
#elec_cable_col= 1
#elec_id_col= 2
#elec_x_col= 3
#elec_y_col= 4
#elec_z_col= 5
#elec_elev_col= 6
#elec_type_col= 7
#elec_start
1 1
1000 100
0 0 -2 !Remote surface
electrode
2
1 -1000 100
-5 0 -1 !Remote borehole
electrode
3
1 -100
100 0
0 2 !Five electrode surface cable
3
2 -50
100 0
0 2
3
3
0 100
0 0 2
3
4 50 100
0 0 2
3
5 100
100 0
0 2
4 1
0 100 -25
0 1 !Five electrode well
4 2
0 100 -20
0 1
4 3
0 100 -15
0 1
4
4
0 100 -10
0 1
4
5 0
100 -5
0 1
#elec_end
Data format
The Data format requires a #data_start keyword
to indicate the start of the data listing and a #data_end
keyword to indicate the end of the list.
In absence of further tags, quadrupoles and data are loaded, in the Inversion
or Forward modeling workspace, on the basis of the I/O format parameters
specified in the configuration settings list.
Data input format can be included in the data file by using the
appropriate configuration tags. The configuration information may include:
#data_id_col, column identifier for the quadrupole
number;
#data_a_cable_col, column identifier for the TX+ (A)
electrode cable number;
#data_a_elec_col, column identifier for the TX+ (A)
electrode id number;
#data_b_cable_col, column identifier for the TX- (B)
electrode cable number;
#data_b_elec_col, column identifier for the TX- (B)
electrode id number;
#data_m_cable_col, column identifier for the RX+ (M)
electrode cable number;
#data_m_elec_col, column identifier for the RX+ (M)
electrode id number;
#data_n_cable_col, column identifier for the RX- (N)
electrode cable number;
#data_n_elec_col, column identifier for the RX- (N)
electrode id number;
#data_res_col, column identifier for field data resistance
(V/I);
#data_ip_wind_col, column identifier for field data IP;
#data_std_res_col, column identifier for field data resistance
standard deviation;
#data_std_ip_col, column identifier for field data IP standard
deviation;
#data_calc_res_col, column identifier for calculated
resistance (V/I);
#data_calc_ip_col, column identifier for calculated IP;
#data_calc_std_res_col, column identifier for calculated
V/I standard deviation;
#data_calc_std_ip_col, column identifier for calculated
IP standard deviation;
#data_appres, flag for data in terms of resistance V/I (1) or
apparent resistivity (2);
#data_ip_scale, scale factor for IP data.
At a minimum columns must include the datapoint ID, the electrode ID's (cable
and electrode) for each of the four quadrapole electrodes (eight columns) and a
resistance.
Flag -1 stands for information not present.
The example below shows a possible structure for a resistance and IP dataset:<
br>
#data_id_col= 1
#data_a_cable_col= 2
#data_a_elec_col= 3
#data_b_cable_col= 4
#data_b_elec_col= 5
#data_m_cable_col= 6
#data_m_elec_col= 7
#data_n_cable_col= 8
#data_n_elec_col= 9
#data_res_col= 10
#data_ip_wind_col= 11
#data_std_res_col= -1
#data_std_ip_col= -1
#data_calc_res_col= -1
#data_calc_ip_col= -1
#data_calc_std_res_col= -1
#data_calc_std_ip_col= -1
#data_appres= 1
#data_ip_scale= 1000.0
#DATA_Start
1 1 1
4 1 4
2 2 1
.1115 12.2
2 1 1
4 2 4
3 2 1
.1122 1.5
3 1 1
4 3 4
4 2 1
.1760 7.6
4 1 1
4 4 4
5 2 1
.2114 4.4
5 3 1
3 2 3
3 3 4
-.113 10.1
6 3 2
3 3 3
4 3 5
-.122 44.7
7 3 1
3 3 3
2 3 4
.1175 16.1
8 3 2
3 4 3
3 3 5
.1625 3.3
#DATA_End
|