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

can anyone explian the logic behind defining the vertices

Register Blogs Community New Posts Updated Threads Search

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
Old   November 10, 2010, 14:39
Default can anyone explian the logic behind defining the vertices
  #1
Member
 
Sandeep
Join Date: Jul 2010
Posts: 48
Rep Power: 15
gandesk is on a distinguished road
I am not able to figure out the direction chosen for defining the vertices in the example figure 5.6 explained in this following link.

http://www.openfoam.com/docs/user/blockMesh.php

may be they have not defined the lengths of the edges and now am not able to figure out the lengths from the vertices definition.

Thanks for the help
Sandeep
gandesk is offline   Reply With Quote

Old   November 10, 2010, 16:33
Default
  #2
Senior Member
 
David Gaden
Join Date: Apr 2009
Location: Winnipeg, Canada
Posts: 437
Rep Power: 22
marupio is on a distinguished road
Hi Sandeep,

Your question isn't very clear. I'm not sure what you are asking...

If it's about finding the length of the edges, then look at example blockMeshDict files. The points are listed first. The order in which they appear is their number.
Code:
    (0 0 0)        // point 0
    (0 0.1 0)     // point 1
    (0.1 0.1 0)    // point 2
    (0.1 0 0)     // point 3
Then when the blocks are defined, they are done according to the numbering in the figure you pointed out. CCW around the bottom, then CCW around the top, as seen from above. You can infer the length of each side by the points list above.

Lastly, you should pay attention to the axis directions defined (shown as x1, x2 and x3 in the diagram). The simpleGrading or edgeGrading lists are based on these axes, not a global coordinate system.

Is that what you wanted to know?
marupio is offline   Reply With Quote

Old   November 10, 2010, 18:08
Default
  #3
Member
 
Sandeep
Join Date: Jul 2010
Posts: 48
Rep Power: 15
gandesk is on a distinguished road
Quote:
Originally Posted by marupio View Post
Hi Sandeep,

Your question isn't very clear. I'm not sure what you are asking...

If it's about finding the length of the edges, then look at example blockMeshDict files. The points are listed first. The order in which they appear is their number.
Code:
    (0 0 0)        // point 0
    (0 0.1 0)     // point 1
    (0.1 0.1 0)    // point 2
    (0.1 0 0)     // point 3
Then when the blocks are defined, they are done according to the numbering in the figure you pointed out. CCW around the bottom, then CCW around the top, as seen from above. You can infer the length of each side by the points list above.

Lastly, you should pay attention to the axis directions defined (shown as x1, x2 and x3 in the diagram). The simpleGrading or edgeGrading lists are based on these axes, not a global coordinate system.

Is that what you wanted to know?

Hi david,


Thanks for the reply. Its my bad that i am not clear in my question. My question is that vertices for the figure 5.6(single block) are mentioned under the section 5.3.1.1 at 'the vertices' in the link i have sent. Now that am not able to visualize the same figure with the defined vertices. Also there are no lengths defined in the figure 5.6 and how the vertices were defined by taking 0.1 in one direction and 1 in another direction etc. Also for some vertices he has taken -ve value which looks impossible for the figure.

the vertices you have sent do not match with the list in the link. i wonder if you are refering to the same figure??

Also i want to know the x y and z directions are same as x1, x2 and x3 directions in the figure 5.6?

Thanks and regards
sandeep
gandesk is offline   Reply With Quote

Old   November 11, 2010, 00:18
Default
  #4
Senior Member
 
Nakul
Join Date: Apr 2010
Location: India
Posts: 147
Rep Power: 16
nakul is on a distinguished road
Hi,

The vertices that have been defined in the link are defined correctly.

x1, x2 and x3 can be assumed as x,y,z directions respectively.

The lengths are arbitary here as this is just an illustration of defining vertices in blockMeshDict. In an actual case the choice of vertices would be detrmined by the dimensions of your domain. Besides that figure is not an exact representation of those vertices.

You can safely assume the figure to be a representation to understand the procedure. If you are having trouble visualising these vertices try making your own rough figure on paper.
nakul 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
[blockMesh] Internal walls of zero thickness anger OpenFOAM Meshing & Mesh Conversion 23 February 6, 2020 18:25
[ICEM] Specifying Periodic Vertices Causes Strange Problem Josh ANSYS Meshing & Geometry 5 July 19, 2011 16:09
[ICEM] Specifying Periodic Vertices Causes Mesh Overlap Josh ANSYS Meshing & Geometry 10 July 8, 2010 02:39
correcting double vertices Tom Siemens 3 October 3, 2006 19:18
vread not storing all vertices Chris Siemens 6 May 18, 2005 02:50


All times are GMT -4. The time now is 01:39.