From 43dff762591ce3efe2bb7ca95f8f7e2c412e433b Mon Sep 17 00:00:00 2001
From: David Seus <david.seus@ians.uni-stuttgart.de>
Date: Thu, 22 Oct 2020 12:30:38 +0200
Subject: [PATCH] setup usecase with gravity without time parallelisation

---
 ...soil-g-but-same-perm-coarse-dt-longterm.py | 24 +++++++++----------
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/Usecases/Two-phase-Richards/multi-patch/layered_soil/TP-R-layered_soil-g-but-same-perm-coarse-dt-longterm.py b/Usecases/Two-phase-Richards/multi-patch/layered_soil/TP-R-layered_soil-g-but-same-perm-coarse-dt-longterm.py
index 90cd4d3..bb74118 100755
--- a/Usecases/Two-phase-Richards/multi-patch/layered_soil/TP-R-layered_soil-g-but-same-perm-coarse-dt-longterm.py
+++ b/Usecases/Two-phase-Richards/multi-patch/layered_soil/TP-R-layered_soil-g-but-same-perm-coarse-dt-longterm.py
@@ -66,7 +66,7 @@ resolutions = {
                 # 4: 1e-6,
                 # 8: 1e-5,
                 # 16: 5e-6,
-                32: 6e-6,
+                32: 2e-5,
                 # 64: 2e-6,
                 # 128: 1e-6,
                 # 256: 1e-6,
@@ -75,16 +75,16 @@ resolutions = {
 # starttimes gives a list of starttimes to run the simulation from.
 # The list is looped over and a simulation is run with t_0 as initial time
 #  for each element t_0 in starttimes.
-# starttimes = {0: 0.0}
-starttimes = {
-    0: 0.0,
-    300: 0.3,
-    600: 0.6,
-    900: 0.9,
-    1200: 1.2
-    }
+starttimes = {0: 0.0}
+# starttimes = {
+#     0: 0.0,
+#     300: 0.3,
+#     600: 0.6,
+#     900: 0.9,
+#     1200: 1.2
+#     }
 timestep_size = 0.001
-number_of_timesteps = 400
+number_of_timesteps = 1500
 
 
 # LDD scheme parameters  ######################################################
@@ -112,10 +112,10 @@ analyse_condition = False
 # when number_of_timesteps is high, it might take a long time to write all
 # timesteps to disk. Therefore, you can choose to only write data of every
 # plot_timestep_every timestep to disk.
-plot_timestep_every = 1
+plot_timestep_every = 5
 # Decide how many timesteps you want analysed. Analysed means, that
 # subsequent errors of the L-iteration within the timestep are written out.
-number_of_timesteps_to_analyse = 7
+number_of_timesteps_to_analyse = 10
 
 # fine grained control over data to be written to disk in the mesh study case
 # as well as for a regular simuation for a fixed grid.
-- 
GitLab