Possible bug in reconstructPar with new BC
I am facing a problem using reconstructPar to reconstruct cases using a new developed BC. The new velocity BC is based on the turbulentInlet BC, having a reference field (vectorField), a fluctuation scale (vector) and some scalar parameters.
When I run the reconstructPar, it writes all parameters as expected, only the reference field is wrongly written as a scalarField with nonsense values.
I have tested versions 1.5.x and 1.6, the same problem appears.
Have someone an idea how to solve (or bypass) this problem?
Make sure you implement rmap and automap methods. Use any other fvPatchField that has a additional field, e.g. totalPressure.
Thank you for the prompt reply. You were right, it was a problem with the automap and rmap methods. It is working well right now.
Thank you again!
it seems that I am facing a similar problem. I changed the inletOutlet fvPatch (from OF 1.6) by making the valueFraction() depending on a field value in the local patch cell. The new velocity BC works fine in serial and parallel computations.
However, when I have used it in parallel, I get the same problem as already described above with reconstructPar. I tried to use automap and rmap and I compiled the BC as part of the solver and alternatively as a dynamic library (is that necessary for reconstructPar?). But that did not change anything. When I set the name of the BC back to inletOutlet in all the processor directories reconstructPar works fine again.
Any ideas what I should look for or what I could have missed?
reconstructPar does not 'know' your boundary condition - it only knows the boundary conditions from the libraries it is linked with. In your system/controlDict add a
to make it 'know' your boundary conditions.
|All times are GMT -4. The time now is 18:10.|