You can't use a wedge type on a non-wedge mesh.
Alter your points so they will form the wedge and than you can use the wedge type.

Sir, I wil be grateful if u explain in details, how to form wedge from the given points?
Thanks

Have a look at the user guide.
http://www.openfoam.com/docs/user/bo...hp#x24-1370014

This is NOT a problem with the utility this thread is about. I won't answer further unrelated questions.

There is a '(' missing at "empty center". Use a text editor that displays matching Parenthesis (Emacs for instance) that helps to spot such problems

Sir,,

I am sorry for disturbing u in another thread.
I didn't get anyother thread where i can put my query regarding axisymmetric geometry.
It will be great if u plz let help me for the following pbm..
I have developed the axisymmetric pbm with follwoing blockMesh file..
blocks
(
hex (0 1 2 3 0 1 6 7) (20 20 1) simpleGrading (1 1 1)
);

edges
(
);

patches
(
wall fixed
(
(3 7 6 2)
)
patch inlet
(
(0 0 7 3)
)
patch outlet
(
(2 6 1 1)
)
empty center
(
(1 1 0 0)
)
wedge front
(
(0 3 2 1)
)
wedge back
(
(0 1 6 7)
)
);
but getting follwoing error..
Creating block mesh from
"/home/javed/OpenFOAM/javed-1.6/run/wedge-new/constant/polyMesh/blockMeshDict"


Creating blockCorners

Creating curved edges

Creating blocks

Creating patches

Creating block mesh topology

Default patch type set to empty
#0 Foam::error::printStack(Foam::Ostream&) in "/home/javed/OpenFOAM/OpenFOAM-1.6/lib/linuxGccDPOpt/libOpenFOAM.so"
#1 Foam::sigFpe::sigFpeHandler(int) in "/home/javed/OpenFOAM/OpenFOAM-1.6/lib/linuxGccDPOpt/libOpenFOAM.so"
#2 Uninterpreted:
#3 Foam::wedgePolyPatch::initTransforms() in "/home/javed/OpenFOAM/OpenFOAM-1.6/lib/linuxGccDPOpt/libOpenFOAM.so"
#4 Foam::wedgePolyPatch::wedgePolyPatch(Foam::word const&, int, int, int, Foam::polyBoundaryMesh const&) in "/home/javed/OpenFOAM/OpenFOAM-1.6/lib/linuxGccDPOpt/libOpenFOAM.so"
#5 Foam::polyPatch::addwordConstructorToTable<Foam::w edgePolyPatch>::New(Foam::word const&, int, int, int, Foam::polyBoundaryMesh const&) in "/home/javed/OpenFOAM/OpenFOAM-1.6/lib/linuxGccDPOpt/libOpenFOAM.so"
#6 Foam::polyPatch::New(Foam::word const&, Foam::word const&, int, int, int, Foam::polyBoundaryMesh const&) in "/home/javed/OpenFOAM/OpenFOAM-1.6/lib/linuxGccDPOpt/libOpenFOAM.so"
#7 Foam::polyMesh::polyMesh(Foam::IOobject const&, Foam::Xfer<Foam::Field<Foam::Vector<double> > > const&, Foam::List<Foam::cellShape> const&, Foam::List<Foam::List<Foam::face> > const&, Foam::List<Foam::word> const&, Foam::List<Foam::word> const&, Foam::word const&, Foam::word const&, Foam::List<Foam::word> const&, bool) in "/home/javed/OpenFOAM/OpenFOAM-1.6/lib/linuxGccDPOpt/libOpenFOAM.so"
#8 Foam::blockMesh::createTopology(Foam::IOdictionary &) in "/home/javed/OpenFOAM/OpenFOAM-1.6/applications/bin/linuxGccDPOpt/blockMesh"
#9 Foam::blockMesh::blockMesh(Foam::IOdictionary&) in "/home/javed/OpenFOAM/OpenFOAM-1.6/applications/bin/linuxGccDPOpt/blockMesh"
#10 main in "/home/javed/OpenFOAM/OpenFOAM-1.6/applications/bin/linuxGccDPOpt/blockMesh"
#11 __libc_start_main in "/lib/tls/i686/cmov/libc.so.6"
#12 _start at /usr/src/packages/BUILD/glibc-2.9/csu/../sysdeps/i386/elf/start.S:122
Floating point exception..

