From f5cc000e3a4eef64fad554b69f8f96bf5e522be0 Mon Sep 17 00:00:00 2001
From: David <forenkram@gmx.de>
Date: Tue, 30 Jun 2020 11:34:21 +0200
Subject: [PATCH] reset some configurations
---
.../TP-R-layered_soil-g-but-same-perm-coarse-dt-longterm.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Two-phase-Richards/multi-patch/layered_soil/TP-R-layered_soil-g-but-same-perm-coarse-dt-longterm.py b/Two-phase-Richards/multi-patch/layered_soil/TP-R-layered_soil-g-but-same-perm-coarse-dt-longterm.py
index 0612f28..a98285d 100755
--- a/Two-phase-Richards/multi-patch/layered_soil/TP-R-layered_soil-g-but-same-perm-coarse-dt-longterm.py
+++ b/Two-phase-Richards/multi-patch/layered_soil/TP-R-layered_soil-g-but-same-perm-coarse-dt-longterm.py
@@ -48,7 +48,7 @@ resolutions = {
# 4: 1e-6,
# 8: 1e-5,
# 16: 5e-6,
- 32: 5e-6,
+ 32: 7e-6,
# 64: 2e-6,
# 128: 1e-6,
# 256: 1e-6,
@@ -87,7 +87,7 @@ 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 = 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
--
GitLab