|
[Sponsors] |
[ICEM] Issue with blocking vertex and replay file |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
February 5, 2015, 16:26 |
Issue with blocking vertex and replay file
|
#1 |
New Member
Join Date: Jun 2014
Posts: 13
Rep Power: 12 |
Hello,
I am trying to make a replay file of a geometry that I want modify and mesh many times. I am able to do the blocking and save the replay file the first time but what happens is as follows: I slightly modify the geometry, then I run the replay file again but it fails because the number of some vertex change (just a couple of vertex but it makes it wrong). I do not know if I am doing something wrong in the script file but it seems strange that depending on the geometry (modified just a bit) the number of the vertex change. I attach the geometry files and the replay script, anybody have an idea about what could be happening? Thank you in advance. replay_structured_06.txt primary_nozzle_01.txt secondary_nozzle_01.txt simmetry.txt.txt |
|
February 6, 2015, 16:30 |
|
#2 |
New Member
Join Date: Jun 2014
Posts: 13
Rep Power: 12 |
Hello, doing some research in posts and in Icem I realised that there are some hidden vertex which can be showed by the command "display_nodes number xx". I realised because when I was trying to select an edge for the split block the number of the vertex defining the edge were different to those shown in the screen.
Does anybody know something about that issue? |
|
May 27, 2015, 09:33 |
|
#3 |
New Member
Sune Niemann
Join Date: Aug 2011
Posts: 18
Rep Power: 15 |
The way that the replay script is written you should run it with an empty part loaded. If any points are already created the script will append the new points which will then have new names.
One way of solving your problem would be to delete all points when running the script, something like: Code:
foreach pnt [ic_geo_lookup point all] {ic_delete_geometry point names $pnt 0 1} If your problem is not with the points but with the block vertices, I would need to know which line produces the error. |
|
|
|