[Katt]

Hi guys;

Out of intense curiosity, how to generate motorBike.eMesh in foam-Extend 1.6/ 3.2.

I could generate the .eMesh using normal openFoam version (3.x) using "surfaceFeatureExtract" that reads from system/surfaceFeatureExtractDict.

Somehow, the .eMesh generated in foam-extend is seen to be inconsistent with what snappyHexMesh can work with.
I used the following command:
surfaceFeatureExtract -includedAngle 150 constant/triSurface/motorBike.stl constant/triSurface/motorBike.eMesh

After struggling for quite long, I do realize the working structure of surfaceFeatureExtract has changed between OF2.2-2.3 versions whereas at-least exporting the mesh from OF3.x to FE1.6 doesnt work (complaints about errors in reading faces file and so on).

Thanks;
KT

[Katt]

Just an update for what happened to me,

I am not yet sure what really does "surfaceFeatureExtract" do in foam-extend 1.6/3.2.

In parallel, I do always have a relatively latest release of OpenFOAM (3.x), where the surfaceFeatureExtract works with the "surfaceFeatureExtractDict" file placed in the system.

First try: Everything in OF3.x works, but the file structure between OF3.x and FE1.6/3.2 are different. So, after matching the files and a few keywords, I tried seeing the output mesh from FE1.6/3.2 but I got a few binary format errors/ complaints.

Second try: OF3.x writes the "faces" output of blockMesh in a binary format (I guess it is default). So, I wanted to see what explicitly is going wrong. So, transformed the binary output to ascii by changing the "system/controlDict/writeOutput" to ascii.

Then I run, surfaceFeatureExtract-> blockMesh -> snappyHexMesh -overwrite and export the mesh to FE1.6 by managing and ordering the files as required to be read by FE1.6 and it finally works.

I guess, the way is to mesh in latest versions of OF and export the meshed domain to FE (older versions).