On this page:
3.7.1 List Model Summary
3.7.2 List Geometry List Names Example List Surface [range] Ids’ Examples Using ’List’ for Querying Connectivity.
3.7.3 List Mesh
3.7.4 List Special Entities
3.7.5 List Cubit Environment Sample output

3.7 Listing Information

The list commands print information about the current model and session. There are five general areas: Model Summary, Geometry, Mesh, Special Entities, and Cubit Environment. The descriptions of these areas includes example output based on the model generated by a journal file listed below. The model consists of a 1x2x3 brick meshed with element size 0.1.

Journal File Used for List Examples

brick x 1 y 2 z 3
 body 1 size 0.1
 mesh volume 1
 block 1 volume 1
 nodeset 1 surface 1
 sideset 1 surface 2
 group "my_surfaces" add surface 1 to 3
 surface 2 name "BackSurface"
 surface 3 name "BottomSurface"
 surface 1 name "FrontSurface"
 surface 4 name "LeftSurface"
 surface 5 name "RightSurface"
 surface 6 name "TopSurface"

3.7.1 List Model Summary

The following commands print identical summaries of the model: the number of entities of each geometric, mesh, and special type

List Model

List Totals

The following output is generated from the list model command.

Cubit> list model


Model Entity Totals:
 Geometric Entities:
 0 assemblies
 0 parts
 2 groups
 1 bodies
 1 volumes
 6 surfaces
 12 curves
 8 vertices
 Mesh Entities:
 6000 hexes
 0 pyramids
 0 tets
 7876 faces
 0 tris
 9854 edges
 7161 nodes
 Special Entities:
 1 element blocks
 1 sidesets
 1 nodesets


Journaled Command: list model

3.7.2 List Geometry

The following commands list information about the geometry of the model.

List Names [Group|Body|Volume|Surface|Curve|Vertex|All]

List {Group|Body|Volume|Surface|Curve|Vertex} <range> [Ids]

List {geom_list} [Geometry|Mesh [Detail]]

List {Group|Body|Volume|Surface|Curve|Vertex} <range> {X|Y|Z}

The first command lists the names in use, and the entity type and id corresponding to each name. Specifying all lists names for all types; other options list names for a specific entity type. The names for an individual entity can be obtained by listing just that entity. Sample output from the list names surface command is shown below. This output shows that, for example, Surface 2 has the name ’BackSurface’.

______Name______ __Type__ Id _Propagated_
 BackSurface Surface 2 No
 BottomSurface Surface 3 No
 FrontSurface Surface 1 No
 LeftSurface Surface 4 No
 RightSurface Surface 5 No
 TopSurface Surface 6 No List Names Example

The second command provides information on the number of entities in the model and their identification numbers. If a range is given then detailed information is given on each entity in that range, unless the ids option is also given. If the ids option is used, just a list of ids is printed. This list can be very useful for large models in which several geometry decomposition operations have performed. Sample output from the list surface command is shown below.

Cubit> list surface ids
 The 6 surface ids are 1 to 6.


Cubit> list surf ids
 The 108 surface ids are 192 to 266, 268 to 271, 273 to 301. List Surface [range] Ids’ Examples

The <range> can be very general using the general entity parsing syntax. Using a <range> gives a brief synopsis of the local connectivity of the model, e.g. one can list the ids of the surfaces containing vertex 2; as shown in the listing below.. An intermediately detailed synopsis can be obtained by placing the range of entities in a group, then listing the group.

Cubit> list surface in vertex 2 ids
 The 3 entity ids are 1, 5, 6.


Cubit> group "v2_surfs" equals surface in vertex 2
 Cubit> list v2_surfs Group Entity 'v2_surfs' (Id = 3)
 It owns/encloses 3 entities: 3 surfaces.
 Owned Entities: Mesh Scheme Interval: Edge
 _____Name____ Type______Id +is meshed Count Size
 FrontSurface Surface 1 map+ 1 H 0.1
 TopSurface Surface 6 map+ 1 H 0.1
 RightSurface Surface 5 map+ 1 H 0.1 Using ’List’ for Querying Connectivity.

The third command provides detailed information for each of the specific entities. This information includes the entity’s name and id, its meshing scheme and how that scheme was selected, whether it is meshed and other meshing parameters such as smooth scheme, interval size and count. The entity’s connectivity is summarized by a table of the entity’s subentities and a list of the entity’s superentities. Also, the nodesets, sidesets, blocks, and groups containing the entity are listed.

Specifying geometry will additionally list the extent of the entity’s geometric bounding box, the geometric size of the entity, and depending on entity type, other information such as surface normal. See also the list {entities} x command below. If multiple volumes, surfaces, or curves are selected, it will list the total volume, area, or length of all entities, and the total geometric bounding box. If multiple volumes are selected, the centroid listed will be the composite centroid of the all of the volumes.

