<!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>MetaForm region boundary</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">MetaForm region boundary</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('sheetmetaldes/smfea_metaform.html');return(false);">MetaForm Overview</a></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td">Options</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('sheetmetaldes/metaform_tips.html');return(false);">Related Topics</a></p>
            </td>
         </tr>
      </table><br><p class="para_topic">Select faces to define the region boundary. The filter allows you to filter between <b class="uiTerm">Any </b>,<b class="uiTerm">Face</b>, <b class="uiTerm">G1&ndash;Faces</b>, or<b class="uiTerm">Sheet</b> face sheet.
      </p>
      <ul>
         <li>
            <p class="para_item"><b class="uiTerm">Any</b> &ndash; select any face or sheet body (default filter).
            </p>
         </li>
         <li>
            <p class="para_item"><b class="uiTerm">Face</b> &ndash; select any face.
            </p>
         </li>
         <li>
            <p class="para_item"><b class="uiTerm">G1&ndash;Faces</b> &ndash; only select faces that are G1 continuous with the first face selected.
            </p>
         </li>
         <li>
            <p class="para_item"><b class="uiTerm">Sheet</b> &ndash; select any sheet body. This will select all faces within that sheet body.
            </p>
         </li>
      </ul>
      <p class="para_topic">The cue message for this selection step is: Select faces to define region boundary.</p>
      <div class="title_division">Target boundary</div>
      <p class="para_division">Select faces to define the target boundary. The region faces will be mapped to this set of faces. The filter lets you pick the following:</p>
      <ul>
         <li>
            <p class="para_item"><b class="uiTerm">Any</b> &ndash; select any face or sheet body.
            </p>
         </li>
         <li>
            <p class="para_item"><b class="uiTerm">Face</b> &ndash; select any face.
            </p>
         </li>
         <li>
            <p class="para_item"><b class="uiTerm">G1&ndash;Faces</b> &ndash; only select faces that are G1 continuous with the first face selected.
            </p>
         </li>
         <li>
            <p class="para_item"><b class="uiTerm">Sheet</b> &ndash; select any sheet body. This will select all faces within that sheet body.
            </p>
         </li>
      </ul>
      <div class="title_division">Boundary conditions</div>
      <p class="para_division">Boundary conditions define how the region finite element mesh is formed to the target boundary. The <b class="uiTerm">Boundary Conditions</b> selection will not be sensitive until you select at least one region boundary object and one target boundary object. The filter lets you pick the following:
      </p>
      <ul>
         <li>
            <p class="para_item"><b class="uiTerm">Any</b> &ndash; select any curve, edge, or point (default).
            </p>
         </li>
         <li>
            <p class="para_item"><b class="uiTerm">Curve</b> &ndash; select any curve.
            </p>
         </li>
         <li>
            <p class="para_item"><b class="uiTerm">Edge</b> &ndash; select any edge.
            </p>
         </li>
         <li>
            <p class="para_item"><b class="uiTerm">Point</b> &ndash; select any point.
            </p>
         </li>
      </ul>
      <p class="para_division">The <b class="uiTerm">Boundary Conditions</b> control the mapping by providing point&ndash;to&ndash;point and curve&ndash;to&ndash;curve constraints. These conditions indicate, for example, that a point on the region boundary will map to an explicit point on the target boundary.
      </p>
      <p class="para_division">When you select an object, the system will determine if the object should be associated with the region or target boundary depending on it proximity to either set of faces.</p>
      <p class="para_division">Each boundary condition is a named object in the <b class="uiTerm">Boundary Condition</b> list box. The dialog box allows you to create, rename, and delete <b class="uiTerm">Boundary Conditions</b>.
      </p>
      <table bgcolor="#F0F0F0" cellpadding="2" cellspacing="4" width="95%" align="center">
         <colgroup span="1">
            <col span="1" width="58*">
            <col span="1" width="140*">
         </colgroup>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><b class="uiTerm">List Box</b></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td">The list box shows all boundary conditions already defined. The highlighted boundary condition name will receive any selections.</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><b class="uiTerm">Boundary Condition Name</b></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td">The name of the highlighted boundary condition is shown in the dynamic input box. Enter a different name into this box in order to rename a boundary condition. If the box is empty when you create a new boundary condition, the system will assign a name.</p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td"><b class="uiTerm">Create</b></p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td">Select this button to create a new boundary condition. If the name box is empty, the system will automatically assign a name.</p>
               <p class="para_td">You can select the <b class="uiTerm">Create Boundary</b> button with the <b class="uiTerm">Name</b> field empty. If this happens a default name will be used. If you wish to create a boundary with a specific name enter the name in the <b class="uiTerm">Name</b> field and then select <b class="uiTerm">Create</b>. Initially, there will not be any default boundary conditions specified. However, you are required to provide at least one boundary condition. Therefore, you will be required to create at least one boundary condition name before selection of the objects that define the boundary condition can proceed.
               </p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td">Rename</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td">Enter a different name into the dynamic input box, and then press the <b class="uiTerm">Rename</b> button in order to rename a boundary condition. The <b class="uiTerm">Rename</b> button will not be sensitive until the current selection step is on <b class="uiTerm">Boundary Conditions</b>, a row has been selected from the <b class="uiTerm">Boundary Conditions</b> list box, and a new name has been entered in the dynamic input box of the <b class="uiTerm">Boundary Condition</b> list.
               </p>
            </td>
         </tr>
         <tr valign="top">
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td">Delete</p>
            </td>
            <td bgcolor="#f7f7f7" colspan="1" rowspan="1">
               <p class="para_td">Press this button to delete the highlighted boundary condition. The <b class="uiTerm">Delete</b> button will not be sensitive until a row in the current selection step is on <b class="uiTerm">Boundary Conditions</b> and a row has been selected from the <b class="uiTerm">Boundary Condition</b> list box. The <b class="uiTerm">Delete</b> button will remove the row that has been selected from the <b class="uiTerm">Boundary Condition</b> list box.
               </p>
            </td>
         </tr>
      </table><br><p class="para_division">A minimum of one boundary condition must be created and selected before a metaform analysis can be performed.&nbsp;You may specify either <b class="uiTerm">Point&ndash;to&ndash;Point</b> or <b class="uiTerm">Profile&ndash;to&ndash;Profile</b> constraints.
      </p>
      <p class="para_division">The cue message for this option is: Select objects on region boundary and target boundary to define boundary condition.</p>
      <p class="para_division">When defining a <b class="uiTerm">Point&ndash;to&ndash;Point</b> constraint, you are required to select a point on the region boundary and a corresponding point on the target boundary. The exception to this rule will apply if a selected point resides on both the region and target boundaries at the same time. For this case, the default behavior will consider the initial and final state of the constraint to be coincident.&nbsp;The number of points that may be specified for a single boundary condition will be 2 (for example, one on the region boundary and one on the target boundary).&nbsp;If a different point is selected, the original point will automatically be deselected and the new point will be used.
      </p>
      <p class="para_division">When defining a <b class="uiTerm">Profile&ndash;to&ndash;Profile</b> constraint, you will be required to select a profile on the region boundary and a corresponding profile on the mapping boundary.&nbsp;As with election of a <b class="uiTerm">Point&ndash;to&ndash;Point</b> constraint, the exception to this rule will apply if a selected profile resides on both the region and mapping boundaries at the same time. Again, the default behavior for this case will consider the initial and final state of the constraint to be coincident. The maximum number of continuous profiles that may be specified for a single boundary will be 2, (for example, one continuous profile on the region boundary and one continuous profile on the target boundary). A profile may consist of more than one edge/curve combination. Validation will be performed to ensure that the selected edges/curves can be joined into a single curve before you can proceed with the region analysis, (for example, all boundary conditions must be resolved before <b class="uiTerm">OK/Apply</b> can be used).
      </p><a class="endOfDocLinks" href="map_geometry.html">MetaForm mapping geometry</a><br></body>
</html>