HyperMesh Subsystem Modeling Exercise Help

Mandy Kramer

I'm struggling with a couple of concepts in subsystem modeling. The attached .hm model helps demonstrate some of my questions.

 

The goal of this example is to use subsystems to:

1. run load case 1 on plate 1
2. run load case 2 on plate 2
3. run load case 3 on plate 3
4. run combined load case 4 on all 3 plates

 

Setup:

• 3 shell element plates with same material and constraint
• load application and mesh density varies a little
• part 3 is a linked instance of part 2

 

Question 1: is there a purpose in a model as simple as this to generating configurations within the part browser? What is the main purpose of making configurations in the part browser?

Question 2: the subsystem browser has "Model" as a subsystem by default, and all other subsystems are underneath it. Is this always the way it's structured? If not, how do you restructure to eliminate the "Model" level?

Question 3: what is the function of the "subsystem set" on the bottom left of the subsystem browser as I have shown. For this example, it seems  like an extra step that might not be necessary for this scenario.

Question 4: I generated each of the subsystems similarly using the drag and drop method from the part browser. The subsystem hierarchy should look very similar for all three, but there are some discrepancies in the entity count (parts vs. no parts, load collectors, geometry, etc.). How to I achieve consistency and how important are all of these entity types in the subsystem modeling?

Question 5: when I activate the check box on any of the "subsystem configurations" in the upper left of the subsystem browser and solve, I get a missing subcase information error. I probed the .fem file and tried to fix the load case problems, but I can't figure out why it's not outputting only the load collectors and load steps that I requested in the subsystem browser (.fem and .out file attached)

Question 6: is there a way to make a subsystem configuration with a different location/orientation part or assembly without generating new linked parts for all of the parts that are in the different location?

Question 7: as a general rule, should the entity state browser not be used when working with configurations and subsystems?

Question 8: do I need to learn more about include files or subsystem modeling before proceeding? Can you recommend some training material?

 

Thank you,

Mandy

Fred_Juras

Hello Mandy,

Please find below quick feedback regarding your questions.

Question 1: the main purpose of part config is to represent all the configurations in one hm database and activate only the interested one. For instance, different design of a same part.

Question 2: the main Model Subsystem is indeed mandatory. The first subsystem in your model will always be the "Model" subsystem. This is the subsystem connected to the "Main Include".

Question 3: subsystem set is just a group of subsystem, for organization/selection purpose. For this usecase, indeed, it is optional.

Question 4: it all depends of the organize settings (RMB in the subsystem browser > Organize settings). As you'll see, you can determine which dependent entities to move when managing subsystem content and behavior if entities are shared across subsystems. For instance, a prop assign to a comp will be move by default with the comp.

Question 5: All entities moved into a Subsystem will be moved to an Include. The Subsystem always has one linked include and contents of the include and subsystem will always be in sync. Therefore, you must organize your subsystem/entities based on the include type => bulk data, subcase section or I/O section. For instance, loadsteps should be defined in a "subcase section" include type.

Question 6: not sure to understand this question... since v2023, you can create and manage instance of subsystem. Please take a look at this video => https://youtu.be/KvZuZJ7C8lw?si=u2khQjAPLVfMcGED

Question 7: yes absolutely. You can still use the entity state browser, but the active state of parts/subsystems should do the job.

Question 8: Please take a look at this tutorial from the online help and this playlist from our Altair How To Youtube channel:
https://help.altair.com/hwdesktop/hwx/topics/tutorials/hwx/model_build_t.htm

 

Regards,
Fred.

Fred_Juras

Hello Mandy,

Please find below quick feedback regarding your questions.

Question 1: the main purpose of part config is to represent all the configurations in one hm database and activate only the interested one. For instance, different design of a same part.

Question 2: the main Model Subsystem is indeed mandatory. The first subsystem in your model will always be the "Model" subsystem. This is the subsystem connected to the "Main Include".

Question 3: subsystem set is just a group of subsystem, for organization/selection purpose. For this usecase, indeed, it is optional.

Question 4: it all depends of the organize settings (RMB in the subsystem browser > Organize settings). As you'll see, you can determine which dependent entities to move when managing subsystem content and behavior if entities are shared across subsystems. For instance, a prop assign to a comp will be move by default with the comp.

Question 5: All entities moved into a Subsystem will be moved to an Include. The Subsystem always has one linked include and contents of the include and subsystem will always be in sync. Therefore, you must organize your subsystem/entities based on the include type => bulk data, subcase section or I/O section. For instance, loadsteps should be defined in a "subcase section" include type.

Question 6: not sure to understand this question... since v2023, you can create and manage instance of subsystem. Please take a look at this video => https://youtu.be/KvZuZJ7C8lw?si=u2khQjAPLVfMcGED

Question 7: yes absolutely. You can still use the entity state browser, but the active state of parts/subsystems should do the job.

Question 8: Please take a look at this tutorial from the online help and this playlist from our Altair How To Youtube channel:
https://help.altair.com/hwdesktop/hwx/topics/tutorials/hwx/model_build_t.htm

 

Regards,
Fred.

Mandy Kramer

Frederic Juras_21782 said:

Hello Mandy,

Please find below quick feedback regarding your questions.

Question 1: the main purpose of part config is to represent all the configurations in one hm database and activate only the interested one. For instance, different design of a same part.

Question 2: the main Model Subsystem is indeed mandatory. The first subsystem in your model will always be the "Model" subsystem. This is the subsystem connected to the "Main Include".

Question 3: subsystem set is just a group of subsystem, for organization/selection purpose. For this usecase, indeed, it is optional.

Question 4: it all depends of the organize settings (RMB in the subsystem browser > Organize settings). As you'll see, you can determine which dependent entities to move when managing subsystem content and behavior if entities are shared across subsystems. For instance, a prop assign to a comp will be move by default with the comp.

Question 5: All entities moved into a Subsystem will be moved to an Include. The Subsystem always has one linked include and contents of the include and subsystem will always be in sync. Therefore, you must organize your subsystem/entities based on the include type => bulk data, subcase section or I/O section. For instance, loadsteps should be defined in a "subcase section" include type.

Question 6: not sure to understand this question... since v2023, you can create and manage instance of subsystem. Please take a look at this video => https://youtu.be/KvZuZJ7C8lw?si=u2khQjAPLVfMcGED

Question 7: yes absolutely. You can still use the entity state browser, but the active state of parts/subsystems should do the job.

Question 8: Please take a look at this tutorial from the online help and this playlist from our Altair How To Youtube channel:
https://help.altair.com/hwdesktop/hwx/topics/tutorials/hwx/model_build_t.htm

 

Regards,
Fred.

Thanks Fred! Very helpful.

-Mandy