HyperMesh Subsystem Configuration - Follower/Ghost Nodes

Mandy Kramer · 2025-01-16T15:08:07+00:00

There was an error rendering this rich post.

Hello,
I'm learning how to work in the subsystems browser to control model configurations and I have low familiarity with include files. My model has RBE3 elements in each configuration that connect to the same set of elements (same mounting holes across concepts). I did a drag-drop operation on the "part" entities associated with each of the configurations into their respective subsystems. The nodes associated with the mounting elements appear in only one of the subsystems and I received this error when conducting a solve:

To resolve, I drag-dropped the "Nodes" associated with the single subsystem into the main "Model" subsystem. The model solves without error now, but "ghost nodes" show up when I open the results in HyperView that are associated with an inactive subsystem part. I can hide the nodes manually in HV, but I'd rather find a way to exclude them from the results file. The image below shows two different "ghost node" sets that show up in my results (one has nodes highlighted, the other doesn't).

Is there a different method I can use to:
a) avoid inclusion of nodes in subsystems during drag/drop configuration construction
b) avoid "ghost node" generation

Thank you,
Mandy

Find more posts tagged with

HyperMesh

Accepted answers

Michael Herve

hello again @Mandy Kramer ,

attached is a modified hm file (from version 2024.1) with the 2 configurations. If I make one configuration active, export it and run it, I see no ghost nodes in the result files:

2025-01-20 Test_Altair_update.hm

Did I miss anything?

Regarding the question about how not to get nodes moved from main model to subsystem when you create a new rbe3, you can right click in the Subsystem Browser →" Organize options". This won't move any node at all, meaning you will have to move the master node to subsystem in a separate step.

Best Regards,

Michael

All comments

Michael Herve

hello @Mandy Kramer ,

are you sing the rbe3 for all configurations? If so are they connecting the same entities for every configuration? If so they should not be placed in any subsystem

Please feel free to tell me if I misunderstood your model organization

Regards,

Michael

Mandy Kramer

Hi @Michael Herve_21439 ,

I have a couple of different subsystems, each with a different RBE3/CONM2 pair. Yes, the RBE3 elements all connect to the same entities, but the CONM2 elements differ, which is why I'm trying to use subsystems/configurations.

I attached a test file to help demonstrate what I'm trying to achieve:

2025-01-20 Test.hm

Any comments on suggested subsystem and configuration use are greatly appreciated. I have a history of misunderstanding their purposes.

Thanks,

Mandy

Michael Herve

hello again @Mandy Kramer ,

attached is a modified hm file (from version 2024.1) with the 2 configurations. If I make one configuration active, export it and run it, I see no ghost nodes in the result files:

2025-01-20 Test_Altair_update.hm

Did I miss anything?

Best Regards,

Michael

Mandy Kramer

Thanks @Michael Herve_21439 . I am also unable to replicate the ghost node issue in my test model. The note on the organization settings answers my question.