CFD Online Discussion Forums

CFD Online Discussion Forums (http://www.cfd-online.com/Forums/)
-   OpenFOAM Other Meshers: ICEM, Star, Ansys, Pointwise, GridPro, Ansa, ... (http://www.cfd-online.com/Forums/openfoam-meshing-other/)
-   -   fluentMeshToFoam error (http://www.cfd-online.com/Forums/openfoam-meshing-other/67388-fluentmeshtofoam-error.html)

bucksfan August 13, 2009 11:26

fluentMeshToFoam error
 
Hello,

Every time I try to mesh anything that I just built with gambit using the fluentMeshToFoam command it always gives me the same error,

Problem : cannot find a single face in the mesh which uses vertices 4(0 2 400 399)

From function findFace(const primitiveMesh&, const face&)
in file fluentMeshToFoam.L at line 858.


I was wondering if there was a way around this or if i should be using a different version of if there was something that I could to get around this.

Thanks

gschaider August 13, 2009 12:14

Quote:

Originally Posted by bucksfan (Post 226253)
Hello,

Every time I try to mesh anything that I just built with gambit using the fluentMeshToFoam command it always gives me the same error,

Just to clarify (because in my opinion you mixed some things up in that sentence):
- you built the geometry in Gambit
- you meshed it in Gambit
- exported the mesh to an MSH file
- now you try to convert it using fluentMeshToFoam

Step 2 is essential (fluentMeshToFoam wants a complete mesh I think)

Quote:

Originally Posted by bucksfan (Post 226253)
Problem : cannot find a single face in the mesh which uses vertices 4(0 2 400 399)

From function findFace(const primitiveMesh&, const face&)
in file fluentMeshToFoam.L at line 858.


I was wondering if there was a way around this or if i should be using a different version of if there was something that I could to get around this.

I'm not aware of any special version dependence of this converter. Are there any special features in all your meshes?

Two tips:
- try the other convert fluent3dMeshToFoam
- build the simplest possible Geometry (for instance a cube), mesh it and then try the converter on it. If that works add the particular specialities of your mesh to it until it breaks

Bernhard

bucksfan August 17, 2009 10:33

It breaks at the cube. I'm trying to create an empty room with an inlet on the upper right wall for a flow and an outlet on the ceiling. But even when I just made it a simple cube with none of the patches it won't even convert over to foam format.

bucksfan August 17, 2009 10:35

And yes sorry the steps that you listed is exactly what I did. Sorry I was a little frusterated when I wrote the first post so it probably wasn't that coherent.

gschaider August 17, 2009 14:20

Quote:

Originally Posted by bucksfan (Post 226585)
It breaks at the cube. I'm trying to create an empty room with an inlet on the upper right wall for a flow and an outlet on the ceiling. But even when I just made it a simple cube with none of the patches it won't even convert over to foam format.

And you tried the other converter, too? Strange. The cells are nothing fancy? Hexes and/or tets?
But those converters usually work without big problems.

Another question: you're running Gambit on Linux, right? I mean: the msh-file has never been handled by a Windoze-machine? Because there are problems with that (the old Newline-problem)

Quote:

Originally Posted by bucksfan (Post 226586)
And yes sorry the steps that you listed is exactly what I did. Sorry I was a little frusterated when I wrote the first post so it probably wasn't that coherent.

The thing is that there were occasions were everyone was trying to help people assuming that the problem happened "at the end" when the problem already occured "in the beginning" because everyone assumed "that can't be the problem"

bucksfan August 18, 2009 08:41

Well I'm running an ssh on a windows box to a linux cluster so it was techinically never really touched by windows really. And no the cells are all normal, it doesn't have to be oriented any certian way does it? The other mesh i created didn't. And fluent3DMeshToFoam isn't working either. :(

gschaider August 19, 2009 04:18

Quote:

Originally Posted by bucksfan (Post 226689)
Well I'm running an ssh on a windows box to a linux cluster so it was techinically never really touched by windows really.

Just checking. Because I think in the past there were problems with MSH-files generated with Windows-versions of Gambit and/or being opened and saved with the Notepad. But run dos2unix on the file to be sure
Quote:

Originally Posted by bucksfan (Post 226689)
And no the cells are all normal, it doesn't have to be oriented any certian way does it?

Not really. General polyeders would be a problem, I guess. But Gambit doesn'T create those anyway
Quote:

Originally Posted by bucksfan (Post 226689)
The other mesh i created didn't. And fluent3DMeshToFoam isn't working either. :(

Have you ever tried fluentMeshToFoam on the msh-file in the icoFoam/elbow-tutorial?

bucksfan August 19, 2009 08:16

Ok well i tried the dos2unix and i am still having the same error pop up. And I just tried running it in icoFoam and it worked perfect. I'm just not understanding why this is popping up at all. Because its only a very very simple mesh.

bastil August 19, 2009 15:22

Just one more hint: For both converters meshes nedd to be saved in ASCII-Foramt, binary format is not supported.

Regards

gschaider August 21, 2009 09:42

Quote:

Originally Posted by bastil (Post 226883)
Just one more hint: For both converters meshes nedd to be saved in ASCII-Foramt, binary format is not supported.

If I understood his last remark correctly, the mesh gets converted, he just gets a warning message.

@bucksfan: could you post a small mesh to have a look at it?

milos October 1, 2009 08:26

Quote:

Originally Posted by gschaider (Post 226259)
Just to clarify (because in my opinion you mixed some things up in that sentence):
- you built the geometry in Gambit
- you meshed it in Gambit
- exported the mesh to an MSH file
- now you try to convert it using fluentMeshToFoam

I did all this and it reports the same thing (can't find vertices...). First I thought it was due a complex geometry, so I made a simple pipe, divided it into two volumes, meshed them (with different steps), then merged them in order to get a coherent single volume. Exported it in .msh format and fluentMeshToFoam reports the mentioned 'vertices' error.

I also tried fluent3DMeshToFoam and it worked, but it's of no use since no boundaries are specified.

My Gambit runs on Windows XP.

Any additional suggestions or ideas?

Thnx a million!

gschaider October 9, 2009 13:03

Quote:

Originally Posted by milos (Post 231154)
I did all this and it reports the same thing (can't find vertices...). First I thought it was due a complex geometry, so I made a simple pipe, divided it into two volumes, meshed them (with different steps), then merged them in order to get a coherent single volume. Exported it in .msh format and fluentMeshToFoam reports the mentioned 'vertices' error.

I also tried fluent3DMeshToFoam and it worked, but it's of no use since no boundaries are specified.

My Gambit runs on Windows XP.

Any additional suggestions or ideas?

And you treated the msh-file with dos2unix (that was discussed above!!). That is important if you use an operating system that is not the proper choice for CAE

Bernhard

milos October 12, 2009 04:24

Yeah, I tried it several times. I hope the command should look like this:

dos2unix nameofthefile.msh

I also tried:

dos2unix nameofthefile.msh -c iso newnameofthefile.msh

, but it says that '-c' is not an option.

Still doesn't work.

gschaider October 12, 2009 12:07

Quote:

Originally Posted by milos (Post 232198)
Yeah, I tried it several times. I hope the command should look like this:

dos2unix nameofthefile.msh

I also tried:

dos2unix nameofthefile.msh -c iso newnameofthefile.msh

, but it says that '-c' is not an option.

Still doesn't work.

Sorry for asking that. It was the only guess I had from that information. And as the other converter works it looks like you HAVE a volume-mesh (the absence of which throws a similar error message AFAIR)

Bernhard

milos October 13, 2009 05:00

It is a volume mesh... Fortunately, it's not necessary for now to merge and refine different meshes in multiple volumes, but I would like to know how to overcome that problem for future situations.

Thnx for the effort. If anyone comes up with any ideas, please let me know.

Milos


All times are GMT -4. The time now is 21:07.