<!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 Geometry View to Enhance Your NC Programs</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 Geometry View to Enhance Your NC Programs</div>
      <hr noshade="true">
      <p class="para_topic">If you want to plan your NC program based on geometry, use the <b class="uiTerm">Geometry View</b> instead of the <b class="uiTerm">Program Order View</b>. You can then organize the setup by geometric feature. 
      </p>
      <p class="para_topic">For example, you can create a geometry group for Pocket A that includes a rough mill operation and a finish mill operation. You do the same for Pocket B. In the<b class="uiTerm"> Program Order View</b>, you change the order of the operation so that you rough both pockets first then finish both pockets. In the <b class="uiTerm">Geometry View</b> your operations are organized by the geometry they machine, but in the <b class="uiTerm">Program Order View</b>, those same operations are organized in the order they are output. 
      </p>
      <p class="para_topic">If you create your NC program in the <b class="uiTerm">Program Order View</b>, you can still use the <b class="uiTerm">Geometry View</b> to help you edit the NC program. Use the <b class="uiTerm">Geometry View</b> to evaluate the operations used in each geometry group and decide if the arrangement is the most efficient. Since the <b class="uiTerm">Geometry View</b> groups the operations together according to their geometry group, the <b class="uiTerm">Geometry View</b> can be used to easily move or copy an operation from one geometry group to another. 
      </p>
      <p class="para_topic">Always check how the changes you have made in any view affect the <b class="uiTerm">Program Order View</b>, as this is the view that contains the sequence of the operations for output.
      </p>
      <div class="title_division"> Operation Order</div>
      <p class="para_division">The order of the operations within the geometry groups is linked from the <b class="uiTerm">Geometry View</b> to the <b class="uiTerm">Program Order View</b>. If you change the order of operations within a geometry group in the<b class="uiTerm"> Geometry View</b>, those changes are also reflected in the <b class="uiTerm">Program Order View</b>. &nbsp;
      </p>
      <p class="para_division">For example, if a hole_geom group contains center drill, drill, and tap, those three operations must occur in that order at each hole. Other operations in other geometry groups can occur in between, but for any hole in the group, center drill must precede drill which must precede the tap. </p>
      <p class="para_division">For reordering to occur in the program group and be maintained in the <b class="uiTerm">Program Order View</b>, the operations: 
      </p>
      <ul>
         <li>
            <p class="para_item">Must be in the same geometry group</p>
         </li>
         <li>
            <p class="para_item">Must be in the same program group </p>
         </li>
         <li>
            <p class="para_item">Must appear in sequential order </p>
         </li>
      </ul>
      <p class="para_division">If there are operations from different programs between your ordered operations, then the order will not be maintained in the <b class="uiTerm">Program Order View</b>. For example, if there are three operations in one geometry group, but the third operation is in a different program, and operation 1 is moved to a position after operation 2, the order will be updated in the program view. However, if operation 1 is moved to after operation 3, the order in the <b class="uiTerm">Program Order View</b> will not be updated, because operation 3 is in a different program.
      </p>
      <p class="para_division">The relative order of consecutive operations within a geometry group is maintained in the <b class="uiTerm">Program Order View</b>, the order of the geometry groups in the <b class="uiTerm">Geometry View</b> is not. &nbsp;In other words, the order of operations in different geometry groups is not automatically maintained in the <b class="uiTerm">Program Order View</b>.
      </p>
      <p class="para_division">The Tool and Method Views have no effect on the <b class="uiTerm">Program Order View</b>. 
      </p>
      <p class="para_division">Operations in the <b class="uiTerm">Unused Items</b> group are not considered when determining the order between the Geometry and the Program Order Views.
      </p>
   </body>
</html>