### TABLE 2. GEOMETRIC MODELING SYSTEMS

1980

Cited by 193

### Table I. Model Geometric Characteristics

### Table I. Model Geometric Characteristics

1995

### Table I. Model Geometric Characteristics

1995

### Table 1 Basic topological entities in the CGM geometric model.

2004

"... In PAGE 6: ...epresentations is discussed in section 2.5. 2.1 Topology The basic topological entities used in CGM, along with their dimensions, are shown in Table1 . Note that in the case of Edges and Faces, the most common nomenclature can be confusing in a finite element context, since there are also edge and face element types.... In PAGE 14: ... GeometryModifyTool functions supporting geometry decomposition are summarized in Table 11. Table1 1: Functions supporting geometry decomposition. Function Description GeometryModifyTool::webcut_with_xxx (xxx = plane, sheet, vertices, cylinder, surface, extended_surface, body) Decompose one or more bodies with a given geometry entity or implicitly-defined geometric entity.... In PAGE 15: ... Functions which control merging are summarized in Table 12. Table1 2: MergeTool functions which control merging of manifold into non-manifold geometry. Function Description MergeTool::merge_all_bodies MergeTool::merge_all_refxxx (xxx = vertices, edges, faces) Performs merge check on all entities of the specified type.... In PAGE 15: ... Table 13 summarizes the functions for creating, removing, and performing other interactions with virtual geometry. Table1 3: VirtualGeometryEngine functions for creating, removing and otherwise interacting with virtual geometry. Function Description PartitionTool::partition Partition the given entity using explicit or implicit geometry (implicit geometry is geometry whose geometric data are ... In PAGE 17: ...Table1 4: Topology traversal functions implemented in TopologyEntity. Function Description TopologyEntity::bodies TopologyEntity::ref_xxx (xxx=volumes, faces, edges, vertices) TopologyEntity::shells TopologyEntity::loops TopologyEntity::co_faces TopologyEntity::co_edges Return list of bodies related to the entity from which the function was called.... In PAGE 17: ... Like the traversal functions in TopologyEntity, these functions are called as member functions from a RefEntity object. Table1 5: Parent and child topology traversal functions defined in RefEntity. Function Description RefEntity::get_child_ref_entities Return a list of all immediate children of the RefEntity.... In PAGE 18: ... The purpose of the code in each subdirectory is also described in Table 16. Table1 6: CGM directory structure and purpose of code in each subdirectory. Directory Purpose Depends on: $(CUBIT_BASE_DIR)/util Utility functions for other code in CGM (none) $(CUBIT_BASE_DIR)/util/OtherFiles Configuration files for compiling CGM on various platforms (none) $(CUBIT_BASE_DIR)/geom Core CGM datastructure and tool classes.... In PAGE 19: ... This section gives some additional notes on compiling applications based on CGM. As noted in Table1 6, some of the code in CGM depends on the ACIS solid modeling engine; however, it is not necessary to link CGM applications with ACIS if ACIS-based geometry will not be used. 3.... In PAGE 20: ... In this application, since it exits immediately after these geometry calculations, there is no need to explicitly shut down CGM. Table1 7: Pseudo code for C++ driver code, forward declarations and main. // include tool and datastructure declarations #include GeometryModifyTool.... In PAGE 21: ...8.2 Reading geometry files In the read_geometry() function, shown in Table1 8, each file is opened, then the file pointer is passed to GeometryQueryTool::import_solid_model function. This function reads all the geometry entities defined in that file and stores them in the CGM database.... In PAGE 21: ... The return value from import_solid_model() should be checked for indications of problems reading the geometry file. Table1 8: Pseudo code for C++ driver; read_geometry() function. CubitStatus read_geometry(int num_files, char **argv) { GeometryQueryTool *gqt = GeometryQueryTool::instance(); // For each file, open and read the geometry for (i = 1; i lt; num_files; i++) { file_ptr = fopen(argv[i], r ); if (file_ptr == NULL) PRINT_ERROR( Could not open file %s\n , argv[i]); else { status = gqt- gt;import_solid_model(file_ptr, argv[i], ACIS_SAT ); } } return CUBIT_SUCCESS; } 3.... In PAGE 22: ... GeometryQueryTool::delete_Body() is called at the end of evaluate_overlaps() to delete any bodies produced during the intersection operation. Table1 9: Pseudo code for C++ driver; evaluate_overlaps() function. CubitStatus evaluate_overlaps() { // evaluate overlaps by intersecting bodies pairwise GeometryModifyTool *gmt = GeometryModifyTool::instance(); // make a copy of the body list for use in this function DLIList lt;Body* gt; all_bodies, all_new_bodies; GeometryQueryTool::instance()- gt;bodies(all_bodies); // step forward on this list, extracting the first body and using it // as a tool for remaining bodies for (i = all_bodies.... In PAGE 24: ...Merging and printing results In the main function, after the call to imprint_bodies() (see Table1 7), all bodies in the model are checked for potential merges by calling MergeTool::merge_all_bodies(). This function uses a pre-defined tolerance while checking for coincident geometry; this tolerance can be changed using other functions in MergeTool.... ..."

### Table 1. Global and local stretch of some large geometric models

2003

Cited by 6

### Table 1. Global and local stretch of some large geometric models

### Table 1. Geometric and optical parameters of the model.

"... In PAGE 2: ... 3. The ringed planet model Nine photometric and geometric parameters are used to deflne the ringed planet ( Table1 and Fig. 1) and several assumptions are made to derive theoretical light curves of the ringed planet along its orbit.... In PAGE 5: ... Parameters for difierent ringed planets. Deflnitions are given in Table1 anf Fig. 1.... ..."