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.

Hi,

Since version 2021, there is a new option called "Automatically update sets to mesh changes", allowing to update sets of nodes and/or elements in case of re-meshing. Thus, if a pressure (or any load/contact surface...) is defined on element set, then pressure will be automatically mapped on the new set in case of remeshing.

This is one advantage of the new load management => to define loads and boundary conditions as distributed loads on sets. More details here: https://help.altair.com/hwdesktop/hwx/topics/pre_processing/entities/loads_r.htm

This solution is highlighted in the attached video.

For a model with classic loads (as in your screenshot), you must process in two steps: first create a field to store the initial pressure loads and then realize the field to map the pressure value on the new mesh.

Regards,
Fred.