Thanks for the help...

Open you own.
We have misused this thread.
Sorry

checkMesh Error when using "axis offset"
 

Dear Foamers,
I'd like to resume this thread and come back to the checkMesh error "Failed 1 mesh checks" which had been previously reported with cases where the axis is not aligned with the patch (axis offset feature). For example:
----------
***Number of edges not aligned with or perpendicular to non-empty directions: 96154
<<Writing 74460 points on non-aligned edges to set nonAlignedEdges
----------
I've got the same problem with a concentric cylinder set-up where the inner cylinder rotates and the outer is fixed (Taylor-Couette system with fluid-filled ring gap).
Do we have to use the collapseEdges utility with such cases (in my case collapseEdges doesn't seem to do anything and the checkMesh issue persists), or can the mesh be used "as is" after using makeAxialMesh??
I'd greatly appreciate any help!
Have a nice day
Bengt

I don't think that MakeAxialMesh works with openFOam 1.7.

I have to simulate a barrel of a gun, as you can see in screen shots (attachments), i have one cell thick in y i direction, but in my boundary file i don't see how to define a wedge, SO has an idea, help plzz
13
(
tube5
{
type wall;
nFaces 30;
startFace 60334;
}
tube4
{
type wall;
nFaces 3;
startFace 60364;
}
FREIN3
{
type wall;
nFaces 70;
startFace 60367;
}
FREIN2
{
type wall;
nFaces 15;
startFace 60437;
}
FREIN1
{
type wall;
nFaces 30;
startFace 60452;
}
Frein
{
type wall;
nFaces 20;
startFace 60482;
}
Pressure_inlet
{
type patch;
nFaces 30;
startFace 60502;
}
Tube3
{
type wall;
nFaces 21;
startFace 60532;
}
Tube2
{
type wall;
nFaces 10;
startFace 60553;
}
Tube1
{
type wall;
nFaces 139;
startFace 60563;
}
Axe
{
type symmetryPlane;
nFaces 215;
startFace 60702;
}
Pressure_outlet
{
type patch;
nFaces 209;
startFace 60917;
}
frontAndBackPlanes
{
type empty;
nFaces 60730;
startFace 61126;
}
)

Greetings,

Help please, you can see my problem here (7th post)
http://www.cfd-online.com/Forums/ope...c-problem.html


Abdel.

Simulation results
 

Hi all

First of all thanks to Bernhard for the great utility.

Have have been using it a bit in order to get a 2D axisymmetrc simulation running. I started off with the example included in the utility, and modified it a bit. I added an outlet, and added a slight inflow into the domain. The model is based on this concept:

http://i1028.photobucket.com/albums/...edge_Assem.jpg


Flow enters the domain tangentially and exits axially. The flow is thus axisymmetric, and I'm just modelling a section of it.

I'm using the IcoFoam solver, and the solution converges well. However, the results don't look right. See below:

http://i1028.photobucket.com/albums/...et/wedge-1.jpg

It seems the flow is exiting the domain with almost no swirl. It also seems the inlet swirl is quickly dissipated. I'm quite sure this is not correct, since there is quite a lot of angular momentum introduced at the inlet, and this momentum must be conserved. I would expect the outlet flow to still have a lot of swirl.

Can anybody suggest any ideas?

Have you checked whether what paraFoam shows you is consistent with what is on the disk. At least for older versions (havn't done wedges since) for glyphs the component "out of the wedge" was removed. What you had to do was use the "Cell Centers"-filter (then you saw nothing) and for that result use "Glyphs" (due to the small picture I'm not 100% sure whether there is a flow "out of the wedge" outside of the Inlet, so this might be not too helpful)

Bernhard

Hi Bengt,
I've run in to this same issue as well. I'm beginning to think that this is an accepted issue. If you look at the tutorial ~/OpenFOAM/sunny-1.6.x/run/tutorials/multiphase/interFoam/les/nozzleFlow2D which also uses an axisymmetric mesh, the same error shows up when you run checkMesh. Whether or not that makes it OK, I'm not sure, but at least it is clear that the provided tutorials have the same issue.

Sunny

hi,

is there a solution for the problem by which makeAxialMesh isn´t running if there are any libs or functions in the controlDict?

Regarding the groovyBC and the simpleFunctionObjects...

neewbie

The problem is that makeAxialMesh only loads the mesh as a polyMesh (it doesn't need more for what it has been doing) while most functionObjects need a fvMesh. The quickest solution is to go to the controlDict, comment out the functions and the libs entry, run MAM and then restore the controlDict to its old glory. Or if you have pyFoam installed run it like this

pyFoamRunner.py --remove-libs --remove-functions makeAxialMesh

which does the editing/restoring for you.

OR there is the possibility to turn of the functionObjects in the source code of the utility (but I'll have to look that up, maybe will do it, but you'll probably need a solution right now)

Bernhard

thanks,

this is exactly as i did.
Some mv and cp in a startscript did the job.

neewbie

btw...
can makeAxialMesh be used for multipleRegion meshes?

neewbie

sorry...
i´ve started a new thread on this...

does this work for foam 1.7
 

I have been trying to make axisymmetric geometry the documentation says this utility is for V1.4 and 1.5. I am using V1.7. has anyone tried this in 1.7 before I put too much effort into altering my geometry.

conversion 2Dmesh to axisymmetric
 

Hi everyone,

I imported my mesh (generate in fluent) file to a FOAM mesh successfully using fluentMeshToFoam command.

and I would Converting a 2Dmesh to axisymmetric, I downlowd the makeAxialMesh and it's compiling successfuly.
my question:What are the other commands to perform the conversion?
I found the answer in a forum on the link, but it's removed:)"Contrib MakeAxialMesh - OpenFOAMWiki"
I work OpenFoam 1.7.1 under UBUNTO
thank you for your help

What do you mean with "it's removed". Don't know the posing you're referring to, but checking with
http://lmgtfy.com/?q=openfoamwiki+makeaxialmesh&l=1
gives the right page

Bernhard

I am afraid that I cannot quite understand what you are asking. Do you mean "What other commands are involved in the process" ?

If you were starting from Gambit, for example, this is a three step process.
1) Convert your 2D Gambit mesh to OpenFOAM format
2) Convert the 2D mesh to a 1-cell deep axial mesh with makeAxialMesh
3) Use collapseEdges to remove the degenerate edges along the axis.

