problems with mesh generation for the motorBike case
 

Hello,

i got this Error message, while am trying to create the mesh by motorBike tuorial.
could any one help me to find the problem?
thanx in advance,

Monzer


that's the error message:


--> FOAM FATAL ERROR:
Specified illegal patch minZ in layer dictionary.
Valid patch names are
72
(
frontAndBack
inlet
outlet
lowerWall
upperWall
motorBike_frt-fairing:001%1
motorBike_windshield:002%2
motorBike_rr-wh-rim:005%5
motorBike_rr-wh-rim:010%10
motorBike_fr-wh-rim:011%11
motorBike_fr-wh-brake-disk:012%12
motorBike_frame:016-shadow%13
motorBike_rear-susp:014%14
motorBike_rear-susp:014-shadow%15
motorBike_frame:016%16
motorBike_rr-wh-rim:005-shadow%17
motorBike_rr-wh-chain-hub:022%22
motorBike_rearseat%24
motorBike_frt-fairing%25
motorBike_windshield%26
motorBike_headlights%27
motorBike_driversseat%28
motorBike_rear-body%29
motorBike_fuel-tank%30
motorBike_exhaust%31
motorBike_rr-wh-rim%32
motorBike_fr-mud-guard%33
motorBike_fr-wh-rim%34
motorBike_fr-wh-brake-disk%35
motorBike_fr-brake-caliper%36
motorBike_fr-wh-tyre%37
motorBike_hbars%38
motorBike_fr-forks%39
motorBike_chain%40
motorBike_rr-wh-tyre%41
motorBike_square-dial%42
motorBike_round-dial%43
motorBike_dial-holder%44
motorBike_rear-susp%45
motorBike_rear-brake-lights%46
motorBike_rear-light-bracket%47
motorBike_frame%48
motorBike_rear-mud-guard%49
motorBike_rear-susp-spring-damp%50
motorBike_fairing-inner-plate%51
motorBike_clutch-housing%52
motorBike_radiator%53
motorBike_water-pipe%54
motorBike_water-pump%55
motorBike_engine%56
motorBike_rear-shock-link%57
motorBike_rear-brake-fluid-pot-bracket%58
motorBike_rear-brake-fluid-pot%59
motorBike_footpeg%60
motorBike_rr-wh-chain-hub%61
motorBike_rear-brake-caliper%62
motorBike_rider-helmet%65
motorBike_rider-visor%66
motorBike_rider-boots%67
motorBike_rider-gloves%68
motorBike_rider-body%69
motorBike_frame:0%70
motorBike_frt-fairing:001-shadow%74
motorBike_windshield-shadow%75
motorBike_fr-mud-guard-shadow%81
motorBike_fr-wh-brake-disk-shadow%83
motorBike_rear-mud-guard-shadow%84
motorBike_rear-susp-spring-damp-shadow%85
motorBike_radiator-shadow%86
motorBike_rear-shock-link-shadow%87
motorBike_rear-brake-fluid-pot-bracket-shadow%88
motorBike_rr-wh-chain-hub-shadow%89
)

From function layerParameters::layerParameters(const dictionary&, const polyBoundaryMesh&)
in file autoHexMesh/autoHexMeshDriver/layerParameters/layerParameters.C at line 932.
FOAM exiting

Greetings Monzer,

Please indicate which OpenFOAM version you are using and what were the exact steps you've taken to reach this error message.

Best regards,
Bruno

Hello Bruno,

thank u for ur reply :)

am using for FOAMpro 2.1.2. (at the University)
i did the following steps:

1- i created the block mesh with out problems
2- i decomposed the mesh
3- i wanted to create the mesh parallel (mpirun -np 6 foamProMesh -parallel)

it began to create to mesh but at the end i got that Error.

i tried a lot of things to solve the problem but i couldn't so i deactivated the Layer generation in snappyHexMeshDict...after that i didn't get that error and i created the mesh and the solving also...but as u know the solving without Layers ist not good especially for the turbulent Modelling.

i dont know where is the Problem :(

i have a question Bruno: is there a problem if i used an OpenFoam version to simulate a modell with different version of the (Foam files)

my greetings :)

Monzer

Hi Monzer,

The error message seems self-explanatory... it's telling you that "minZ" cannot be used for adding layers to it.
For example, check layers part in the "snappyHexMeshDict" file from OpenFOAM 2.1.x: https://github.com/OpenFOAM/OpenFOAM...xMeshDict#L199

