Tipper

This object can be used to store tipper (ZTEM) surveys - a natural-source geophysical method. Data are provided in the frequency-domain as point source measurements of tipper data.

The following example shows how to generate a tipper survey with associated data stored in geoh5 format and accessible from Geoscience ANALYST.

mtSurvey

[1]:
import numpy as np

from geoh5py.objects import TipperBaseStations, TipperReceivers
from geoh5py.workspace import Workspace


# Create a new project
workspace = Workspace("my_project.geoh5")

# Define the pole locations
n_stations = 64
n_lines = 2
x_loc, y_loc = np.meshgrid(
    np.linspace(0, 60, n_stations), np.linspace(-20, 20.0, n_lines)
)
vertices = np.c_[x_loc.ravel(), y_loc.ravel(), np.zeros_like(x_loc).ravel()]

# Assign a line ID to the poles (vertices)
parts = np.kron(np.arange(n_lines), np.ones(n_stations)).astype("int")

# Create the survey from vertices
receivers = TipperReceivers.create(workspace, vertices=vertices, parts=parts)
base = TipperBaseStations.create(workspace, vertices=vertices)

We have so far created two seperate entities, one for the receiver locations and another for the base station(s). In order to finalize the survey, the association must be made between the two entities:

[2]:
receivers.base_station = base

or equivalently

[3]:
base.receivers = receivers

Only one of the two options above is needed.

Metadata

Along with the TipperReceivers, the metadata contains all the necessary information to define the geophysical experiment.

[4]:
receivers.metadata
[4]:
{'EM Dataset': {'Base stations': UUID('7391c5ff-aa34-496c-9950-3e7da2dddbe2'),
  'Channels': [],
  'Input type': 'Rx and base stations',
  'Property groups': [],
  'Receivers': UUID('e6cc82b3-3198-442e-bf7c-6ba761e1f37f'),
  'Survey type': 'ZTEM',
  'Unit': 'Hertz (Hz)'}}

Channels

List of frequencies at which the data are provided.

[5]:
receivers.channels = [30.0, 45.0, 90.0, 180.0, 360.0, 720.0]

Input type

Generic label used in the geoh5 standard for all EM survey entities. Restricted to Rx and base station in the case of a tipper survey.

Property groups

List of PropertyGroups defining the various data components (e.g. Txz (real), Tyz (imag), …). It is not required to supply all components of the impedence tensor, but it is expected that each component contains a list of data channels of length and in the same order as the Channels (one Data per frequency).

The class method add_components_data can help users add data from nested dictionaries. Below is an example using four components:

[6]:
# Arbitrary data generator using sine functions
def data_fun(c, f):
    return (c + 1.0) * (f + 1.0) * np.sin(f * np.pi * (x_loc * y_loc).ravel() / 400.0)


# Create a nested dictionary of component and frequency data.
data = {
    component: {
        f"{component}_{freq}": {"values": data_fun(cc, ff)}
        for ff, freq in enumerate(receivers.channels)
    }
    for cc, component in enumerate(
        [
            "Txz (real)",
            "Txz (imaginary)",
            "Tyz (real)",
            "Tyz (imaginary)",
        ]
    )
}

receivers.add_components_data(data)
[6]:
[<geoh5py.groups.property_group.PropertyGroup at 0x7f7ac9f893f0>,
 <geoh5py.groups.property_group.PropertyGroup at 0x7f7ae5c11900>,
 <geoh5py.groups.property_group.PropertyGroup at 0x7f7ac9ad64d0>,
 <geoh5py.groups.property_group.PropertyGroup at 0x7f7ac9ad6ce0>]

Metadata are updated immediately to reflect the addition of components:

[7]:
receivers.metadata
[7]:
{'EM Dataset': {'Base stations': UUID('7391c5ff-aa34-496c-9950-3e7da2dddbe2'),
  'Channels': [30.0, 45.0, 90.0, 180.0, 360.0, 720.0],
  'Input type': 'Rx and base stations',
  'Property groups': ['Txz (real)',
   'Txz (imaginary)',
   'Tyz (real)',
   'Tyz (imaginary)'],
  'Receivers': UUID('e6cc82b3-3198-442e-bf7c-6ba761e1f37f'),
  'Survey type': 'ZTEM',
  'Unit': 'Hertz (Hz)'}}

Data channels associated with each component can be quickly accessed through the BaseEMSurvey.components property:

[8]:
receivers.components
[8]:
{'Txz (real)': [<geoh5py.data.float_data.FloatData at 0x7f7ac9ad6860>,
  <geoh5py.data.float_data.FloatData at 0x7f7ae5c32950>,
  <geoh5py.data.float_data.FloatData at 0x7f7ac9fe3bb0>,
  <geoh5py.data.float_data.FloatData at 0x7f7ae5c30e50>,
  <geoh5py.data.float_data.FloatData at 0x7f7ae5c33a60>,
  <geoh5py.data.float_data.FloatData at 0x7f7ac9ad68c0>],
 'Txz (imaginary)': [<geoh5py.data.float_data.FloatData at 0x7f7ac9ad6dd0>,
  <geoh5py.data.float_data.FloatData at 0x7f7ac9ad6e90>,
  <geoh5py.data.float_data.FloatData at 0x7f7ac9ad6a40>,
  <geoh5py.data.float_data.FloatData at 0x7f7ac9ad6fe0>,
  <geoh5py.data.float_data.FloatData at 0x7f7ac9ad7160>,
  <geoh5py.data.float_data.FloatData at 0x7f7ac9ad72b0>],
 'Tyz (real)': [<geoh5py.data.float_data.FloatData at 0x7f7ac9ad7550>,
  <geoh5py.data.float_data.FloatData at 0x7f7ac9ad6290>,
  <geoh5py.data.float_data.FloatData at 0x7f7ac9ad7070>,
  <geoh5py.data.float_data.FloatData at 0x7f7ac9ad76a0>,
  <geoh5py.data.float_data.FloatData at 0x7f7ac9ad77f0>,
  <geoh5py.data.float_data.FloatData at 0x7f7ac9ad79d0>],
 'Tyz (imaginary)': [<geoh5py.data.float_data.FloatData at 0x7f7ac9ad6d10>,
  <geoh5py.data.float_data.FloatData at 0x7f7ac9ad6320>,
  <geoh5py.data.float_data.FloatData at 0x7f7ac9700400>,
  <geoh5py.data.float_data.FloatData at 0x7f7ac97004c0>,
  <geoh5py.data.float_data.FloatData at 0x7f7ac9700670>,
  <geoh5py.data.float_data.FloatData at 0x7f7ac9700790>]}

Receivers

Generic label used in the geoh5 standard for EM survey to identify the TipperReceivers entity.

Base stations

Generic label used in the geoh5 standard for EM survey to identify the TipperBaseStations entity.

Survey type

Label identifier for ZTEM survey type.

Unit

Units for frequency sampling of the data: Hertz (Hz), KiloHertz (kHz), MegaHertz (MHz) or Gigahertz (GHz).

[9]:
workspace.finalize()