From ec3cdf57bb648455ac321876350ebf52cc7d0799 Mon Sep 17 00:00:00 2001 From: Mark Olesen <Mark.Olesen@esi-group.com> Date: Wed, 15 Dec 2021 11:33:19 +0100 Subject: [PATCH] ENH: have expression dupZeroField respect defaultBoundaryType - this is now consistent with what the internal "get(Vol|Surface|Point)Field" methods deliver (ie, zero-gradient for volume, calculated otherwise). Still some slight inconsistencies with what the internal "new(Vol|Surface|Point)Field" methods deliver however. There they are always "calculated" --- src/finiteVolume/expressions/volume/volumeExprDriver.C | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/finiteVolume/expressions/volume/volumeExprDriver.C b/src/finiteVolume/expressions/volume/volumeExprDriver.C index 35ce03da28b..ff9e160fbc1 100644 --- a/src/finiteVolume/expressions/volume/volumeExprDriver.C +++ b/src/finiteVolume/expressions/volume/volumeExprDriver.C @@ -233,7 +233,9 @@ Foam::expressions::volumeExpr::parseDriver::dupZeroField() const ( \ word(pTraits<Type>::typeName) + word("(zero)"), \ (*ptr).mesh(), \ - dimensioned<Type>(Zero) \ + dimensioned<Type>(Zero), \ + /* zeroGradient (volume) or calculated (other) */ \ + defaultBoundaryType(*ptr) \ ).ptr() \ ); \ break; \ -- GitLab