As for compatibility... in theory, they should be compatible. All I know is that ICON's variant of OpenFOAM has features that the original version didn't have at the time each one was released.

Last but not least, I suggest that you contact your system's administrator at the University about support for FOAMPro from ICON; or contact ICON directly to ask for help, telling them which University you go to... hopefully they'll guide you through the process of how you can get help from them.

Best regards,
Bruno

Thanx Bruno for ur replay, i tried ur suggestion but it still not working, any way am grateful to u becuase ur replayed :)
mebay i have to ask the company a bout this problem.

my best greetigs to you

Monzer

[/PHP]hello Bruno,

could u help me to find the error. am trying to creat the mesh for the same example (a car in windtunnel), but i got this error message about the windtunnel boundaries:

--> FOAM FATAL IO ERROR:
wrong token type - expected word found on line 125 the label 0
file:/RUN/project2/system/autoHexMeshDict::surfaces::regions::name at line 125.
From function operator>>(Istream&, word&)
in file primitives/strings/word/wordIO.C at line 91.
FOAM exiting

u can see the Referred attachment (HexMeshDict)

thanx in advance :)

best greetings

Monzer

Hi Bruno,

i found the error and the mesh is correctly created :) , but i got an anther Error by solving (LES)

the Error is:

--> FOAM FATAL IO ERROR:
keyword surface is undefined in dictionary "::surfaces::surfaces"
file: ::surfaces::surfaces from line 194 to line 200.
From function dictionary::lookupEntry(const word&, bool, bool) const
in file db/dictionary/dictionary.C at line 410.
FOAM exiting


my question is, is there a dictionary with this name ????
i didn't hear about this Dictionary, could u plz give me an advice?

my best greetings :)


Monzer

Hi Monzer,

What's above that message?
And which application did you run to get that error?

Best regards,
Bruno

Hi Bruno,

am trying to solve a simulation (car in windtunnel).
i did at first the block mesh without problems, then a tried to create the mesh parallel into 8 processors, but i got this error message:

[3] --> FOAM FATAL ERROR:
[3] cell 22462 of level 0 does not seem to have 8 points of equal or lower level
cellPoints:6(2964 2981 1355 844 2404 2406)
pointLevels:6{0}
[3]
[3]
[3] From function hexRef8::setRefinement(const labelList&, polyTopoChange&)
[3] in file polyTopoChange/polyTopoChange/hexRef8.C at line 3638.
[3]
FOAM parallel run aborting
[3]
[3] #0 Foam::error::printStack(Foam::Ostream&)--------------------------------------------------------------------------
An MPI process has executed an operation involving a call to the
"fork()" system call to create a child process. Open MPI is currently
operating in a condition that could result in memory corruption or
other system errors; your MPI job may hang, crash, or produce silent
data corruption. The use of fork() (or system() or other calls that
create child processes) is strongly discouraged.
The process that invoked fork was:
Local host: vumca348 (PID 20184)
MPI_COMM_WORLD rank: 3
If you are *absolutely sure* that your application will successfully
and correctly survive a call to fork(), you may disable this warning
by setting the mpi_warn_on_fork MCA parameter to 0.
--------------------------------------------------------------------------
in "/share/openfoam/icon/FOAMpro-2.1.2/FOAM-2.1.2/lib/linux64GccDPOpt/libOSspecific.so"
[3] #1 Foam::error::abort() in "/share/openfoam/icon/FOAMpro-2.1.2/FOAM-2.1.2/lib/linux64GccDPOpt/libFOAM.so"
[3] #2 Foam::hexRef8::setRefinement(Foam::List<int> const&, Foam::polyTopoChange&) in "/share/openfoam/icon/FOAMpro-2.1.2/FOAM-2.1.2/lib/linux64GccDPOpt/libdynamicMesh.so"
[3] #3 Foam::meshRefinement::refine(Foam::List<int> const&) in "/share/openfoam/icon/FOAMpro-2.1.2/FOAM-2.1.2/lib/linux64GccDPOpt/libautoMesh.so"
[3] #4 Foam::meshRefinement::refineAndBalance(Foam::strin g const&, Foam::decompositionMethod&, Foam::fvMeshDistribute&, Foam::List<int> const&, double) in "/share/openfoam/icon/FOAMpro-2.1.2/FOAM-2.1.2/lib/linux64GccDPOpt/libautoMesh.so"
[3] #5 Foam::autoRefineDriver::featureEdgeRefine(Foam::re finementParameters const&, Foam::PtrList<Foam::dictionary> const&, int, int) in "/share/openfoam/icon/FOAMpro-2.1.2/FOAM-2.1.2/lib/linux64GccDPOpt/libautoMesh.so"
[3] #6 Foam::autoRefineDriver::doRefine(Foam::dictionary const&, Foam::refinementParameters const&, bool, Foam::dictionary const&) in "/share/openfoam/icon/FOAMpro-2.1.2/FOAM-2.1.2/lib/linux64GccDPOpt/libautoMesh.so"
[3] #7 Foam::autoHexMeshDriver::doMesh() in "/share/openfoam/icon/FOAMpro-2.1.2/FOAM-2.1.2/lib/linux64GccDPOpt/libautoMesh.so"
[3] #8 main in "/share/openfoam/icon/FOAMpro-2.1.2/FOAM-2.1.2/applications/bin/linux64GccDPOpt/foamProMesh"
[3] #9 __libc_start_main in "/lib64/libc.so.6"
[3] #10 __gxx_personality_v0 in "/share/openfoam/icon/FOAMpro-2.1.2/FOAM-2.1.2/applications/bin/linux64GccDPOpt/foamProMesh"
--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 3 in communicator MPI_COMM_WORLD
with errorcode 1.
NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on
exactly when Open MPI kills them.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
mpirun has exited due to process rank 3 with PID 20184 on
node vumca348 exiting without calling "finalize". This may
have caused other processes in the application to be
terminated by signals sent by mpirun (as reported here).
--------------------------------------------------------------------------

