|
33 | 33 | # - Additional data |
34 | 34 | # - Faults |
35 | 35 | # |
36 | | -# We will see each of this class in further detail in the future. |
| 36 | +# We will see each of these classes in further detail in the future. |
37 | 37 | # |
38 | 38 | # Most of data can also be generated from raw data that comes in the form |
39 | 39 | # of CSV-files (CSV = comma-separated values). Such files might be |
|
42 | 42 | # Microsoft Excel or LibreOffice Calc. |
43 | 43 | # |
44 | 44 | # In this tutorial, all input data is created by importing such CSV-files. |
45 | | -# These exemplary files can be found in the ``input_data`` folder in the |
| 45 | +# These example files can be found in the ``input_data`` folder in the |
46 | 46 | # root folder of GemPy. The data comprises :math:`x`-, :math:`y`- and |
47 | 47 | # :math:`z`-positional values for all surface points and orientation |
48 | 48 | # measurements. For the latter, poles, azimuth and polarity are |
49 | 49 | # additionally included. Surface points are furthermore assigned a |
50 | 50 | # formation. This might be a lithological unit such as "Sandstone" or a |
51 | | -# structural feature such as "Main Fault". It is decisive to remember |
| 51 | +# structural feature such as "Main Fault". It is important to remember |
52 | 52 | # that, in GemPy, interface position points mark the **bottom** of a |
53 | 53 | # layer. If such points are needed to resemble a top of a formation (e.g. |
54 | 54 | # when modeling an intrusion), this can be achieved by defining a |
|
119 | 119 | # |
120 | 120 | # You can assign several surfaces to one series. The order of the units |
121 | 121 | # within such as series is only relevant for the color code, thus we |
122 | | -# recommend to be consistent. You can define this order via another |
| 122 | +# recommend being consistent. You can define this order via another |
123 | 123 | # attribute "``order_formations``/ " or by using the specific command |
124 | 124 | # ``set_order_formations``. (If the order of the pile differs from the |
125 | 125 | # final result the color of the interfaces and input data will be |
126 | 126 | # different.) |
127 | 127 | # |
128 | | -# Every fault is treated as an independent series and have to be at set at |
| 128 | +# Every fault is treated as an independent series and has to be at set at |
129 | 129 | # the **top of the pile**. The relative order between the distinct faults |
130 | 130 | # defines the tectonic relation between them (first entry is the |
131 | 131 | # youngest). |
|
189 | 189 | # Our model input data, here named "*geo\_model*", contains all the |
190 | 190 | # information that is essential for the construction of our model. You can |
191 | 191 | # access different types of information by using ``gp.get_data`` or simply |
192 | | -# by accessiong the atrribues. |
| 192 | +# by accessiong the atrributes. |
193 | 193 | # |
194 | 194 | # We can, for example, return the coordinates of our modeling grid via: |
195 | 195 | # |
|
283 | 283 |
|
284 | 284 | # %% |
285 | 285 | # This function rescales the extent and coordinates of the original data |
286 | | -# (and store it in the attribute ``geo_data_res`` which behaves as a usual |
| 286 | +# (and stores it in the attribute ``geo_data_res`` which behaves as a usual |
287 | 287 | # ``InputData`` object) and adds mathematical parameters that are needed |
288 | 288 | # for conducting the interpolation. The computation of this step may take |
289 | 289 | # a while, as it also compiles a theano function which is required for the |
290 | 290 | # model computation. However, should this not be needed, we can skip it by |
291 | 291 | # declaring ``compile_theano = False`` in the function. |
292 | 292 | # |
293 | 293 | # Furthermore, this preparation process includes an assignment of numbers |
294 | | -# to each formation. Note that GemPy's always creates a default basement |
| 294 | +# to each formation. Note that GemPy always creates a default basement |
295 | 295 | # formation as the last formation number. Afterwards, numbers are |
296 | 296 | # allocated from youngest to oldest as defined by the sequence of series |
297 | 297 | # and formations. On the property ``formations`` on our interpolation |
|
315 | 315 | # ``compute_model``. By default, this will return two separate solutions |
316 | 316 | # in the form of arrays. The first gives information on the lithological |
317 | 317 | # formations, the second on the fault network in the model. These arrays |
318 | | -# consist of two subarrays as entries each: |
| 318 | +# consist of two subarrays as entries described here: |
319 | 319 | # |
320 | 320 | # 1. Lithology block model solution: |
321 | 321 | # |
|
0 commit comments