Hi Georg,
unfortunately, this will not work. We have that
residual = storage + inner_flux + boundary_flux + sources
Once we have that residual = 0, we can say
boundary_flux = - (storage + inner_flux + sources)
which is what I just suggested to calculate.
However, if you impose
boundary_flux = -
Hi again!
For the outflow boundary condition, also computeFlux is used on the boundary. I
am not 100% sure but since this is just an approximation it would probably be
better to rewrite the evalOutflowSegment-function of the boxlocalresidual
according to your explanations?
Kind regards
Georg
Hi Bernd,
Thanks for the information. I was not aware that computeFlux on a boundary face
for the box method will be just an approximation. I will have to improve the
code.
Kind regards
Georg
Von: Dumux [mailto:dumux-boun...@listserv.uni-stuttgart.de] Im Auftrag von
Bernd Flemisch
Gesendet:
Hi Georg,
sorry for the long silence.
I agree that it should be easier to calculate the fluxes from outside
the local residual. As you suggest, this could be made possible by a
static computeFlux function. We are currently on the way of rethinking
and -working the whole volVars/fluxVars
Hi Etienne,
sorry to get back to you so late.
1. The residual evaluation is done element-wise. On each element,
secondary variables are calculated from the primary ones by using the
material law defined on the subcontrol volume. If the parameters are
defined element-wise like in your
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#321 - DiffusivityConstantTau unused, rename tau
User who did this - Thomas Fetzer (Thomas Fetzer)
--
There is a test in material/fluidmatrixinteractions. I would propose to shift
tau to a
