why element set created is an internal set? 1

[roudan]

Hi

I am using python script to create a element set with a name.

modelInstane=modelAssembly.instances['instance-name']
AllElement_MappedRegion=modelInstane.elements
eleSet_DataMapping_CLWR_AllLayers=modelAssembly.Set(elements=AllElement_MappedRegion, name='EleSet_MappedRegion_ThisModel')

in the inp file, I didn't find the element set name of 'EleSet_MappedRegion_ThisModel'. Instead, it created an internal element set with underdash in the first letter like _G49
*Elset, elset=_G49, internal, instance=Instance-Part-Inside, generate
1, 62944, 1

I am wondering if I can create a NON-Internal element set using python? Thanks

 

[FEA way]

The Internal parameter is there just to highlight that the set was created internally in Abaqus/CAE. You can delete this parameter and it should work fine.

 

[roudan]

Thanks FEA Way, I am wondering if how to create NON-Internal Element Set? so I have a predefined element set name which I can use in INP file. Thanks

 

[FEA way]

Normally Python commands shouldn't create internal sets, check the syntax of the script. And keep in mind that you can quickly test short scripts using Command line interface (bottom part of Abaqus/CAE window). You can also do some tasks manually in CAE and either check the replay file or record macro to see which Python commands correspond to each operation.

Here's an exemplary script that creates assembly level elset using getByBoundingBox method:

a = mdb.models['Model-1'].rootAssembly
e1 = a.instances['Part-1-1'].elements.getByBoundingBox(-1000,-1000,-1000,1000,1000,1000)
a.Set(elements=e1, name='Set-1')

 

[roudan]

Thank you so much FEA Way, i found the error now, the element set is defined before meshing. after moving to after meshing, it is fine now. Thank you again!