|
[Sponsors] |
[ICEM] what is wrong with my blocking "meshing parameters"? |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
November 25, 2009, 04:49 |
what is wrong with my blocking "meshing parameters"?
|
#1 |
Member
stb
Join Date: Sep 2009
Posts: 39
Rep Power: 16 |
i want to create hex mesh with ICEMCFD,two relative edges which seems to be parallel each other.
but actually, they are not showed when i select "to all parallel edges", just like 1w and 2w figture. i want to distribute the same nodes in the two edges. for example, when i set 3 nodes in second edge, the first edge became 15, but when i set 15 nodes in second edge, the first one became 27. i tried several methods such "linked bunching, to match the nodes number between these two edges, but unsuccessful. i want to know which causes this? any hint and reply is Extremely grateful. thank you all. Last edited by snailstb; November 25, 2009 at 05:11. |
|
November 28, 2009, 00:31 |
Implied splits.
|
#2 |
Senior Member
Simon Pereira
Join Date: Mar 2009
Location: Ann Arbor, MI
Posts: 2,663
Blog Entries: 1
Rep Power: 47 |
These edges are not as parallel as you think
In fact, I assume the second edge is a component of the first. When you increase the component, it adds to the other. The other edge that combines has 12 nodes... So anything you add to the second (3 or 15) is combined with the 12 to give your final counts on the first edge... Users get into this kind of trouble by using partial splits... It is easy for new users to forget that that the splits they make continue on even through the sections where you can't see them (we call these "implied splits"... It is just the nature of multiblock and can't really be avoided; if you split an index, it is split, even in the areas where you don't see the split, because otherwise the math wouldn't add up. When you make a new split in the previously hidden region, if it is right on the implied split, it will use that index, but if it is a little off, it will create a new split which may then propagate other implied splits, etc. I avoid this trouble by extending my splits thru the entire blocking (unless I really have a good reason not to)... Some say it is "messy", but at least I can see the splits and don't need to keep track of implied ones. If you do that (Split blocks => Extend split) here you will see the two splits and be able to collapse a layer. If you had done it initially (Split with all blocks displayed), the split would have already been at the second location and you wouldn't have felt the need to split again... (It was the the second split also created an "implied split" at the first location causing your trouble.) The fix is to find that edge with 12 nodes and adjust it... If you can't then extend some splits and see where they go. You may decide you want to fix it (collapse an index with merge verts and propagate) or if it is really bad, chalk it off to the learning curve and start again with fully propagated edges (split with all blocks visible) unless you are really sure what you are doing. Hope this answer doesn't confuse more than it helps. |
|
December 1, 2009, 08:32 |
|
#3 |
Member
stb
Join Date: Sep 2009
Posts: 39
Rep Power: 16 |
firstly, thank you, simon.
i split the first edge and second edge using "extend split" respectively. i find that implied splits between these two edges disappear.but the first edge index is not the second index. so i have no choose but create a new block once again, and split through this two deges in order to make them continuous. the implied edge disappear.when i select "copy to parallel edges", these two edges show parallel. i wonder when the implied edges will come out? splitting the block is the only way to avoid the implied edges? by the way, when i meshing, one error occour as follow: "A minor internal error has occurred. You may continue to work but if problems arise they may be related to this error. Try using the check/fix function to fix the problem The following message was designed to aid developers fix the problem: error meshing edge 276 283"what causes this error? how to solve it? and what is meaning about "edge 276 283", does it mean that edge 276 is the edge number? i can not find out how to know the edge number in ICEMCFD. thank you very much. Last edited by snailstb; December 1, 2009 at 11:04. |
|
December 1, 2009, 23:48 |
Edge vertex1 vertex2
|
#4 |
Senior Member
Simon Pereira
Join Date: Mar 2009
Location: Ann Arbor, MI
Posts: 2,663
Blog Entries: 1
Rep Power: 47 |
The edges are named by the verts on either side.
In the model tree, you can right click on vertex and turn on the option to show the numbers. Under the blocking tab, you can try the check/fix to see if it will sort out the problem. Not all of these errors will stop you from meshing. To get rid of issues due to implied splits, I usually use the option to "Extend splits". I have a development task in place to improve this and allow the select tool to lock onto hidden implied splits so that it can use the existing index instead of creating a new one; hopefully we can take care of that before the next release... |
|
December 2, 2009, 02:42 |
|
#5 | |
Member
stb
Join Date: Sep 2009
Posts: 39
Rep Power: 16 |
Quote:
thank you . |
||
December 2, 2009, 15:31 |
display_nodes
|
#6 |
Senior Member
Simon Pereira
Join Date: Mar 2009
Location: Ann Arbor, MI
Posts: 2,663
Blog Entries: 1
Rep Power: 47 |
Ok, sure, you can do anything with ICEM CFD, but there isn’t always a button.
Go to the model tree and make sure Vertices is off… But right click on Verticies and activate the display option for “Numbers”. Then type the display nodes command in the message window (in a fresh line at the bottom) and hit enter. display_nodes number n1 n2 … e.g: display_nodes number 25 display_nodes number 25 30 It will display just these verts (rather than all the vertices) with their vertex node numbers ( n1, n2) … on the screen. There are lot of hidden things you can do from Tcl. You can see them if you setenv HEXA_DEBUG 1. |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
udf error | srihari | FLUENT | 1 | October 31, 2016 15:18 |
CHT - interface regions? | rogbrito | ANSYS Meshing & Geometry | 6 | September 2, 2009 12:25 |
Mesh is created in blocking | Severin | CFX | 3 | September 18, 2007 10:02 |
Correct lift but wrong pressure drag - possible? | zx | Main CFD Forum | 4 | July 28, 2007 00:38 |
Pressure contour seems wrong??? | Harry Qiu | FLUENT | 1 | June 29, 2001 06:53 |