I'll quote from the wiki page about step #3.

"The collapseEdges utility should remove these degenerate edges (and the faces that go with it) and stitch the mesh together. For an application like this, you would want to use collapseEdges with a very small length scale argument and an angle argument near 180 degrees."

Regards,
DPS

Hi gschaider,

Thank you very much for the website, I can access to this one :)

Thank's a lot

Hello Gschaider
 

Hello Gschaider,

I am new at OpenFoam environment. I would like to ask you that...Is it possible to switch axisymmetric BC in OpenFoam ?

BR,
Gitesh

Runing Test case step by step
 

Hello Dear Foamers:)
Especially Dear Bernhard;)

I want to run testCase and doing below steps:
(I think this thread need a post that describe process step by step like this:()

(My OF version: openFoam 1.5-dev)
1-Download files of utility and after Compile makeAxilMesh using "wmake all"---> well done
2-Download "testCase" files
3-Go to testCase Directory
4-Run "blockMesh"----> well done
5-Run "makeAxialMesh -axis movingWall -wede frontAndBack -overwrite" --->well done
6-Run "paraFoam" and can see wedge shape grid
7-Run "collapseEdges 0.0001 175 -overwrite" shows below message:


Create time

Create polyMesh for time = 0

Merging:
edges with length less than 0.0001 meters
edges split by a point with edges in line to within 175 degrees

Collapsing 21 small edges
Morphing ...
Collapsing 0 small edges
Collapsing 0 in line edges
Max face area:4.36194e-05
Collapse area factor:1e-09
Collapse area:4.36194e-14
Collapsing 0 small high aspect ratio faces
Writing collapsed mesh to time 0
End


8-Run "icoFoam" and it runs without any problem!

-----------------------------------------------------
-----------------------------------------------------
Queations:

1))Is my Steps all True? Isn't anything wrong?

