Automatic surface/node set names sometimes are too long

Feature Requests
1

Hi, I give to my parts significative names, but not too long, something like “REINFORCEMENT_U” in the worst cases, but I found that when the tool for detect and create surface contact sets (wonderfull tool!) is used, it creates names automatically that in those cases that combine two “long part names” get a name that are too long for running in CCX. Maybe a lenght limit in the name creation algorithm would solve this case.

Worst, if I delete such contact definition, looks like those long names stays somewhere in the model dictionary (?) and then a several error messages appear, didn´t find a way to purge those hiden sets and fix the model.

Regards!

2

I was not aware/forgot that the name’s length is limited.

Changing the global behaviour of creating names is a lot of work, but I can add a simple local fix for this.

I can limit the length of the created pair names. Currently, the name consists of the first part and the second part names connected with “to” string. Then some additional strings “Internal-1_Internal_Selection-1” and “Master_S4” are attached:

Internal-1_Internal_Selection-1_Long_part_name_1_to_Long_part_name_2_Master_S4

These strings can be up to 40 characters long. So if the name “part-1_to_part-2” is longer than 35 characters, I will shorten it to “part-1_to”.

However, I was unable to reproduce the problem with undeleted invalid items after the contact has been deleted.

3

Here’s how Abaqus names them:

IMG_9617
IMG_9617986×499 75.8 KB

The prefix is “CP” by default.

Master and Slave can be easily replaced by M and S at the beginning or at the end.

1 Like
4

I have some name-fixing routines that search for certain keywords in item names when I load the .dat files. So, for now, I relied on longer keywords to prevent them from being accidentally created by the user. However, I can now create reserved names for that and make them shorter.

1 Like