From 533e7d2a1254bf3b54bfc694a94f95bdb11cfb7f Mon Sep 17 00:00:00 2001
From: David <forenkram@gmx.de>
Date: Thu, 6 Aug 2020 18:18:42 +0200
Subject: [PATCH] setup longterm fine calculation
---
.../TP-R-layered_soil_with_inner_patch-realistic.py | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/Two-phase-Richards/multi-patch/layered_soil_with_inner_patch/TP-R-layered_soil_with_inner_patch-realistic.py b/Two-phase-Richards/multi-patch/layered_soil_with_inner_patch/TP-R-layered_soil_with_inner_patch-realistic.py
index 8a3234c..c7e5397 100755
--- a/Two-phase-Richards/multi-patch/layered_soil_with_inner_patch/TP-R-layered_soil_with_inner_patch-realistic.py
+++ b/Two-phase-Richards/multi-patch/layered_soil_with_inner_patch/TP-R-layered_soil_with_inner_patch-realistic.py
@@ -30,7 +30,7 @@ date = datetime.datetime.now()
datestr = date.strftime("%Y-%m-%d")
# Name of the usecase that will be printed during simulation.
-use_case = "TP-R-layered-soil-with-inner-patch-realistic-same-intrinsic-ultrafine-tol"
+use_case = "TP-R-layered-soil-with-inner-patch-realistic-same-intrinsic-longterm"
# The name of this very file. Needed for creating log output.
thisfile = "TP-R-layered_soil_with_inner_patch-realistic.py"
@@ -47,7 +47,7 @@ resolutions = {
# 4: 2e-6, # h=0.5590
# 8: 2e-6, # h=0.2814
# 16: 1e-6, # h=0.1412
- 32: 1e-9,
+ 32: 1e-6,
# 64: 2e-6,
# 128: 2e-6
}
@@ -57,8 +57,8 @@ resolutions = {
# 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.01
-number_of_timesteps = 500
+timestep_size = 0.001
+number_of_timesteps = 5000
# LDD scheme parameters ######################################################
Lw1 = 0.01 # /timestep_size
@@ -114,7 +114,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 = 2
+plot_timestep_every = 10
# 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