<!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>IPW Behavior for Operations that Use the IPW as Blank</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_topic5" id="xps10_pagetitle">IPW Behavior for Operations that Use the IPW as Blank</div>
      <hr noshade="true">
      <p class="para_topic">The following describes various IPW behaviors for any operation that uses the IPW as blank, such as Cavity Milling and Plunge Milling.</p>
      <table border="0">
         <tr>
            <td valign="top" align="left"><img align="left" src="../graphics/note.gif" alt="Note" title="Note"></td>
            <td valign="bottom" align="left" width="100%">
               <div class="para_note">
                  <p class="para_note_body">The <b class="uiTerm">In-process Workpiece</b> options are <b class="uiTerm">Use Level Based</b> and <b class="uiTerm">Use 3D</b>. Plunge Milling only uses the 3D option.
                  </p>
               </div>
            </td>
         </tr>
      </table>
      <table border="1" cellspacing="0" width="100%" align="center">
         <tr valign="top">
            <th colspan="1" rowspan="1" width="50%">
               <p class="para_th">Situation</p>
            </th>
            <th colspan="1" rowspan="1" width="50%">
               <p class="para_th">Behavior</p>
            </th>
         </tr>
         <tr valign="top">
            <td colspan="1" rowspan="3" width="50%">
               <p class="para_td">Any Cavity Mill or Plunge Milling operation that has the <b class="uiTerm">In-process Workpiece</b> option turned on.
               </p>
            </td>
            <td colspan="1" rowspan="1" width="50%">
               <p class="para_td">The software traverses back up the program view hierarchy to find an operation with a  <a class="links" href="javascript:void(0)" onclick="top.openFile('mfgmilling/ipw_toolpaths.html#pcmill_cav_blk_geom_ipw_valid_input_req');return(false);">valid in-process workpiece</a> that refers to the same initial workpiece. Whether such an operation with a valid in-process workpiece is found or not, the software always ensures that all the operations in the relevant geometry group and program view hierarchy have a valid tool path. &nbsp;It also checks to see whether a &nbsp;blank definition was available&nbsp;to define the initial work piece for the first operation in the relevant geometry group. &nbsp;If any of these conditions are not met, it issues an error message.
               </p>
            </td>
         </tr>
         <tr valign="top">
            <td colspan="1" rowspan="1" width="50%">
               <p class="para_td">The software automatically generates the in-process workpiece each time the tool path is generated using the operation's Generate action from the <b class="uiTerm">Operation Navigator</b>, as long as all the other  <a class="links" href="javascript:void(0)" onclick="top.openFile('mfgmilling/ipw_toolpaths.html#pcmill_cav_blk_geom_ipw_valid_input_req');return(false);">requirements for generating a valid in-process workpiece</a> are satisfied.
               </p>
            </td>
         </tr>
         <tr valign="top">
            <td colspan="1" rowspan="1" width="50%">
               <p class="para_td">Any inherited blank geometry is ignored and the in-process workpiece model is used instead. &nbsp;The software does not allow the use of blank geometry and the&nbsp;<b class="uiTerm">In-process Workpiece</b> option at the same time in any operation.
               </p>
            </td>
         </tr>
         <tr valign="top">
            <td colspan="1" rowspan="1" width="50%">
               <p class="para_td">An operation with a valid in-process workpiece is found in the sequence.</p>
            </td>
            <td colspan="1" rowspan="1" width="50%">
               <p class="para_td">The software uses the in-process workpiece as a reference, and then applies the tool path from all the subsequent operations up to the current operation, to this reference in-process workpiece. &nbsp;It stores the resultant in-process workpiece with this operation after applying the current operation's tool path to the reference in-process workpiece.</p>
               <table border="0">
                  <tr>
                     <td valign="top" align="left"><img align="left" src="../graphics/note.gif" alt="Note" title="Note"></td>
                     <td valign="bottom" align="left" width="100%">
                        <div class="para_note">
                           <p class="para_note_body">The <b class="uiTerm">Use Level Based</b> IPW option will only consider other cavity milling and zlevel operations. Other operations are ignored. 
                           </p>
                        </div>
                     </td>
                  </tr>
               </table>
            </td>
         </tr>
         <tr valign="top">
            <td colspan="1" rowspan="1" width="50%">
               <p class="para_td">An operation with a valid in-process workpiece is not found in the sequence, but all the preceding operations in the sequence have a valid tool path.</p>
            </td>
            <td colspan="1" rowspan="1" width="50%">
               <p class="para_td">The software applies all these tool paths to the blank defined for the first operation in the sequence that inherits the initial workpiece. &nbsp;It stores the resultant in-process workpiece with this operation after applying the current operation's tool path to the reference in-process workpiece.</p>
            </td>
         </tr>
         <tr valign="top">
            <td colspan="1" rowspan="1" width="50%">
               <p class="para_td">Any operation which is being edited and has&nbsp;<b class="uiTerm">In-process Workpiece</b> turned on.
               </p>
            </td>
            <td colspan="1" rowspan="1" width="50%">
               <p class="para_td">The software automatically generates the resultant in-process workpiece when you accept the edits by using the <b class="uiTerm">OK</b> action on the edit dialog, as long as the tool path has been generated during the particular edit session. &nbsp;The software also ensures that all the other  <a class="links" href="javascript:void(0)" onclick="top.openFile('mfgmilling/ipw_toolpaths.html#pcmill_cav_blk_geom_ipw_valid_input_req');return(false);">requirements for generating a valid in-process workpiece</a> are satisfied.
               </p>
            </td>
         </tr>
         <tr valign="top">
            <td colspan="1" rowspan="1" width="50%">
               <p class="para_td">Any operation which is marked as <b class="uiTerm">Regenerate</b> and needs to be regenerated.
               </p>
            </td>
            <td colspan="1" rowspan="1" width="50%">
               <p class="para_td">All the subsequent operations in the program group and the geometry group hierarchy that refer to the same initial workpiece are also marked as <b class="uiTerm">Regenerate</b>, if they have&nbsp;<b class="uiTerm">In-process Workpiece</b> turned on or have an in-process workpiece object generated.
               </p>
            </td>
         </tr>
         <tr valign="top">
            <td colspan="1" rowspan="1" width="50%">
               <p class="para_td">The state of this option is changed for any operation.</p>
            </td>
            <td colspan="1" rowspan="1" width="50%">
               <p class="para_td">The tool path status of the concerned operation and the successive operations in the program view hierarchy that share the same initial workpiece are changed to <b class="uiTerm">Regenerate</b>.
               </p>
            </td>
         </tr>
      </table><br></body>
</html>