[schiffbauer]

Dear Foamers,

mapping a field with OF 2.4.0, I get the following error:

Create databases as time
Case   : ../testMap
nProcs : 1

Source time: 0
Target time: 0

Create meshes

Source mesh size: 36509    Target mesh size: 36509


Consistently creating and mapping fields for time 0

Creating mesh-to-mesh addressing for region0 and region0 regions using cellVolumeWeight


--> FOAM FATAL ERROR: 
Plane normal defined with zero length
Bad points:(0.18 0.0839999 0.012) (0.18 0.0899998 0.012) (0.18 0.0959993 0.012)

    From function void plane::calcPntAndVec
(
    const point&,
    const point&,
    const point&
)

    in file meshes/primitiveShapes/plane/plane.C at line 116.

FOAM aborting

#0  Foam::error::printStack(Foam::Ostream&) at ??:?
#1  Foam::error::abort() at ??:?
#2  Foam::plane::calcPntAndVec(Foam::Vector<double> const&, Foam::Vector<double> const&, Foam::Vector<double> const&) at ??:?
#3  Foam::tetOverlapVolume::tetTetOverlapVol(Foam::tetPoints const&, Foam::tetPoints const&) const at ??:?
#4  Foam::tetOverlapVolume::cellCellOverlapVolumeMinDecomp(Foam::primitiveMesh const&, int, Foam::primitiveMesh const&, int, Foam::treeBoundBox const&) const at ??:?
#5  Foam::meshToMeshMethod::interVol(int, int) const at ??:?
#6  Foam::cellVolumeWeightMethod::calculateAddressing(Foam::List<Foam::List<int> >&, Foam::List<Foam::List<double> >&, Foam::List<Foam::List<int> >&, Foam::List<Foam::List<double> >&, int, int, Foam::List<int> const&, Foam::List<bool>&, int&) at ??:?
#7  Foam::cellVolumeWeightMethod::calculate(Foam::List<Foam::List<int> >&, Foam::List<Foam::List<double> >&, Foam::List<Foam::List<int> >&, Foam::List<Foam::List<double> >&) at ??:?
#8  Foam::meshToMesh::calcAddressing(Foam::word const&, Foam::polyMesh const&, Foam::polyMesh const&) at ??:?
#9  Foam::meshToMesh::calculate(Foam::word const&) at ??:?
#10  Foam::meshToMesh::constructNoCuttingPatches(Foam::word const&, Foam::word const&, bool) at ??:?
#11  Foam::meshToMesh::meshToMesh(Foam::polyMesh const&, Foam::polyMesh const&, Foam::meshToMesh::interpolationMethod const&, bool) at ??:?
#12  ? at ??:?
#13  ? at ??:?
#14  __libc_start_main in "/lib/x86_64-linux-gnu/libc.so.6"
#15  ? at ??:?
Aborted (core dumped)

The mesh is a NACA profile in .stl-format, created with sHM.

Trying to find a solution, I did the following:
1.) run the simulation - OK
2.) copied the case folder and deleted the time directories
3.) run

mapFields ../sourceCase/

- NOT OK

Besides, I changed the mesh in the source case. The result was the same with the difference that the

Bad points: (...) ...

changed.

The other thread linked to this error didn't provide a solution. Do you have an idea?

[schiffbauer]

I still have the same problem, does somebody has an idea?

[wyldckat]

Greetings schiffbauer,

I've searched with Google just now for:

site:www.cfd-online.com openfoam Plane normal defined with zero length

And quickly found this thread: http://www.cfd-online.com/Forums/ope...pfields-2.html - where in post #32 is the answer.

In addition to this, in OpenFOAM-dev, mapFields from 2.2 was restored and the one from 2.3 was renamed to mapFieldsPar: http://www.openfoam.org/mantisbt/view.php?id=1702

Best regards,
Bruno

[schiffbauer]

Thanks for your quick answer.
Well, actually I wanted to solve it with the actual OF version 2.4.0, but this might be not the easiest way...

[danielbanos10]

I had the same error in OF 2.4, and the solution I found was to move the target mesh a little bit into the soure mesh, in orden to use cuttingPatches instead of patchMap.
And now it works, and there is no normal errors.
Best regards

[LuckyTran]

I followed the suggestion in #34 and added

-mapMethod mapNearest

the default is cellVolumeWeight. Using mapNearest successfully mapped.

[boffin5]

For the run error of "plane nomal defined with zero length", I tried the suggestion of using "mapNearest" in fvOptions.

I have two simulations that I tried it on; the first was a chtMultiRegion case with complicated geometry which takes a long time to mesh. Using mapNearest, the simulation locked up in the chtMultiRegionFoam phase.

So I then went to a simple template case with the same setup. This one runs quickly, so is good to try things on. However, when I used mapNearest, it simply caused the simulation to lock up just as with the complicated case.

Am I missing something? Maybe a tolerance setting?