Tetramesh endless loop
Hi, whenever I run my tetramesh, there's a strong chance that I run into an endless loop. I am not sure why. You think you would have the same outcome if you run it twice or multiple times in a row. I have an enclosed volume and I have already built a shell using automesh. This is especially true when I two sets of this script in a row for different enclosed volumes.
Here is a part of my code:
*createmark components 2 "2_MeshTri_IntactEndAttachment" "2_MeshTri_Epiphyseal" \
"2_MeshTri_EpiMeta_CutPlane"; #this is an enclosed volume
*createstringarray 2 "elements_on" "geometry_on"
*isolateentitybymark 2 1 2
*createentity comps includeid=0 name="component1"
*clearmark components 1
*setvalue comps id=15 name=3_MeshTetra_Epiphyseal
*setvalue comps id=15 color=#00B050
*createstringarray 2 "pars: upd_shell fix_comp_bdr el2comp=1 aft vol_smth vol_smth2 tet_clps='0.500000,1.000000,0' max_size='2.000000,1.000000,1.79769e+308'" \
"tet: 35 1 1 2 0.8 0 262147 1"
*createmark components 2 "2_MeshTri_IntactEndAttachment" "2_MeshTri_Epiphyseal" \
"2_MeshTri_EpiMeta_CutPlane"
*tetmesh components 2 1 elements 0 -1 1 2
Answers
-
Hello William
You can try creating tetramesh for individual components first using the script. Maybe the tetramesh parameters for 1 of your components is causing the issue . You can also try to mesh the components manually using the tetramesh parameters set in the code.
Are you using namespaces in your tcl code ? The namespace command lets you create, access, and destroy separate contexts for commands and variables. It would avoid name collisions for variable which might be happening if you are running the script again. Probably there are some global variables which are still active when you run the script again. Deleting the existing namespaces before running script again can help
0
Altair Employee