diff --git a/Usecases/Two-phase-Richards/multi-patch/layered_soil/TP-R-layered_soil-g-but-same-perm.py b/Usecases/Two-phase-Richards/multi-patch/layered_soil/TP-R-layered_soil-g-but-same-perm.py
index 620840e8229d6e7b5dc68fe49e6f72c78ff8e6a3..4979dea3d1ee4324563184f5768da164cfdf6239 100755
--- a/Usecases/Two-phase-Richards/multi-patch/layered_soil/TP-R-layered_soil-g-but-same-perm.py
+++ b/Usecases/Two-phase-Richards/multi-patch/layered_soil/TP-R-layered_soil-g-but-same-perm.py
@@ -49,7 +49,7 @@ datestr = date.strftime("%Y-%m-%d")
 
 
 # Name of the usecase that will be printed during simulation.
-use_case = "TP-R-layered-soil-realistic-same-perm-vanG-Mualem"
+use_case = "TP-R-layered-soil-realistic-same-perm-vanG-Mualem-new-param-test"
 # The name of this very file. Needed for creating log output.
 thisfile = "TP-R-layered_soil-g-but-same-perm.py"
 
@@ -78,32 +78,32 @@ resolutions = {
 # that this initial timestep should be counted as.
 # Format:
 # timestep_num: initial_time
-starttimes = {0: 0.0}
-# starttimes = {
-#     0: 0.0,
-#     1: 0.3,
-#     2: 0.6,
-#     3: 0.9,
-#     }
+# starttimes = {0: 0.0}
+starttimes = {
+    0: 0.0,
+    1: 0.3,
+    2: 0.6,
+    3: 0.9,
+    }
 timestep_size = 0.001
-number_of_timesteps = 1500
+number_of_timesteps = 1
 
 # LDD scheme parameters  ######################################################
-Lw1 = 0.1  # /timestep_size
+Lw1 = 0.025  # /timestep_size
 Lnw1 = Lw1
-Lw2 = 0.9  # /timestep_size
+Lw2 = 0.1  # /timestep_size
 Lnw2 = Lw2
-Lw3 = 0.9  # /timestep_size
+Lw3 = 0.1  # /timestep_size
 Lnw3 = 0.025
 Lw4 = 0.08  # /timestep_size
-Lnw4 = 0.025
+Lnw4 = 0.005
 
-lambda12_w = 0.75
+lambda12_w = 2
 lambda12_nw = 2
-lambda23_w = 0.3
+lambda23_w = 4
 lambda23_nw = 1
-lambda34_w = 0.4
-lambda34_nw = 2
+lambda34_w = 4
+lambda34_nw = 1
 
 include_gravity = True
 debugflag = False
@@ -113,10 +113,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 = 5
+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 = 10
+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.