Surface IDs keep changing

Akshay Manthekar
Akshay Manthekar Altair Community Member
edited April 2022 in Community Q&A

Hi all,

I am trying to automate fillet nodes detection and splitting the surface as shown in the figure. The code will detect nearest node as you can see in the command window (in fig) and split the surface. The PROBLEM is that surface IDs keep changing after every split and the code is throwing error. Can anyone help me with this? Your help is much appreciated.

Thank you in advance!!

image

Tagged:

Best Answer

Answers

  • AltairLiz
    AltairLiz
    Altair Employee
    edited April 2022

    Hi,

    Can you provide the details on which Altair product/version you are using?

     

     

  • Akshay Manthekar
    Akshay Manthekar Altair Community Member
    edited April 2022

    Hi Elizabeth,

    I am using version 17.3

  • AltairLiz
    AltairLiz
    Altair Employee
    edited April 2022
    Akshay Manthekar said:

    Hi Elizabeth,

    I am using version 17.3

    Which product are you using?

  • Akshay Manthekar
    Akshay Manthekar Altair Community Member
    edited April 2022

    Hi Elizabeth,

    Thanks for reverting back.

    I am running the tcl script in HyperMesh product of Altair. Please find below attached pic for details. 

     


    Altair Home: C:/Temp

    Updates Information:
    ------------------------------------------------------------
    hwDesktop2017.3
    hwSolvers2017.2

    Versions:
    ------------------------------------------------------------
    e_2017.1_win64.exe: 2017.1.0.13 (Mar 9 2017)
    e_2017.2_win64.exe: 2017.2.0.12 (Jun 16 2017)
    hgtrans.exe: 2017.3.0.17 (Oct 6 2018)
    hmobj.dll: 2017.3.0.17 (Oct 6 2018)
    hmopengl.exe: 2017.3.0.17 (Oct 6 2018)
    hst.exe: 2017.3.0.17.1466500 (Oct 6 2018)
    hstbatch.exe: 2017.3.0.17.1466500 (Oct 6 2018)
    hstdss.exe: 2017.3.0.17.1466500 (Oct 6 2018)
    hvp.exe: 2017.3.0.17 (Oct 6 2018)
    hw.exe: 2017.3.0.17 (Oct 6 2018)
    hwmbdmodel.dll: 2017.3.0.17 (Oct 6 2018)
    hwplot.dll: 2017.3.0.17 (Oct 6 2018)
    hwplot3d.dll: 2017.3.0.17 (Oct 6 2018)
    hwpost.dll: 2017.3.0.17 (Oct 6 2018)
    hwtext.dll: 2017.3.0.17 (Oct 6 2018)
    hwvideo.dll: 2017.3.0.17 (Oct 6 2018)
    hwx.exe: 2017.3.0.17 (Oct 6 2018)
    hx_2017.0_win64.exe: 2017.0.0 (Oct 28 2016)
    hx_2017.1_win64.exe: 2017.1.4 (Mar 27 2017)
    hx_2017.2_win64.exe: 2017.2.3 (May 30 2017)
    nusolver.dll: 2017.2 (Jul 10 2017)
    optistruct_2017.0_win64.exe: 2017.0.0.18 (Dec 19 2016)
    optistruct_2017.1_win64.exe: 2017.1.0.17 (Apr 4 2017)
    optistruct_2017.2_win64.exe: 2017.2.0.13 (Jun 26 2017)
    templex.exe: 2017.3.0.17 (Oct 6 2018)

     

     

    image

  • Ben Buchanan
    Ben Buchanan
    Altair Employee
    edited April 2022 Answer ✓

    Right, there is no guarantee of new surfaces having a certain ID.  You will probably need to use something like *createmarklast

    https://2022.help.altair.com/2022/hwdesktop/hwd/topics/reference/hm/_createmarklast2.htm?zoom_highlight=createmarklast

  • Akshay Manthekar
    Akshay Manthekar Altair Community Member
    edited April 2022

    Hi Ben,

    Thank you so much for your help. This will surely help me dealing with new ID generation while doing surface splits.

Categories