CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > Software User Forums > OpenFOAM > OpenFOAM Meshing & Mesh Conversion

[snappyHexMesh] Position of ref. box changes after snappy

Register Blogs Community New Posts Updated Threads Search

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
Old   December 17, 2009, 03:47
Default Position of ref. box changes after snappy
  #1
New Member
 
Patrick Wang
Join Date: Dec 2009
Location: Stuttgart, Germany
Posts: 26
Rep Power: 16
foam_noob is on a distinguished road
A friendly hello to all,

I am currently simulating the airflow over a model automobile. After creating several refinement boxes and running snappy, I noticed that the positions of the boxes had changed. One of the refinement boxes is supposed to be located at the rear of the vehicle. Instead it moved to the front. The file is of STL format.


Any help is appreciated and rewarded with digital Christmas cookies.


Patrick
Attached Images
File Type: jpg pic01.jpg (79.0 KB, 35 views)
foam_noob is offline   Reply With Quote

Old   December 24, 2009, 02:57
Default
  #2
Member
 
James Baker
Join Date: Dec 2009
Posts: 35
Rep Power: 16
fijinx is on a distinguished road
This may be a solution, or not! If you read the OpenFOAM manual Section 5.3.1 page U-134 it defines the coordinate system as the order of your vertices "the x1 direction is described by moving from vertex 0 to vertex 1;" and so on. So your x y z is not as you might expect unless you follow this convention. Also, I believe snappy reads the coordinate info from the blockmesh file, so if it's defined backward, it'll be on the wrong side.

--James
fijinx is offline   Reply With Quote

Old   January 12, 2010, 02:23
Default
  #3
New Member
 
Patrick Wang
Join Date: Dec 2009
Location: Stuttgart, Germany
Posts: 26
Rep Power: 16
foam_noob is on a distinguished road
Thank you for your reply James,

The STL file which I meshed with snappy is a closed 3d object. I only used the BlockMeshDict to create a box around the meshed STL file. Afterwards I defined the LocationInMesh to be inside the 3d object and created refinement boxes in the snappy file. The outer box created with BlockMeshDict was therefore deleted.

Now I have 2 questions.

1. Does the box created in BlockMeshDict influence the position of the refinement boxes created in snappy?

2. Does the origin of the coordinate system change after I mesh my STL file with snappy?

Thanks in advanced,

Patrick
foam_noob is offline   Reply With Quote

Old   January 13, 2010, 13:12
Default
  #4
Senior Member
 
Francesco Del Citto
Join Date: Mar 2009
Location: Zürich Area, Switzerland
Posts: 237
Rep Power: 18
fra76 is on a distinguished road
Strange, the closed STL files used for refining should not move around. What I can suggest is:
- check that it is in the position you expect, by loading it in paraFoam, together with the mesh.
- use a recent 1.6.x version, as this tool is under continuous evolution. A while ago I hit a problem with closed STL files and the mesher refining outside instead of inside them. This problem had been then fixed in one of the 1.6.x updates.

About your 2 questions, the answer is no for both!

Francesco
fra76 is offline   Reply With Quote

Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
I get different results when I scale the 'falling box' tutorial Hossein1 FLUENT 7 August 19, 2017 02:52
Hello,does anybody konw how to constraint 6DOF type box at specific position? shchao OpenFOAM Running, Solving & CFD 0 March 13, 2013 03:35
DPM UDF particle position using the macro P_POS(p)[i] dm2747 FLUENT 0 April 17, 2009 01:29
Immersol Simulation of a Heated Box Dong Phoenics 0 March 2, 2006 21:20
Combustion Convergence problems Art Stretton Phoenics 5 April 2, 2002 05:59


All times are GMT -4. The time now is 15:33.