<!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>Options</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_topic2" id="xps10_pagetitle">Options</div>
      <hr noshade="true">
      <table cellspacing="4" align="center">
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('translatoruser/iges_imp_adv_set.html');return(false);">Overview</a></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td">Options</p>
            </td>
         </tr>
      </table><br><div class="title_division">Copious data</div>
      <p class="para_division"><b class="uiTerm">Copious Data</b> maps to the following options: <b class="uiTerm">Linear Nurb Splines</b>, <b class="uiTerm">Cubic Nurb Best Fit Splines</b>, or <b class="uiTerm">Groups of Lines</b>. IGES file crosshatching and other drafting entities may be written to <b class="uiTerm">Copious Data</b>. When crosshatch data maps to copious data it becomes individual lines, which make up the crosshatch. This option allows you to specify which type of lines you would like the crosshatch mapped to. The <b class="uiTerm">Linear Nurb Splines</b> option is the default option.
      </p>
      <div class="title_division">Map view dependent / Modified entity</div>
      <p class="para_division">A view dependent or view modified entity in IGES maps to either an entity that has the same view dependency or view modification as detailed in the IGES file or it maps to a model entity, being seen in all NX views. Any entity that has a zero in the View Field in the IGES file creates as a model entity in NX. When this field is non&ndash;zero, the entity is either view dependent or view modified. If this option is on, all entities in the IGES file will create in model space. The default is to map these entities as view dependent modified entities.</p>
      <div class="title_division">Smooth B-surface</div>
      <p class="para_division">When this option is on, removing knots that have a multiplicity equal to the degree of the surface will do a smoothing of an IGES b-surface. This happens only for non-rational b-surfaces. An IGES surface that converts to a b-surface during translation will also have the smoothing performed. The purpose of this option is to ensure that an IGES b-surface processes into a single NX sheet to allow it to trim interactively as one sheet. If this option is off some smoothing will happen but only within the Parasolid linear resolution, which is tighter than many surfaces would require.</p>
      <div class="title_division">Flatten assembly</div>
      <p class="para_division">When this option is on, IGES sub-figure entities will import directly into the part. If off, then sub-figures become NX components.</p>
      <div class="title_division">Automatic sewing of surfaces</div>
      <p class="para_division">This option allows you to automatically sew surfaces together as a solid as part of the translation.</p>
      <p class="para_division">The sewing completes once all of the data successfully imports into NX. The sewing process attempts to sew all surfaces together as best it can. The algorithm repeatedly cycles the sewing process (at a fixed tolerance of 0.1 mm), omitting problem surfaces at each stage in an attempt to obtain a good sewn body. The system will make five attempts to sew the surfaces before deciding that the sew process cannot complete. This algorithm allows it to handle gaps between surfaces and include the appropriate sheet bodies in most cases. Surfaces, which create non-manifold conditions, are not included in the sewn solid.</p>
      <p class="para_division">The purpose of this option is to save time when you need complete bodies.</p>
      <div class="title_division">Layer default for level 0</div>
      <p class="para_division">The <b class="uiTerm">Layer Default for Level 0</b> option allows you to specify which NX layer is to be assigned to entities specified in the input STEP file as being on Layer 0 in the originating system.
      </p>
      <p class="para_division">Corresponds to default file option ZERO_LAYER_DEFAULT.</p>
      <p class="para_division">In addition STEP layers will map to NX layers as follows:</p>
      <p class="para_division">STEP layer 0&rarr;user input</p>
      <p class="para_division">STEP layers 1&ndash;256&rarr;NX layers 1&ndash;256</p>
      <p class="para_division">STEP layers 257&ndash;512&rarr;NX layers 1&ndash;256</p>
      <p class="para_division">STEP layers 513&ndash;768&rarr;NX layers 1&ndash;256</p>
      <p class="para_division">etc.</p>
      <p class="para_division">(for example, STEP layer 257&rarr;NX layer 1</p>
      <p class="para_division">STEP layer 258&rarr;NX layer 2)</p>
      <p class="para_division">Layer Default for Level 0:1</p>
   </body>
</html>