Merge pull request #116 from openearth/add_content

updated readthedocs

.vscode/settings.json

@@ -0,0 +1,3 @@
+{
+    "restructuredtext.confPath": "${workspaceFolder}\\doc"
+}

doc/BMI.rst

@@ -1,7 +1,7 @@
 .. _basicModelInterface:
 
 *******************************
-The Basic Model Interface
+The BMI
 *******************************
 
 Introduction
@@ -52,32 +52,6 @@ Also, all 'bmi'ed' models can still be executed in stand-alone mode.
 
 Compared to 'non-bmi'ed' version of a model, run times of the 'bmi'ed' version are near-identical.
 
-GLOFRIM workflow
-================
-By applyting the BMI functions, the following workflow is followed in GLOFRIM. The example shows coupling between a
-hydrologic and a hydrodynamic model, but would be identical if other or more models were coupled.
-
-.. image:: _images/workflow.png
-    :scale: 40%
-    :align: center
-
-After the model are chosen and coupling settings are defined in the GLOFRIM ini-file, the ini-file is read by GLOFRIM
-to first initialize the model-specific configuration files and then initialize both models as a coupled entity.
-
-Essential part of creating the coupled entity is the coupling of grids which is explained in more detail in :ref:`gridCoupling`.
-
-Once the coupled models are initialized, a loop is entered, starting at the start time and terminating at the end time
-as specified in the python executiont command (see :ref:`run_from_commandline`).
-
-During the loop, models are individually updated from the upstream end of the model cascade to the most downstream model,
-depending on the number of models coupled.
-
-After a model is updated, the variables to be exchanged (as defined in GLOFRIM ini-file) are retrieved from the providing model,
-if necessary aligned, and inserted to the receiving model. Only then, model time of the receiving model is forward integrated
-until the model time of the providing model is reached.
-
-If model end time is reached, model execution is finalized.
-