2022.4+26187-e1209cf7 Apr 14, 2022

7.1 Global Element IDs

 

7.1.1 Cubit Mesh Entity ID Spaces

All mesh entities have an ID associated with them which is unique within the corresponding mesh entity ID space. For example, a hex will have an id which can be used in commands such as "list hex 17". However, this ID is only unique amoungst the hexahedra in the Cubit session. There could also be a tet, quad, tri, edge, node, etc. with ID 17.

7.1.2 Global Element IDs

Whenever a hex, tet, quad, tri, etc. gets put into an element block, it is assigned another ID which is called the Global Element ID. The Global Element ID is unique among all element which have been put into any block. It is exported to the Exodus file format so that downstream analysis applications can map elements back to the corresponding Cubit hex, quad, etc. 

7.1.2.1 Interacting with GlobalElement IDs

After a hex, quad, etc. is placed into an element block, you can see which ID was assigned to it with the list command. For example:

reset
bri x 10
mesh vol all
block 1 hex all
list hex 1

The resulting output will contain the following:

 Cubit> list hex 1
 Hex 1
 Global Element ID = 1

In this simple example, the Hex ID is the same as the Global Element ID, but this will not always be true. These Global Element IDs are exported as the global id in the Exodus file. If during an analysis run, a particular element needs to be identified back in the Cubit session, they can be found with any of the following commands:

List element <id_range>

Users can control the assigned Global Element ID with the renumber command.