Limitation: sampling FO not working with ACMI

Attached case replicating the behavior oscillatingInletACMI2D.tgz

@Mattijs @mark

(Ref EP#333)

I think the problem is in the constructor of isoSurface, the reset of slicedVolScalarField (cValsPtr_).

The adaptPatchFields function in isoSurface needs some special treatment for ACMI. It seems that in the creation of slicedVolScalarField, a cyclicACMIFvPatchField.updateCoeff() is called which triggers slicedFvPatchField::.updateCoeff(), which is not implemented.

Correct. The slicedVolField will have

• on the acmi: an acmiFvPatchField (since it is coupled)

• on the wall: a slicedFvPatchField and now any trigger of the acmi will update the coefficients on the wall which is not defined. Solutions:

• isoSurface do not use slicing.

• on acmi keep a slicedFvPatchField. (change SlicedGeometricField constructor). Bit ad hoc.

• on the wall: keep wallFvPatchField if it is referred to by an acmi. Not logical.

• in acmiFvPatchField: do not update if other side is sliced. Ad hoc.

• define slicedFvPatchField::updateWeightedCoeffs. My preference.

Other option is to comment out virtual updateCoeffs in slicedFvPatchField, which is NotImplemented and let the function from fvPatchField change the Updated flag to true. I tested it and the iso surface works.

Happy with that. Can you put it in and add some comment why? (when acmi gets used with mesh.C() on the 'other' patch - this is done in isoSurface routines).

solved by commit 40bfd331

closed

mentioned in issue #488 (closed)