Miss I something with hm_measureshortestdistance ?
Hello everybody,
I wanted to find the shortest distance between 2 components (the red and blue ones on 1.png) so I used the tool "Shortest Distance" and selected the surfaces by components (2.png and 3.png).
I get a very surprising result (4.png) which is not what I expected when I only select the 2 closest surfaces and not all the surfaces by component (5.png). I get the same thing with tcl scripting. Moreover I get different results with
*createmark surfs 1 "by comp" $compA
*createmark surfs 2 "by comp" $compB
hm_measureshortestdistance surfs 1 0 surfs 2 0 0
> 1.1180339887499 0.5 -1 0 186 553.777047411 -321.215545654 -742.620963493 41 554.277047411 -322.215545654 -742.620963493</code></p> <p>and</p> <p><code> *createmark surfs 1 "by comp" $compA
*createmark surfs 2 "by comp" $compB
hm_measureshortestdistance surfs 2 0 surfs 1 0 0
> 0.99999999999989 -0.99999999999989 0 0 187 554.777047411 -322.215545654 -742.620963493 2 553.777047411 -322.215545654 -742.620963493
Finally, I get the result I expect if I only select the 2 closest surfaces with tcl scripting </code><code>
> 0.5 0.5 0 0 2 553.777047411 -322.215545654 -745.370963493 41 554.277047411 -322.215545654 -745.370963493
Has anyone ever experienced this kind of strange result? Miss I something with the use of hm_measureshortestdistance ?
Thanks a lot,
Florian
Best Answer
-
Hi Florian,
I've reported a bug to the Altair team regarding hm_measureshortestdistance in 2022.3. I recommend trying in 2022.2 to see if that fixes the issue. Or hopefully it will be fixed in 2023 when that is released.
-Bocaj22
0
Answers
-
Hi Florian,
I've reported a bug to the Altair team regarding hm_measureshortestdistance in 2022.3. I recommend trying in 2022.2 to see if that fixes the issue. Or hopefully it will be fixed in 2023 when that is released.
-Bocaj22
0