From cb7630ceea1aa51262ceaff9a23dde2fb6c0044e Mon Sep 17 00:00:00 2001
From: David Seus <david.seus@ians.uni-stuttgart.de>
Date: Tue, 7 Jul 2020 18:02:02 +0200
Subject: [PATCH] play around with parameters

---
 ...alistic-gravity-but-same-intrinsic-perm.py | 30 +++++++++----------
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/Two-phase-Richards/two-patch/TP-R-two-patch-test-case/TP-R-2-patch-realistic-gravity-but-same-intrinsic-perm.py b/Two-phase-Richards/two-patch/TP-R-two-patch-test-case/TP-R-2-patch-realistic-gravity-but-same-intrinsic-perm.py
index 352e07f..ace7a5e 100755
--- a/Two-phase-Richards/two-patch/TP-R-two-patch-test-case/TP-R-2-patch-realistic-gravity-but-same-intrinsic-perm.py
+++ b/Two-phase-Richards/two-patch/TP-R-two-patch-test-case/TP-R-2-patch-realistic-gravity-but-same-intrinsic-perm.py
@@ -30,13 +30,13 @@ date = datetime.datetime.now()
 datestr = date.strftime("%Y-%m-%d")
 
 # Name of the usecase that will be printed during simulation.
-use_case = "TP-R-2-patch-realistic-gravity-but-same-intrinsic-perm"
+use_case = "TP-R-2-patch-realistic-same-intrinsic-perm-flattening-L"
 # The name of this very file. Needed for creating log output.
 thisfile = "TP-R-2-patch-realistic-gravity-but-same-intrinsic-perm.py"
 
 # GENERAL SOLVER CONFIG  ######################################################
 # maximal iteration per timestep
-max_iter_num = 250
+max_iter_num = 1000
 FEM_Lagrange_degree = 1
 
 # GRID AND MESH STUDY SPECIFICATIONS  #########################################
@@ -47,7 +47,7 @@ resolutions = {
                 # 4: 1e-5,
                 # 8: 1e-5,
                 # 16: 5e-6,
-                32: 5e-6,
+                32: 3e-6,
                 # 64: 2e-6,
                 # 128: 2e-6,
                 # 256: 1e-6,
@@ -56,32 +56,32 @@ 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, 1: 0.3, 2: 0.6, 3: 0.9}
 timestep_size = 0.001
-number_of_timesteps = 800
+number_of_timesteps = 1
 
 # LDD scheme parameters  ######################################################
-Lw1 = 0.25
-Lnw1 = 0.25
+Lw1 = 0.4
+Lnw1 = 0.1
 
-Lw2 = 0.5
-Lnw2 = 0.25
+Lw2 = 0.4
+Lnw2 = 0.4
 
-lambda_w = 40
-lambda_nw = 40
+lambda_w = 0.25
+lambda_nw = 0.25
 
 include_gravity = True
 debugflag = False
-analyse_condition = True
+analyse_condition = False
 
 # I/O CONFIG  #################################################################
 # 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 = 4
+plot_timestep_every = 1
 # 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 = 5
+number_of_timesteps_to_analyse = 1
 
 # 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.
@@ -334,7 +334,7 @@ if __name__ == '__main__':
             #     parameter=simulation_parameter
             #     )
 
-        LDDsim.join()
+        # LDDsim.join()
         if mesh_study:
             simulation_output_dir = processQueue.get()
             hlp.merge_spacetime_errornorms(isRichards=isRichards,
-- 
GitLab