Skip to content

Commit f23caba

Browse files
committed
Apply Victor's suggestions
1 parent 37cdc61 commit f23caba

File tree

2 files changed

+15
-14
lines changed

2 files changed

+15
-14
lines changed

doc/source/examples/multiphysics/tracer-in-static-mixer/tracer-in-static-mixer.rst

+15-14
Original file line numberDiff line numberDiff line change
@@ -45,6 +45,8 @@ In this example, we use the auxiliary tracer physics to quantify the mixing of t
4545
#. Simulating the transient flow with a small ``time step`` until the flow has reached the steady state;
4646
#. Simulate the flow of the tracer with a larger ``time step`` while reusing the computed velocity field from the previous simulation.
4747

48+
This strategy reduces the computational cost of the simulation as the fluid flow solution is reused in the second step.
49+
4850
--------------
4951
Parameter File
5052
--------------
@@ -70,7 +72,7 @@ Simulation control
7072
set output frequency = 5
7173
end
7274
73-
#. We use a ``bdf1`` time integration scheme with a short ``time step = 1e-4`` seconds. After ``time end = 40e-4`` seconds, we consider that the velocity field has reached a steady state.
75+
We use a ``bdf1`` time integration scheme with a short ``time step = 1e-4`` :math:`\text{s}`. After ``time end = 40e-4`` :math:`\text{s}`, we consider that the velocity field has reached a steady state. According to :doc:`../../sharp-immersed-boundary/3d-rbf-static-mixer/3d-rbf-static-mixer`, the pressure drop varies by less than :math:`5` % in the range [30, 40] :math:`\text{s}`.
7476

7577
Restart
7678
******************
@@ -86,13 +88,12 @@ We use Lethe's checkpoint/restart mechanism to feed the steady-state flow inform
8688
set restart = false
8789
end
8890
89-
#. We ``checkpoint`` the simulation at every ``5`` time steps, both for safety (each time step takes a long time to complete) and for reuse in the second simulation.
90-
#. We do not ``restart`` the simulation unless stopped before it reaches ``time end``.
91+
We ``checkpoint`` the simulation at every ``5`` time steps, both for safety (each time step takes a long time to complete) and for reuse in the second simulation.
9192

9293
Multiphysics
9394
******************
9495

95-
Both ``fluid dynamics`` and ``tracer`` are enabled for the first simulation. However, the tracer injection only begins at the second step.
96+
Both ``fluid dynamics`` and ``tracer`` are enabled for the first simulation to ensure initialization of the ``tracer`` field. However, the tracer injection only begins at the second step.
9697

9798
.. code-block:: text
9899
@@ -104,7 +105,7 @@ Both ``fluid dynamics`` and ``tracer`` are enabled for the first simulation. How
104105
Physical Properties
105106
*******************
106107

107-
In this case we consider that we have a passive tracer in water. The units used for the physical properties are centimeters and seconds.
108+
In this case we consider that we have a passive tracer in water. The units used for the physical properties are :math:`\text{cm}` and :math:`\text{s}`.
108109

109110
.. code-block:: text
110111
@@ -121,9 +122,9 @@ In this case we consider that we have a passive tracer in water. The units used
121122
end
122123
123124
#. The ``tracer diffusivity model`` is ``immersed solid tanh``. This model is used in ``lethe-fluid-sharp`` for tracer flow percolating immersed solids.
124-
#. The ``tracer diffusivity outside`` is ``1e-5``, as this is a typical value for a passive tracer in a liquid.
125-
#. The ``tracer diffusivity inside`` is set to ``1e-10``. The low value prevents diffusivity inside the solid while providing numerical stability.
126-
#. The ``thickness`` is ``5e-1``. At the scale of the problem, this provides a smooth transition without generating oscillations between liquid and solid phases.
125+
#. The ``tracer diffusivity outside`` is ``1e-5`` :math:`\text{cm²/s}`, as this is a typical value for a passive tracer in a liquid.
126+
#. The ``tracer diffusivity inside`` is set to ``1e-10`` :math:`\text{cm²/s}`. The low value prevents diffusivity inside the solid while providing numerical stability (:math:`> 0`).
127+
#. The ``thickness`` is ``5e-1`` :math:`\text{cm}`. At the scale of the problem, this provides a smooth transition without generating oscillations between liquid and solid phases. The thickness is of the order of magnitude of the smallest cell length to restrict the transition to one cell thickness.
127128

