CubitModifyInterface Namespace Reference
This document explains how to access Cubit mesh data from C++ or python. More...
Functions
Detailed Description
This document explains how to access Cubit mesh data from C++ or python.
The purpose of CubitMeshInterface is to provide developers with a query interface for Cubit mesh data.
Most function prototypes are easy to understand. A few are more ambiguous and for those some examples are provided. Note that input parameters that require entity types, such as "volume", "quad", "curve", and so forth, expect lower case spellings of those entity types.
Examples are provided for C++ and python developers.
Function Documentation
- std::vector< double > & coords)
-
coordsvector of node locations, ordered x,y,z for each node
- std::vector< int > & tri_nodes)
-
tri_nodesvector of node ids, ordered ccw for each tri
- double x0,
- double y0,
- double z0,
- double x1,
- double y1,
- double z1,
- int color)
brief draw a line in space in the graphics window
- double x,
- double y,
- double z,
- int color)
brief draw a point in space in the graphics window
brief flush the graphics pipeline
brief updates all entities in cubit DB (including graphics) after the mesh has been modified
- int num_nodes,
- int * nodes,
- double * coords)
-
num_nodesnumber of nodes we are passing in
-
nodesarray of node ids (array size = num_nodes)
-
coordsarray of x-y-z coordinates (array size = 3*num_nodes)
- const std::string & geom_type,
- int from_entity_id,
- int to_entity_id,
- bool snap_to)
-
geom_typeSpecifies the geometry type of the entity
-
from_entity_idid of an existing cubit entity of type geom_type that currently contains mesh entities. entity will no longer me "meshed" following this operation
-
to_entity_idid of an existing cubit entity of type geom_type that does not currently meshed. entity will be meshed following this operation.
-
snap_toproject any nodes to the gometry entity with id to_entity_id