<!DOCTYPE html
  PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<!--
Copyright (c) 2006 UGS Corp.

All Rights Reserved.

This software and related documentation are proprietary to UGS Corp.
-->
<html>
   <head>
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <title>Using Attributes For Classification</title>
      <script language="javaScript">
        abridged="false";
        displayConditions=new Array();
      </script>
      <link type="text/css" href="../css/main_styles.css" rel="stylesheet">
   </head>
   <body class="bodydocs" onload="top.pageLoader()" bgcolor="#FFFFFF">
      <div class="title_topic4" id="xps10_pagetitle">Using Attributes For Classification </div>
      <hr noshade="true">
      <p class="para_topic">After the Holemaking module has identified the features in a part according to their CAM_FEATURE_NAME attribute, the system then groups the features together based on their other attribute values such as diameter and tolerance.</p>
      <p class="para_topic">Attributes attached to geometric entities or features, can be used as classification criteria to classify the features based on these attributes. Therefore, features are grouped together into feature groups depending on the chosen classification criteria. </p>
      <p class="para_topic">Classification attributes are given the same names as base feature parameters in order to allow manufacturing parts to contain mixed feature types. Using the same names also keeps the Holemaking template from getting too complex. </p>
      <div class="title_division">Amount of Attribute Information Needed Per Entity Tag </div>
      <p class="para_division">Some entities need more attributes than others depending on the tagged entity (face, edge, arc, point). For example, a tagged face does not necessarily need a depth attribute because the Holemaking template can use the Model Depth for the depth calculation. However, on a point a depth attribute is essential because there is no Model Depth to draw from. Every tagged entity needs to have certain attributes to make it a valid candidate for the Holemaking process. &nbsp;&nbsp;&nbsp;</p>
      <p class="para_division">Below is an example of how the different entity tags need different amounts of information for the same CAM_FEATURE_NAME value. </p>
      <p class="para_division">Minimum attribute requirements for a SIMPLE_HOLE:</p>
      <p class="para_division">Face: CAM_FEATURE_NAME, DIAMETER, I, J, K </p>
      <p class="para_division">Edge: CAM_FEATURE_NAME, DIAMETER </p>
      <p class="para_division">Arc: CAM_FEATURE_NAME, DIAMETER, DEPTH, I, J, K</p>
      <p class="para_division">Point: CAM_FEATURE_NAME, DIAMETER, DEPTH, I, J, K</p>
      <div class="title_division">Using Minimum Attributes</div>
      <p class="para_division">You should always apply the same set of attributes to all entities on a mixed feature type model. This is because only the minimum set are taken into account for feature classification. </p>
      <div class="title_division">Example </div>
      <p class="para_division">A model contains a tagged point and a base feature. The tagged point is tagged with SIMPLE_HOLE as its CAM_FEATURE_NAME. It also has an additional attribute, TOLERANCE. The base feature is also a SIMPLE_HOLE, with the same parameter values as the tagged point (diameter, depth, I,J,K). However, it does not have the addition of the TOLERANCE attribute. </p>
      <p class="para_division">Holemaking tries to group these entities based on the same characteristics. The TOLERANCE attribute does not display in the Classification Criteria field in Holemaking because it is not an attribute that both tagged entities contain. Therefore, it is removed from the Classification Criteria field in this case. </p>
   </body>
</html>