128129
Tracer Boundary Conditions
129130
***************************
@@ -163,7 +164,7 @@ Tracer Boundary Conditions
163164
end
164165
165166
#. We use ``time dependent`` boundary conditions, defined at :math:`y<0` and :math:`11 < t < 61` to inject a pulse on the lower half of the inlet.
166-
#. All other boundary conditions are ``outlet``. This condition is natural for the outlet of the problem. For lateral walls, this condition represents an impermeable wall.
167+
#. All other boundary conditions are ``outlet``. This condition is natural for the outlet of the problem. For lateral walls, this condition represents an impermeable wall since velocity is perpendicular.
167168

168169
Post-processing
169170
*******************
@@ -181,7 +182,7 @@ Post-processing
181182
set tracer flow rate name = tracer_flow_rate
182183
end
183184
184-
#. ``calculate average velocities`` is enabled, beginning at ``initial time = 30e-4``. This means that the last :math:`25\%` of the first simulation will be used to calculate the time-averaged fluid velocity profile.
185+
#. ``calculate average velocities`` is enabled, beginning at ``initial time = 30e-4`` :math:`\text{s}`. This means that the last :math:`25\%` of the first simulation will be used to calculate the time-averaged fluid velocity profile.
185186
#. ``calculate tracer flow rate`` is enabled to provide data for mixing quantification.
186187

187188
Simulation 2: Tracer transport
@@ -201,8 +202,8 @@ Simulation control
201202
...
202203
end
203204
204-
#. We use a longer ``time step`` of ``10`` seconds.
205-
#. We simulate until ``time end = 500`` seconds to allow the tracer to flow through the entire length of the domain.
205+
#. We use a longer ``time step`` of ``10`` :math:`\text{s}`.
206+
#. We simulate until ``time end = 500`` :math:`\text{s}` to allow the tracer to flow through the entire length of the domain.
206207

207208
Restart
208209
******************
@@ -262,7 +263,7 @@ The simulation can be launched on multiple cores using ``mpirun`` and the ``leth
262263
Results
263264
-------
264265

265-
The following movie shows the evolution of tracer through the static mixer, both as a colored slice and colored streamlines:
266+
The following movie shows the flow of the tracer through the static mixer, both as a colored slice and colored streamlines:
266267

267268
.. raw:: html
268269

@@ -285,7 +286,7 @@ The tracer evolution through the inlet and outlet can be monitored by plotting t
285286
| |
286287
+-----------------------------------------------------------------------------------------------------------------------------+
287288

288-
As the Figure shows, the concentration of the tracer flattens as it flows. The gap between between the inlet and outlet peaks is of :math:`170` seconds. When compared to the theoretical time of :math:`150` seconds (:math:`d_x/u_x`, with :math:`d_x` the domain length and :math:`u_x` the inlet velocity), this difference can be explained by retention effects and the tortuous paths that the tracer travels through.
289+
As the Figure shows, the concentration of the tracer flattens as it flows. The gap between between the inlet and outlet peaks is of :math:`170` :math:`\text{s}`. When compared to the theoretical time of :math:`150` :math:`\text{s}` (:math:`d_x/u_x`, with :math:`d_x` the domain length and :math:`u_x` the inlet velocity), this difference can be explained by retention effects and the tortuous paths that the tracer travels through.
289290

290291
---------
291292
Reference

0 commit comments

Comments
 (0)