|
[Sponsors] |
November 20, 2007, 05:39 |
hi everybody
i try to crea
|
#1 |
Guest
Posts: n/a
|
hi everybody
i try to create internalls walls in OF thanks to this thread: http://openfoamwiki.net/index.php/Howto_importing_fluent_mesh_with_internal_wall s i create my mesh with gambit but when i convert fluent mesh to openfoam it say me "Patch internal is internal to the mesh and is not being added to the boundary." but it don't create a set to use after splitmesh what am i doing wrong? what is the easy way to create a faceset ? bestregards |
|
November 20, 2007, 07:06 |
With the new versions of fluen
|
#2 |
Assistant Moderator
Bernhard Gschaider
Join Date: Mar 2009
Posts: 4,225
Rep Power: 51 |
With the new versions of fluentMeshToFoam (1.4+ I think) you have to explicitly trigger the writting of the sets with the -writeSets-option.
It has been asked before here. I will modify the Wiki-page accordingly Bernhard
__________________
Note: I don't use "Friend"-feature on this forum out of principle. Ah. And by the way: I'm not on Facebook either. So don't be offended if I don't accept your invitation/friend request |
|
November 20, 2007, 07:24 |
thanks bernhard
|
#3 |
Guest
Posts: n/a
|
thanks bernhard
|
|
November 20, 2007, 07:47 |
sorry but i have got this erro
|
#4 |
Guest
Posts: n/a
|
sorry but i have got this error
Create polyMesh for time = 0 #0 Foam::error::printStack(Foam:stream&) in "/home/gui/OpenFOAM/OpenFOAM-1.4.1/lib/linuxGccDPOpt/libOpenFOAM.so" #1 Foam::sigSegv::sigSegvHandler(int) in "/home/gui/OpenFOAM/OpenFOAM-1.4.1/lib/linuxGccDPOpt/libOpenFOAM.so" #2 Uninterpreted: [0xffffe420] #3 Foam::polyMesh::initMesh() in "/home/gui/OpenFOAM/OpenFOAM-1.4.1/lib/linuxGccDPOpt/libOpenFOAM.so" #4 Foam::polyMesh::polyMesh(Foam::IOobject const&) in "/home/gui/OpenFOAM/OpenFOAM-1.4.1/lib/linuxGccDPOpt/libOpenFOAM.so" #5 main in "/home/gui/OpenFOAM/OpenFOAM-1.4.1/applications/bin/linuxGccDPOpt/splitMesh" #6 __libc_start_main in "/lib/tls/i686/cmov/libc.so.6" #7 Foam::regIOobject::write() const in "/home/gui/OpenFOAM/OpenFOAM-1.4.1/applications/bin/linuxGccDPOpt/splitMesh" Erreur de segmentation (core dumped) i suppose it's because startface like it say in the wiki What mean "current number of faces" for the startface on the wiki?where i can found it? best regards |
|
November 20, 2007, 07:59 |
Have a look at the faces-file
|
#5 |
Assistant Moderator
Bernhard Gschaider
Join Date: Mar 2009
Posts: 4,225
Rep Power: 51 |
Have a look at the faces-file in polyMesh. At the start of the list it says how many faces are in the list. This is the "current number of faces". Use it for the startFace.
__________________
Note: I don't use "Friend"-feature on this forum out of principle. Ah. And by the way: I'm not on Facebook either. So don't be offended if I don't accept your invitation/friend request |
|
November 20, 2007, 09:04 |
Alternatively, you can try to
|
#6 |
Senior Member
Francesco Del Citto
Join Date: Mar 2009
Location: Zürich Area, Switzerland
Posts: 237
Rep Power: 18 |
Alternatively, you can try to use fluent3DMeshToFoam shipped with OF 1.4.1.
If the internal walls are correctly set up in Fluent (i.e., with a Shadow face), it should be able to convert the mesh. Francesco |
|
December 5, 2007, 08:35 |
Hi!
I have a GAMBIT mesh wi
|
#7 |
New Member
Mads Reck
Join Date: Mar 2009
Posts: 17
Rep Power: 17 |
Hi!
I have a GAMBIT mesh with internal walls. I have exported it to a Fluent .msh file, which reads nicely into Fluent. I want it into OpenFOAM. It works beautifully if I do nothing, but naturally the internal walls are missing from the simulation. So, I did the fluentMeshToFoam . <case> <meshfile.msh> -writeSets fluentMeshToFoam recognises the internal walls but skips them, as noted by the original poster: "Patch internal is internal to the mesh and is not being added to the boundary." I have multiple internal walls, defined as separate BC's in Gambit. I am trying to just get one of them active. So, in the boundary-file I add two entries: InternalA { type wall; nFaces A; startFace B; } InternalB { type wall; nFaces A; startFace B; } I do not think that the question of what values to put A and B to, is clearly defined anywhere, or in the wiki. It is not clear to ignorant little me, at least. I run the command splitMesh . <case> <gambit_bc_name> InternalA InternalB and it gives various error messages, depending on what values A and B have. Hence I have some questions, and please be accurate and comprehensible :-) Question 1: I guess A and B has to be the same in InternalA and in InternalB, right? Question 2: what should A be set to? Question 3: what should B be set to? I tried to set A to the first number which occurs in the sets/<gambit_bc_name> file. Makes no sense to me, as splitMesh should be able to read this number. I tried to set B to the first number which occurs in the faces-file (just after the header). I believe this is the total face count. Makes no sense to me, why I should be using that number, as it should be available to splitMesh already from the faces-file. Makes no sense, meaning that I do not understand at all what numbers should go in A and B. Any help is greatly appreciated, thanks a bunch! /Mads I got a sets-directory in my polyMesh directory. |
|
December 5, 2007, 08:54 |
Hi Mads,
Have you tried flu
|
#8 |
Member
Christian Winkler
Join Date: Mar 2009
Location: Mannheim, Germany
Posts: 63
Rep Power: 17 |
Hi Mads,
Have you tried fluent3DMeshToFoam, this should do it. Best regards Christian |
|
December 6, 2007, 03:51 |
Hi Christian,
fluent3dMeshT
|
#9 |
New Member
Mads Reck
Join Date: Mar 2009
Posts: 17
Rep Power: 17 |
Hi Christian,
fluent3dMeshToFoam never worked for me. But, slightly embarrassed I admit, that fluentMeshToFoam now works, it seems. Well, actually it still breaks, but now it ends on "new cannot satisfy memory request". The mesh is probably too big. I have plenty of RAM so I wonder if changing to the 64bit version will alleviate this...? Just, to clarify, since I may have caused some confusion, entries in the boundary file should read something like this: InternalA { type wall; nFaces 0; startFace <facecount>; } InternalB { type wall; nFaces 0; startFace <facecount>; } where <facecount> is the total number of faces, found in the file ./<case>/constant/polyMesh/faces as the first entry after the header. I have two follow-up questions, then. Q1: will 64-bit version alleviate the memory limit-issue? Q2: is fluent3DMeshToFoam the preferred choice? Thanks! /Mads |
|
December 6, 2007, 09:35 |
I had the same problem - I sho
|
#10 |
Member
Paul Mauk
Join Date: Mar 2009
Posts: 39
Rep Power: 17 |
I had the same problem - I should import a fluent-mesh with an internal wall. This never worked with fluentMeshToFoam, but after reading these messages I've tried fluent3DMeshToFoam - and I have to confirm - it works perfectly!!
|
|
December 10, 2007, 05:14 |
A quick hint on having multipl
|
#11 |
New Member
Mads Reck
Join Date: Mar 2009
Posts: 17
Rep Power: 17 |
A quick hint on having multiple internal walls (i.e. defined in each own BC set)?
Do I run splitMesh multiple times or do I have to include all internals in one BC set in Gambit? /Mads |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Use wall function on some walls (not all walls) | Mahdi10 | FLUENT | 1 | February 16, 2009 11:52 |
HTC for low Y+ walls | Tang | FLUENT | 0 | March 15, 2007 15:55 |
how to cluster walls | prc | Siemens | 2 | December 26, 2006 03:56 |
too many walls?? | matze | Siemens | 2 | March 1, 2006 07:13 |
Thermal B.C at walls | Riham | FLUENT | 3 | January 27, 2004 13:57 |