do u have an idea about this error?
thank you in advance :)
best greetings
Monzer

Quick answer: try using the motorBike 2.1.x case from this page: http://code.google.com/p/bluecfd-sin...untimes202_211
It has the ability to run in serial or parallel, depending on your options.
Do not forget to edit the file "Allrun" and change "snappyHexMesh" to "foamProMesh".

thanx Bruno for ur replay, i'll try it and tell u the results :)

Hello Bruno,

I have a question:

I generated 2 meshs for the same case (one with Star ccm+ und the another with OpenFoam), although I sat the same refinement levels for both, I got a difference number of cells (the mesh with Starccm+ generated 28 % more cells than with Openfoam)

do now any way to generate the same number of cells??

Thanx in advance

my best regards

Mizo

Hi Monzer,

It all depends on the kind of mesh you're trying to do on Star-CCM+. If I remember correctly, the similar method on Star-CCM+ to OpenFOAM's snappyHexMesh is the "trimmed mesh".

You didn't specify the reason why you want to do the meshes on both Star-CCM+ and on OpenFOAM, but if you want to compare solutions, then it's better to generate the mesh on OpenFOAM and export to Fluent mesh format and then import on Star-CCM+. For more information: http://openfoamwiki.net/index.php/FoamMeshToFluent

Best regards,
Bruno

thanx Bruno for your answer, actualy I want to compare the solution between OpenFoam and ccm+, but I will try your method :)

thank you again

best regards

Mizo

hello Bruno,

I have a big problem with Layer-generation
I cann't get complet Layers on the outside surface of the car,

the layer settings are the following:

growUpPatches false;
dumpLayerQuality true;
featureAngleGrowAround 100;
featureAngleTerminate 180;
expansionRatio 1.3;
finalLayerRatio 0.4;
minThickness 0.2;
nGrow 8;
featureAngleMerge 180;
nSnap 10;
nRelaxIter 5;
nSmoothSurfaceNormals 10;
nSmoothNormals 3;
nSmoothThickness 10;
maxFaceThicknessRatio 0.5;
maxThicknessToMedialRatio 0.3;
minMedianAxisAngle 80;
nBufferCellsNoExtrude 0;
terminationStrategy 1;
nLayerIter 50;
truncateFromWall true;
growConvexEdge true;
growConcaveEdge true;
redistributeManifold true;
nLayerIter 50;
allowSharedEdgeExtrusion true;

you can see the result in the attached foto.

i will be grateful for any help

thanx in advance

Mizo

Hi Mizo,

Sorry, unfortunately I don't know much about this topic. But I'll quote myself from yesterday:
Best regards,
Bruno