In continuation of issue 92 (Spurious warrings on swak4foam variable), the problem still persist when a variable is generated by calculatedGlobalVariables (the issue was already fixed when a variable was passed to groovyBC inmediately).
A tarbal of a sample case using calculatedGlobalVariables is attached to demonstrate the warning generated:
--> FOAM Warning :
From function PatchValueExpressionDriver::getField(const word &inName)
in file lnInclude/PatchValueExpressionDriverI.H at line 131
Variable CFeMeanInletNew is not a single value but does not fit the size. Using average and hoping for the best
For groovy BC this warning was raised because a single value was stored as a field with only one entry. Apparently this is still the case for the calculatedGlobalVariables?
Seems like the case of uniform values is not considered