2))What does this Case physically show ? Only a full closed cylinder whitout any flow?

3))Any body can mail me a test case for Flow in a simple axisymmetric pipe?
I will appreciat if anybody upload a pipe case for using everyone for test beside this simple and maybe unused case :(

-------------------------------------------------------
-------------------------------------------------------
shariatkhah@gmail.com

Thanks:)

If we're talking about the same case (the one in the SVN) then it is basically a driven cavity where the axis does not go through the edge of the geometry. Therefor collapsing is not needed (for that case)

Hello Foamers,

I am trying to use makeAxialMesh to convert mt 2D pipe into a 3D one. I'm using the steps listed below, I believe they are all correct?

01) Put rotationDict into the system
02) Run $ makeAxialMesh -axis center -wedge frontAndBack (This created a folder 1)
03) Backup constant/polyMesh into constant/polyMesh-2Dorg
04) $ mv 1/polyMesh constant/.
05) $ rm -rf 1
06) $ unset FOAM_SIGFPE
07) run $ collapseEdges 1e-8 180
08) Backup constant/polyMesh into constant/polyMesh-2DAxiorg
09) $ mv 1/polyMesh constant/.
10) $ rm -rf 1
11) checkMesh

When running checkMesh I get the following error and I'm not sure how to fix it.

Checking geometry...
Overall domain bounding box (0 0 0.47819) (25 0.5 0.52181)
Mesh (non-empty, non-wedge) directions (1 1 0)
Mesh (non-empty) directions (1 1 1)
Wedge frontAndBack_pos with angle 2.49748 degrees
***Wedge patch frontAndBack_pos not planar. Point (0.25 0.0717724 0.518679) is not in patch plane by 5.12279e-07 meter.
Boundary openness (1.66027e-20 0 -6.63727e-18) OK.
Max cell openness = 9.3096e-17 OK.
Max aspect ratio = 7.50424 OK.
Minumum face area = 0.00020772. Maximum face area = 0.0172689. Face area magnitudes OK.
Min volume = 5.193e-05. Max volume = 0.000363295. Total volume = 0.272622. Cell volumes OK.
Mesh non-orthogonality Max: 0 average: 0
Non-orthogonality check OK.
Face pyramids OK.
Max skewness = 0.330802 OK.
Coupled point location match (average 0) OK.

Failed 1 mesh checks.

End

Any help or a push in the right direction would be helpful.

Thanks,
Tom

Have you tried checkMesh after MAM (makeAxialMesh) too? Just to make sure that the problem was not introduced by collapseEdges.

Also try this: if writeFormat in controlDict is set to ascii then try setting writePrecision to higher number (12 or so). Reset after the mesh manipulation

Hi Bernhard,

Thanks for your quick reply. I just ran checkMesh after MAM and I have the error as shown below. My writeFormat is ascii and I have tried changing the writePrecision from 6 up to 24.

Checking geometry...
Overall domain bounding box (0 0 0.478190306317332003427367) (25 0.5 0.521809693682668052083784)
Mesh (non-empty, non-wedge) directions (1 1 0)
Mesh (non-empty) directions (1 1 1)
Wedge frontAndBack_pos with angle 2.49762356858921519275896 degrees
Wedge frontAndBack_neg with angle 2.49762356858906953149813 degrees
All edges aligned with or perpendicular to non-empty directions.
Boundary openness (4.17361820446499761229836e-21 0 -6.63727839475413910092676e-18) OK.
Max cell openness = 9.63289024144322500065237e-17 OK.
Max aspect ratio = 7.50427090517739259212249 OK.
***Zero or negative face area detected. Minimum area: 0
<<Writing 100 zero area faces to set zeroAreaFaces
Min volume = 0.000140685850519272698721726. Max volume = 0.00080548557824244697029431. Total volume = 0.333707879182710054344341. Cell volumes OK.
Mesh non-orthogonality Max: 87.4369863522491215235277 average: 17.0098551033114944175395
*Number of severely non-orthogonal faces: 87.
Non-orthogonality check OK.
<<Writing 87 non-orthogonal faces to set nonOrthoFaces
***Error in face pyramids: 187 faces are incorrectly oriented.
<<Writing 187 faces with incorrect orientation to set wrongOrientedFaces
***Max skewness = 7.96818897130483527746492, 98 highly skew faces detected which may impair the quality of the results
<<Writing 98 skew faces to set skewFaces
Coupled point location match (average 0) OK.

