Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
LDD-for-two-phase-flow-systems
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
David Seus
LDD-for-two-phase-flow-systems
Commits
888b0c8f
Commit
888b0c8f
authored
4 years ago
by
David
Browse files
Options
Downloads
Patches
Plain Diff
setup analysing solver at times for diff perm type
parent
125ed913
Branches
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
Usecases/Two-phase-Richards/multi-patch/layered_soil/TP-R-layered_soil.py
+16
-9
16 additions, 9 deletions
...se-Richards/multi-patch/layered_soil/TP-R-layered_soil.py
with
16 additions
and
9 deletions
Usecases/Two-phase-Richards/multi-patch/layered_soil/TP-R-layered_soil.py
+
16
−
9
View file @
888b0c8f
...
...
@@ -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-
different-intrinsic-vanG-Mualem
"
use_case
=
"
TP-R-layered-soil-different-intrinsic-vanG-Mualem
-analyise-timesteps
"
# The name of this very file. Needed for creating log output.
thisfile
=
"
TP-R-layered_soil.py
"
...
...
@@ -75,9 +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
=
{
190
:
0.19
,
440
:
0.44
,
690
:
0.69
,
940
:
0.94
,
1190
:
1.19
,
1440
:
1.440
}
timestep_size
=
0.001
number_of_timesteps
=
150
0
number_of_timesteps
=
6
0
# LDD scheme parameters ######################################################
...
...
@@ -108,7 +115,7 @@ analyse_condition = False
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
=
1
number_of_timesteps_to_analyse
=
2
# 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.
...
...
@@ -116,17 +123,17 @@ if mesh_study:
write_to_file
=
{
# output the relative errornorm (integration in space) w.r.t. an exact
# solution for each timestep into a csv file.
'
space_errornorms
'
:
Tru
e
,
'
space_errornorms
'
:
Fals
e
,
# save the mesh and marker functions to disk
'
meshes_and_markers
'
:
Tru
e
,
'
meshes_and_markers
'
:
Fals
e
,
# save xdmf/h5 data for each LDD iteration for timesteps determined by
# number_of_timesteps_to_analyse. I/O intensive!
'
L_iterations_per_timestep
'
:
False
,
# save solution to xdmf/h5.
'
solutions
'
:
Tru
e
,
'
solutions
'
:
Fals
e
,
# save absolute differences w.r.t an exact solution to xdmf/h5 file
# to monitor where on the domains errors happen
'
absolute_differences
'
:
Tru
e
,
'
absolute_differences
'
:
Fals
e
,
# analyise condition numbers for timesteps determined by
# number_of_timesteps_to_analyse and save them over time to csv.
'
condition_numbers
'
:
analyse_condition
,
...
...
@@ -432,7 +439,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
,
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment