🎉Community Raffle - Win $25

An exclusive raffle opportunity for active members like you! Complete your profile, answer questions and get your first accepted badge to enter the raffle.
Join and Win

How to find surface IDs of new surface generated?

User: "Akshay Manthekar"
Akshay Manthekar
Altair Community Member
Updated by Akshay Manthekar

Hi Guys,

I have a geometry in which surfaces are penetrating into each other. I have created a macro which splits the surface(s) by another surface. As we know, after splitting, new surface ids would be formed. So, I want to delete the new surface IDs which are formed after split operation. 

Can anyone help me which command should I use to know what new surface IDs are formed after splitting?

Your help is much appreciated.

Thanks in advance

Find more posts tagged with

English
HyperMesh
v2021.2
Sort by:
1 - 3 of 31
    User: "Akshay Manthekar"
    Akshay Manthekar
    Altair Community Member
    OP
    Updated by Akshay Manthekar

    Hi Ben,

    Thanks for the response.

    Can you tell the difference between hm_latestentityid and *createmarklast commands.

    I have read the documentation but couldn't understand it.

    It would be very kind of you if you put it into simple words for me.

     

    Thanks!

     

    User: "Ben Buchanan"
    Ben Buchanan
    Altair Employee
    Updated by Ben Buchanan

    Hi Ben,

    Thanks for the response.

    Can you tell the difference between hm_latestentityid and *createmarklast commands.

    I have read the documentation but couldn't understand it.

    It would be very kind of you if you put it into simple words for me.

     

    Thanks!

     

    Hey Akshay,

    Yeah looks like there is some crossover here.  One of the main differences I see is that hm_latestentityid returns the id when the command is run  and *createmarklast puts it on the mark

    So I think this:

    set node1 [hm_latestentityid nodes]

    and this:

    *createmarklast nodes 1

    set node1 [hm_getmark nodes 1]

    would give you the same result.

    Looks like hm_latestentityid gives you more flexibility because you can go back to not just the last created put up to the latest 99 entities created.

    Hope that helps.

Quick Links