[CLN/DOC]

Author: Leguark

DevelopersGuide.md

@@ -16,7 +16,7 @@ Github release
     # push git tag
     $ git push --tags origin master
 
-PyPi release
+PyPi release:
 ------------
 New 
 ```

examples/tutorials/ch1_fundamentals/ch1_1_basics.py

@@ -83,65 +83,15 @@
 # %% 
 geo_model.orientations_copy
 
-# %%
-# Declaring the Sequential Order of Geological Formations
-# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-# In our model, we want the geological units to appear in the correct chronological order. 
-# Such order could be determined by a sequence of stratigraphic deposition, unconformities 
-# due to erosion, or other lithological genesis events like igneous intrusions. A similar 
-# age-related order is declared for faults in our model. In GemPy, we use the function 
-# `gempy.map_stack_to_surfaces` to assign formations or faults to different sequential series 
-# by declaring them in a Python dictionary.
-#
-# The correct ordering of series is crucial for model construction! It's possible to assign 
-# several surfaces to one series. The order of units within a series only affects the color 
-# code, so we recommend maintaining consistency. The order can be defined by simply changing 
-# the order of the lists within `gempy.core.data.StructuralFrame.structural_groups` and 
-# `gempy.core.data.StructuralGroups.elements` attributes.
-#
-# Faults are treated as independent groups and must be younger than the groups they affect. 
-# The relative order between different faults defines their tectonic relationship 
-# (the first entry is the youngest).
-#
-# For a model with simple sequential stratigraphy, all layer formations can be assigned to 
-# one series without an issue. All unit boundaries and their order would then be determined 
-# by interface points. However, to model more complex lithostratigraphical relations and 
-# interactions, separate series definition becomes important. For example, modeling an 
-# unconformity or an intrusion that disrupts older stratigraphy would require declaring a 
-# "newer" series.
-#
-# By default, we create a simple sequence inferred from the data:
-#
-#
-# Setting Up the Structural Framework
-# """""""""""""""""""""""""""""""""""
-#
-# Each data entry includes an ID that corresponds to a formation name, which GemPy uses to create a base structural framework.
-# However, the sequence of these formations is still arbitrary, as they have all automatically been assigned to the default
-# structural group in our `geo_model` object. We will fix this in the subsequent steps.
 
 # %%
-geo_model.structural_frame
-
-# %%
-# Our example model comprises four main layers (plus an underlying
-# basement that is automatically generated by GemPy) and one main normal
-# fault displacing those layers. Assuming a simple stratigraphy where each
-# younger unit was deposited onto the underlying older one, we can assign
-# these layer formations to one series called "Strat\_Series". For the
-# fault, we declare a respective "Fault\_Series" as the first key entry in
-# the mapping  dictionary. We could give any other names to these
-# series, the formations however have to be referred to as named in the
-# input data. 
-# 
-#
 # Declaring the Sequential Order of Structural Elements (Geological Formations)
 # """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
 # In our model, we want the geological units to appear in the correct chronological order. This order could be determined by a sequence
 # of stratigraphic deposition, unconformities due to erosion, or other lithological genesis events like igneous intrusions. A similar
 # age-related order is declared for faults in our model. In GemPy, we use the function `gempy.map_stack_to_surfaces` to assign formations
 # or faults to different sequential series by declaring them in a Python dictionary.
-
+#
 #
 # The correct ordering of series is crucial for model construction! It's possible to assign several surfaces to one series. The order of
 # units within a series only affects the color code, so we recommend maintaining consistency. The order can be defined by simply changing
@@ -179,8 +129,6 @@
 # Note how the structural frame still indicates the "Fault Series" group to have a relation type "erode".
 # We still need to tell GemPy that we want this group to be a fault. We do this using the function `set_is_fault`.
 
-geo_model.structural_frame  # Display the resulting structural frame
-
 # %% 
 gp.set_is_fault(
     frame=geo_model.structural_frame,