From 6eeb1834a9a7a966b45de73082dba5d915b42955 Mon Sep 17 00:00:00 2001 From: Wolfgang Bangerth Date: Wed, 11 Dec 2019 15:23:44 -0700 Subject: [PATCH] Also update the 3d picture section. --- examples/step-46/doc/results.dox | 36 +++++++------------------------- 1 file changed, 8 insertions(+), 28 deletions(-) diff --git a/examples/step-46/doc/results.dox b/examples/step-46/doc/results.dox index 57d7b1327b..7b3e46c0fe 100644 --- a/examples/step-46/doc/results.dox +++ b/examples/step-46/doc/results.dox @@ -112,37 +112,17 @@ Refinement cycle 2 Solving... @endcode You'll notice that the big bottleneck is the solver: SparseDirectUmfpack needs -approximately 8 hours and some 42 GB of memory to solve the last iteration of -this problem on a 2010 workstation (the second to last iteration took only 6 +nearly 5 hours and some 80 GB of memory to solve the last iteration of +this problem on a 2016 workstation (the second to last iteration took only 16 minutes). Clearly a better solver is needed here, a topic discussed below. -The results can also be visualized and yield some good pictures: +The results can also be visualized and yield good pictures as +well. Here is one, showing both a vector plot for the velocity (in +oranges), the solid displacement (in blues), and shading the solid region: - - - - - - - - -
- -

- Vectors of the fluid velocity and magnitude of the - displacement of the solid part. -

- 		- -

- Streamlines of the velocity, with the mesh superimposed. -

-
- -

- Solid displacement. -

-
+

+ +

In addition to the lack of a good solver, the mesh is a bit unbalanced: mesh refinement heavily favors the fluid subdomain (in 2d, -- 2.39.5