Specifying mesh will additionally list the number of mesh entities of each type interior to the entity and on bounding subentities. mesh detail will list the ids of the mesh entities as well, following the format of the list ids command above.

The fourth command lists the entities sorted by either the x, y, or z coordinate of their geometric center. For example, in a large, basically cylindrical model centered around z-axis, it is useful to list the surfaces of a volume sorted by z to identify the source and target sweeping surfaces.

3.7.3 List Mesh

The following commands list mesh entity information.

List {Hex|Face|Edge|Node} <id_range>

List {Hex|Face|Edge|Node} <id_range> IDs

For both of these commands, the range can be very general, following the general entity parsing syntax. The first command provides detailed information. For an entity, the information includes its id, owning geometry, subentities and superentities. For a hex, the Exodus Id is also listed. For a node, its coordinates are listed. The second command lists only the entity ids, and is usually used in conjunction with complex ranges.

3.7.4 List Special Entities

List {special_type} <range>

Special entities include (element) blocks, sidesets and nodesets (representing boundary conditions). Like the list geometry and list mesh commands, if no range is specified then the number of entities of the given type is summarized. Otherwise, listing a special entity prints the mesh and geometry it contains.

(Some special entities are of interest mainly to developers and are not described here, e.g. whisker sheets, and whisker hexes.)

3.7.5 List Cubit Environment

The user may list information about the current Cubit environment such as message output settings, memory usage, and graphics settings. Message Output Settings

There are several major categories of Cubit messages.

By default, Info, Warning, Error, and Echo messages are printed, and Debug messages are not printed. Information, Warning and Debug message printing can be turned on or off (or toggled) with a set command; error messages are always printed. Debugging output can be redirected to a file. Current message printing settings can be listed.

List {Echo|Info|Errors|Warning|Debug }

Set {Echo|Info|Warning} [On|Off]

[Set] Debug <index> [On|Off]

[Set] Debug <index> File <’filename’>

[Set] Debug <index> Terminal

Message flags can also be set using command line options, e.g. -warning={on|off} and -information={on|off}. Debug flags can be set on with -debug=<setting>, where <setting> is a comma-separated list of integers or ranges of integers denoting which flags to turn on. E.g. to set debug flags 1, 3, and 8 to 10 on, the syntax is -debug=1,3,8-10.

In addition to the major categories, there are some special purpose output settings.

[Set] Logging {Off|On File <’filename’> [Resume]}

List Logging

If logging is enabled, all echo, info, warning, and error messages will be output both to the terminal and to the logging file. The resume option will append to the logfile, if it exists, instead of writing over it. If the logfile doesn’t already exist, it will be created.

List Journal Title "<title_string>"

The List Journal command lists which types of Cubit commands will be journaled and the file to which the journaled commands are being written.

List Title

The List Title command will list the title to be written to the Exodus file. To assign a title to an exodus file, use the Title command.

List Default Block

Set Default Block {ON|off}

The List Default Block command lists which type of geometric entities for which blocks will automatically be generated at export if no other blocks have been specified. The Set Default Block command will toggle whether these default blocks are written, or not, during the export operation when no other blocks have been specified.

List Settings

The List Settings command lists the value of all the message flags, journal file and echo settings, as well as additional information. The first section lists a short description of each debug flag and its current setting. Next come the other message settings, followed by some flags affecting algorithm behavior. Sample output

Cubit> list settings

Debug Flag Settings (flag number, setting, output to, description):

 1 OFF terminal Debug Graphics toggle for some debug options.

 2 OFF terminal Whisker weaving information

 3 OFF terminal Timing information for 3D Meshing routines.

 4 OFF terminal Graphics Debugging (DrawingTool)

 5 OFF terminal FastQ debugging

 6 OFF terminal Submapping graphics debugging

 7 OFF terminal Knife progress whisker weaving information

 8 OFF terminal Mapping Face debug / Linear Programming debug

 9 OFF terminal Paver Debugging




 echo = On

 info = On

 journal = On

 journal graphics = Off

 journal names = On

 journal aprepro = On

 journal file = 'cubit11.jou'

 warning = On

 logging = Off recording = Off

 keep invalid mesh = Off

 default names = Off

 default block =

 Volumes catch interrupt = On

 name replacement character = '_', suffix character = '@'

 Matching Intervals is fast, TRUE;

 multiple curves will be fixed per iteration.

 Note in rare cases 'slow', FALSE, may produce better meshes.

 Match Intervals rounding is FALSE; intervals will be rounded towards the user-specified intervals. Graphical Display Information

List View

The list view command prints the current graphics view and mode parameters. See Graphics Window. Memory Usage Information

Users are encouraged to use Unix commands such as ‘top’ to check total Cubit memory use. Developers may check internal memory usage with the following command:

List Memory [‘<object type>’]

Without an object type, the command prints memory use for all types of objects.