### Table 1: Simulated data: Observed odds ratios (OR), associated 95% confidence intervals (CI) and SEM regression coefficients with corresponding standard errors (SE) obtained via ML estimation (N = 5000)

2005

"... In PAGE 5: ... This approach assumes that the model is correctly specified. Results Table1 contains observed odds ratios for the simulated data set and their decomposition into regression effects based on SEM using Yule apos;s transformation of odds ratios. A standard approach to the analysis of binary variables using multivariate logistic regression for the simulated data is presented in Table 2.... ..."

### Table 1. Total polygon count in the models N

2003

"... In PAGE 8: ... Assuming that all of the extracted models are composed of closed polygonal surfaces, we can compute enclosed volume as a a signed sum of the pyramids with a base composed of the i apos;th triangle and a top vertex places at the origin of the dataset. 32 Then V 1 6 N poly X i=1 A i 1 3 (v 1 i + v 2 i + v 3 i ) N i ;; (17) Table1 lists values of polygon count, surface area and total volume, for the models extracted from scalar volume datasets (V 1 and V 2 ), before and after the level set algorithm is applied to the volumes. We note that the polygon count drops, because of the simpli ed form of the nal extracted triangular mesh.... ..."

Cited by 11

### Table 2: Parameter estimates for main and interaction effects on cognitive score by the logistic regression model

2007

"... In PAGE 4: ... A combination of the two var- iants forms four nominal response categories among which non-carriers below age 65 serve as the reference group. In Table2 , we show the parameter estimates for the main and interaction effects by our logistic regression model. The model identified a highly significant effect of age-group that is negatively correlated with individual apos;s cognitive function (RRR = 0.... In PAGE 4: ... For comparison, we applied our retrospective logis- tic regression model to the dichotomized cognitive score. Parameter estimates in Table2 also reveal the negative association with cognitive functioning by aging (RRR = 0.... In PAGE 4: ... This is understandable since the case-only model measures the deviation from the multiplication of main effects [9] which is exactly the def- inition of interaction effect in our model. However, since the maximum likelihood from the dichotomized trait is lower than the continuous trait ( Table2 ), the model using cognitive score as a continuous trait should be preferred. Table 2: Parameter estimates for main and interaction effects on cognitive score by the logistic regression model... In PAGE 5: ... As shown by equation (6), testing the null hypothesis of b = 0 is equivalent to testing Ho : RRR = 1. This is also shown by the 95% confidence intervals for the estimated RRRs in Table2 . Since the slope parameters for the main and interaction effects are all statistically differ- ent from zero, none of the 95% confidence intervals of RRR covers the null risk of one.... ..."

### Table 3: Association between WHOMS acceptability and patients apos; characteristics

"... In PAGE 8: ... Multivariate analysis for the quot;WHOMS acceptability quot; out- come confirmed the pattern of association that emerged in univariate analysis. Variables most strongly associated with acceptability were: FCT score, age and number of education years ( Table3 ). The model showed a good fit with the data (Hosmer-Lemeshow chisquare = 3.... In PAGE 8: ...ations (83.5%, sensitivity 87.5% specificity 78.1%). In particular, the odds ratios reported in Table3 indicate that for a unit increase in the FCT score, holding all other var- iables constant, the odds of accepting WHOMS increased by 173%, indicating a very strong relationship. Both age and education years still maintain an independent, although weaker, association with acceptability (results indicate a reduction by 9% and an increase by 32% in the odds of accepting WHOMS for a unit increase, respectively).... ..."

Cited by 1

### Table 1 Increase of the mesh size

2003

"... In PAGE 10: ...he 3D Garment v2.0 system [19], the result is shown in Fig. 12j, 12k, and 12l. From the above examples and applications, it is easy to find that our extrusion approach is an intuitive, efficient geometric modeling tool for freeform polygonal object modeling. The number of vertices and faces of the toy design application and the fashion design application is shown in Table1 . Both the number of vertices and the number of faces are increased considerably after extrusion.... ..."

Cited by 4

### Table 1: Shows the polygon counts after applying the mesh simplification technique on several models.

"... In PAGE 4: ... The following table shows all the re- sults for the polygonal models on which we have used our technique. From the Table1 above, we can deduce that while a smaller order GAEA produces a simpler resulting mesh, it also suffers in terms of quality. However in another observation of the results in the table above, it seems that the algorithm is only able to produce minimal reduction in the number of polygons.... ..."

### Table 2: Supported associations

"... In PAGE 5: ...able 1: Diagram Patterns in alfabet........................................................................................ 30 Table2 : Comparison of metamodeling environments .... In PAGE 31: ... These features come into play when a change in a model requires updating other models in the abstraction hierarchy None of the reviewed metamodeling environment brings together in a single system the best of the capabilities offered by specialized tools. In Table2 , a representative sample of the available metamodeling environments is benchmarked against a set of criteria considered highly important. Please notice that the last column in that table refers to System Architect, a product that will be analyzed in section 3.... In PAGE 32: ...32 Table2 : Comparison of metamodeling environments alfabet GME MetaEdit+ System Architect Semantic validity checks Automatic link maintenance. Checks must be coded as scripts to be invoked by the platform (events) OCL (at beta stage) Fill-in-the- blanks customization.... In PAGE 33: ... Model definition export possible only in ASCII text format. Tools that export/import from MS Repository can be used with GME A reporting tool with textual files as output Output can be prepared with VBA (Visual Basic for Applications) GUI builder for forms-based dialogs Yes Executable models User-defined methods can be added to classes Yes, provided they follow a data-flow scheme Yes (partial) No Source-code generation No Yes Yes (partial) Query language over modelbases Extended SQL No Scripting of the tool Only as DLL (Dynamic Link Library), using C++ COM (Component Object Model) Java-like, proprietary, inside the tool Visual Basic for Applications amp; ActiveX Automation Table2... ..."

### Table 1: Model characteristics, memory use and timings for different polygonal models

1999

"... In PAGE 10: ... All tests were run on a SGI Onyx2 BaseReality with one R10000, 195 MHz processor, 64 MB texture memory and 256 MB main memory. Table1 shows detailed results of the proposed adaptive voxelization technique with respect to memory requirements, rendering complexity and frame rates. The models we compare to each other are illustrated in the top row of Figure 6.... In PAGE 10: ... In the demonstrated examples, however, this time was negligible compared to the overall rendering times. Also from Table1 it can be observed that our approach is still slower than pure polygon rendering. This loss in the rendering performance can be explained by the fact that although we already did considerably reduce the number of operations to be per- formed in the rasterization unit the capacity of the rasterization hardware still prohibits... In PAGE 11: ...Table1 . Since only the polygons that result from clipping the slicing planes against the bounding boxes, only about 1% of the primitives needed to render the polygonal models have to be converted into fragments.... ..."

Cited by 6

### 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. Example of laten factor and its associated pages from KDDCUP

"... In PAGE 7: ... Here, we present the experimental results of the derived latent factors from two real data sets based on PLSA model respectively. Table1 il- lustrates one example out of the derived factors extracted from the KDDCUP data set as well as the dominant page set, whose probabilities are over the predefined threshold, whereas Table 2 presents the example out of those from CTI data set. From these tables, it is easily concluded that the factor #6 in KDDCUP data set reflects the scenario involving in online shopping process, whereas the factor #13 stands for ac-... ..."