In order to simulate geophysical data from a physical property model, we need three things: a computational mesh, a discretization of the model within that mesh and a means to simulate the data. Plate simulation relies on discretize for octree mesh creation, and SimPEG for finite volume based forward modeling. Plate simulation includes a module for generating a simple two-layer model with embedded plate anomalies within octree meshes. In this section, we will discuss all three of these components, their interface exposed by the ui.json file, and the storage of results.
.. toctree:: :maxdepth: 3
In order to accurately simulate our earth model, we need a mesh that is refined in key areas, while being coarse enough elsewhere to efficiently simulate data. The plate simulation package includes refinements at the earth-air interface, the transmitter and receiver sites and on the surface of plates.
The meshing can be controlled by options exposed in the ui.json. Those options are significantly reduced compared with the octree creation from grid-app since we have tailored many of the parameters to suit the needs of plate simulation.
The plate simulation package includes a module for generating plate(s) embedded in a two-layer Earth model within octree meshes. There are many permutations of this simple geological scenario leading to a complex interface. To simplify things, we have broken the discussion into two sub-sections: background (basement and overburden) and plates.
All model values within plate-simulation are to be provided in ohm-metres. The basement resistivity is actually closer to a halfspace in the sense that it fills the model anywhere outside of the overburden and plate. So the basement resistivity should be chosen as an effective resistivity for the whole geological section. This should be quite reasonable for most applications where the differences in resistivity between layers is much smaller than the difference between overburden and any anomalous bodies (plates).
The overburden is discretized by the resistivity and thickness of the layer. The thickness is referenced to the earth-air interface and extends into the earth by the amount specified in the thickness parameter.
In this section we will discuss the various plate options available through the ui.json and their impact on the resulting discretized model.
The first set of options allows the user to specify the number of plates and their spacing.
For all choices of n>1, the plates will be evenly spaced at the requested
spacing and will share the same resistivity, size and orientation.
The plate resistivity is expected to be entered in ohm-metres.
The size of the plate is given as a 'thickness', 'strike length', and 'dip length'.
The image below shows a dipping plate with annotations showing the size parameters for that particular plate.
A dipping plate striking northeast with annotations for its thickness, strike length and dip length.
The orientation of the plate is provided in terms of a dip and dip direction. The dip is defined as the angle between the horizontal projection of the plate normal and the plate tangent sharing the same origin. The dip direction is measured between the horizontal projection of the plate normal and the North arrow. See the image below for a visual representation of these angles.
Plate orientation options. Plate orientation is given as a dip and dip direction. The dip (b) is defined as the angle between the horizontal the projection of the plate normal (n') and the plate tangent sharing the same origin (t). The dip direction (a) is the angle measured between the horizontal projection of the plate normal (n') and due north (N).
The location of the plate can be provided in both relative and absolute terms.
The position parameters are given as an easting, northing, and elevation. If the
relative locations checkbox is chosen, then the easting and northing will be
relative to the center of the survey and the elevation will be relative to one of
the available references. The elevation may either be referenced to the earth-air
interface or the overburden provided by the Depth reference dropdown. Either of
these choice can be relative to the minimum, maximum, or mean of the points making
up the reference surface as given by the Reference type dropdown. In all of these
cases the distance provided will act as a depth below the reference to the top of
plate in the z negative down convention. If the relative locations checkbox is not
chosen, then the easting, northing, and elevation is simply the location of the
center of the plate.
Plate location options in relative mode. Notice the Elevation is given as
negative to ensure the top of the plate is below the selected min of the
overburden.
The simulation parameters control the forward modeling of the plate model discretized within the octree mesh. Rather than exposing the parameters within the plate simulation interface all over again, we simply allow the user to select an existing forward modelling SimPEG group. It is expected that the user will have already edited those options and provided at least a topography and survey object as well as selected one or more components to simulate. The user may also provide a name to the new SimPEG group that will be used to store the results.
Selecting the initialized forward modelling SimPEG group and naming the group that will store the plate simulation results.
The required SimPEG group can be created within Geoscience ANALYST through the
Geophysics menu under SimPEG Python Interface entry.
Once created, the options can be edited by right-clicking the group and choosing the 'Edit Options' entry.
Since plate-simulation will create its own mesh and model, the mesh and conductivity selections can be ignored. Selecting a value will not conflict with the plate-simulation objects and will simply be ignored. In contrast, the survey, topography and at least one component must be selected to run the simulation.
The results of the simulation are stored in the SimPEG group named in the :ref:`simpeg group option <simpeg_group_options>` section.
Results group containing a survey object with all the simulated data channels stored in property groups, and an octree mesh containing the model parameterized in the interface.
To iterate on the design of experiment, simply copy the options, edit, and run again.
If the user wishes to sweep one or more of the input parameters to run a large number of
simulations, they can use the generate sweep file option to write a file used
by the param-sweeps package to do just
that. It is beyond the scope of this document to discuss the use of that package;
refer to its README for further details.
