Failed 3 mesh checks.

End

Increasing the writePrecisioin to 12 reduce the failed mesh checks from 4 to 3, but further increases did not change anything. Could this be a fundamental problem with my 2D mesh?

Tom

15 digits is the maximum that makes sense (double-precision doesn't store more). The three "problems" are exactly what collapseEdges takes care of (the axis-patch "degenerated" to a collection of zero-area faces - that is the first error. The others are following from this)

The fourth error you're referring to is the "planar"-error in your original posting, right? And a subsequent collapseEdge should remove the other 3

Wooooooot!!! Everything works XD

Thanks Bernhard!

Tom

Great. Could you add a few words about this (write precision and errors to be ecpected in checkMesh) to the Wiki-page of makeAxialMesh so that the knowledge is preserved for future generations?

Hello Tom,

To support Bernhards post, could you please give some words about your adjustments?

Did you get rid of the "Wedge patch frontAndBack_pos not planar"-error by increasing the writePrecision? I get this error too, after MAM with write precision to 15.. But for me, this is the only error..

I get the error (from MAM)
and then checkMesh reports
Thanks!

The problem here is that MAM assumes that the axis is centrally aligned to the original mesh in respect to the "ignored" coordinate (the one where only one cell layer eists). Otherwise you will get an asymetric wedge (faces are collapsed towards the axis) - have a look in paraview and you'll see what I mean. Either move the mesh (in your case preferable) or the axis so that this requirement is satisfied.

Hi Bernhard,

thanks for your comment.
i tried that too, but then I am getting a floating Point Exception in checkMesh, although the mesh "looks good" in paraview.. I keep on digging where it comes from, but maybe it wont work for my mesh..

Have you removed the faces of size 0 with collapseEdges? But even then checkMesh shouldn't crash

Hi Berhnhard,

I think the error came due to an inconsistency with the boundary definitions in the poly Mesh..
After some tries with the parameters for collapsEdges it seems that there is no error anymore.. can't believe it yet ;)

Thanks!

plz help me
 

Hi dear Bernhard Gschaider!

I used 2Daxisymmetric for openFoam,and for this used makeAxialmesh and coolapseEdge to make wedge type for boundary.
I make it,
but my result after run is not correct and differrent with 3Dmodel.

if what i did in modelling 2DAxisymetric is not correct please tell me???
Thanks a lot.

plz help me???
 

dear Foamers.
I have used 2Daxisymmetric for openFoam.
for this reason used :
1)makeAxialMesh -axis axis.4 -wedge frontAndBackPlanes
2)collapseEdges 1e-8 180
to make wedge type for boundary.

after do above,added for me 2 files.(seen in pic 1)

I have copied polyMesh from file:2e-08 to polyMesh in constant(seen in pic 2),and then I have deleted files: 1e-08 and 2e-08 .(seen in pic 3)

and after those I have correct B.C in file:0.
Then run paraFoam and (seen pic 4)
Is it my way true???


but my result after run is not correct and differrent with 3Dmodel.
if my work in modelling 2DAxisymetric is not correct please tell me???

Thanks for your attention:)

The way you do it looks alright and the geometry definitely looks wedgy. By using the -overwrite-option you can avoid the copying business.

In which way do the results differ?

Thanks.
 

Hi Bernhard Gschaider.
Thanks for your answer Bernhard,My problem was solved.
thanks alot.