<?xml version="1.0" encoding="iso-8859-1" standalone="yes" ?>
<rss version="2.0">
<channel>
<title>ESI-CFD FAQ - The five questions posted most recently:</title>
<description>FAQ for all CFD related products</description>
<link>http://www.esi-cfd.com/faq</link>	<item>
		<title><![CDATA[How to use the Copy/Paste Feature in CFD-ACE-GUI?]]></title>
		<description><![CDATA[<p>
As of V2009.0, CFD-ACE-GUI has the capability to copy/paste settings to similar entities
within a model, as well as across different models within the same CFD-ACE-GUI window. This can save on keystrokes when setting up your case.  It is especially useful
for cases where settings are repeated.  Just enter the desired setting for the first entity,
and simply copy and paste those settings to multiple entities at once.
</p>
<p>
<br />
The Model Explorer allows you to copy and paste settings for the following objects (or group of objects):
</p>
<ul>
	<li>
	Boundary Conditions</li>
	<li>Volume Conditions (Properties)</li>
	<li>Initial Conditions</li>
	<li>Momentum Resistance Regions</li>
	<li>Multiple Reference Frame Regions</li>
	<li>Fan Models</li>
	<li>Macro Particle Settings</li>
	<li>Spray Injector Settings</li>
</ul>
<p>
<br />
The steps are similar to any other copy &amp; paste procedure:
</p>
<ol>
	<li>Select the object with the settings you wish to copy. It can be done
	by clicking on the object (BC/VC, Fan, etc.) in the Model Explorer or Viewer window.</li>
	<li>Right-click the selected item. Choose "Copy ..." from the menu that
	pops up (see figure 1 below).
	<p align="center">
	<br />
	<img src="../images/stories/esi_user_tips/ut801_1.png" border="0" alt="Image" title="Image" hspace="6" width="570" height="244" />
	</p>
	<p align="center">
	<em><strong>Figure 1.  Copy/Paste feature in CFD-ACE-GUI</strong></em>
	</p>
	</li>
	<li>Select the objects (or a single object) on which you want to paste the settings.
	Right-click and choose "Paste from ..." as shown in figure 1.
	</li>
	<li>Click "Apply" on the right panel to save the changes. </li>
</ol>
<p>
 
</p>
<p align="right">
<span style="font-size: 12px; font-family: Arial"><em>Tested with V2011.0</em>
</span>
</p>
]]></description>
		<link>http://www.esi-cfd.com/faq/index.php?action=artikel&amp;cat=4&amp;id=12&amp;artlang=en</link>
		<pubDate>Tue, 15 May 2012 20:16:00 GMT</pubDate>
	</item>
	<item>
		<title><![CDATA[Is there an option to preserve boundaries between patches with CFD-VisCART’s Single Domain mesher?]]></title>
		<description><![CDATA[<p>
The ‘Preserve Features’ option does very well in preserving features between geometry
patches – as long as the patches are not coplanar (dihedral angle = 0) or include a very small
dihedral angle between them. As an example, let us consider the geometry shown in figure 1, where the
dihedral angle between the adjacent patches gradually reduces until the patches become coplanar.
</p>
<p align="center">
<img src="../images/stories/esi_user_tips/ut891_1.png" border="0" alt="Image" title="Image" hspace="6" width="518" height="352" />
</p>
<p align="center">
<em><strong>Figure 1.  Varying dihedral angle between adjacent patches</strong></em>
</p>
<p>
Generating a single domain volume mesh in CFD-VisCART for this case, with the
‘Preserve Features’ option activated, results in the surface mesh shown in figure 2.
As can be observed, the boundary between the patches is captured very well where the
dihedral angle is high, but as the dihedral angle decreases, the quality of boundary
capture deteriorates.
</p>
<p align="center">
<img src="../images/stories/esi_user_tips/ut891_2.png" border="0" alt="Image" title="Image" hspace="6" width="519" height="353" />
</p>
<p align="center">
<em><strong>Figure 2.  ‘Preserve Features’ option used with single
domain mesher - <br />
surface mesh shown</strong></em>
</p>
<p>
To address this issue, a new option called ‘Preserve Boundary Between Two Patches’
was introduced in CFD-VisCART V2011.0. It is available with the single domain mesher only and
can be found under the Advanced tab in the Generate Mesh dialog, as depicted in figure 3 below.
For the same model, activating this new option instead of the ‘Preserve Features’
option yields the surface mesh shown in figure 4. As can be seen, the boundary between
the patches is captured along the entire length of the model.
</p>
<p align="center">
<img src="../images/stories/esi_user_tips/ut891_3.png" border="0" alt="Image" title="Image" hspace="6" width="544" height="294" />
</p>
<p align="center">
<em><strong>Figure 3.  ‘Preserve Boundary Between Two Patches’ option</strong></em>
</p>
<p align="center">
<br />
<img src="../images/stories/esi_user_tips/ut891_4.png" border="0" alt="Image" title="Image" hspace="6" width="519" height="353" />
</p>
<p align="center">
<em><strong>Figure 4.  ‘Preserve Boundary Between Two Patches’ option used with
single domain mesher -<br />
surface mesh shown</strong></em>
</p>
<p>
In addition to capturing explicit boundaries (boundaries between adjoining patches),
this new option also enables the capture of implicit boundaries (for example, intersection of
overlapping parts). Free boundaries though are not captured using this new option.
</p>
<p>
<br />
To summarize, if it is required to capture different types of features and boundaries in the model,
our recommendation is to activate both the ‘Preserve Features’ and ‘Preserve
Boundary Between Two Patches’ options for best results.
</p>
<p>
 
</p>
<p align="right">
<span style="font-size: 12px; font-family: Arial"><em>Tested with V2011.0</em>
</span>
</p>
]]></description>
		<link>http://www.esi-cfd.com/faq/index.php?action=artikel&amp;cat=3&amp;id=192&amp;artlang=en</link>
		<pubDate>Wed, 09 May 2012 23:15:00 GMT</pubDate>
	</item>
	<item>
		<title><![CDATA[Is there an option in CFD-VisCART to keep a geometry part but make it invisible to the mesher?]]></title>
		<description><![CDATA[<p>
When performing an analysis comparing component A versus component B, it is useful to have
both components stored in the same file for physical comparison and documentation purposes.
However, when generating the mesh for the analysis, only one of the parts should be considered
at a time. The "Suppression" option in CFD-VisCART makes this possible.
</p>
<p>
Suppressing an entity makes it invisible to the mesher during the mesh generation phase.
The suppressed entity remains in the model and continues to be visible to the user.
This allows for the quick and convenient addition/removal of parts to/from the final computational
domain. 
</p>
<p>
Below is an example of a car model where the simulation goal is to characterize the effects
of the windshield position on the flowfield. Two simulations would be run, one for each
windshield position, so the model contains two windshield parts. The second
windshield part can be suppressed while the first is retained for the meshing phase,
thus obtaining the first DTF simulation file. Then, another mesh can be generated by
suppressing the first windshield and "unsuppressing" the second one, thus creating the
second simulation file.
</p>
<p align="center">
<img src="../images/stories/esi_user_tips/ut890_1.png" border="0" alt="Image" title="Image" hspace="6" width="598" height="358" />
</p>
<p align="center">
<em><strong>Figure 1.  Car model with two windshield parts</strong></em>
</p>
<p align="center">
<br />
<img src="../images/stories/esi_user_tips/ut890_2.png" border="0" alt="Image" title="Image" hspace="6" width="597" height="259" />
</p>
<p align="center">
<em><strong>Figure 2.  Suppression option</strong></em>
</p>
<p>
 
</p>
<p align="center">
<img src="../images/stories/esi_user_tips/ut890_3.png" border="0" alt="Image" title="Image" hspace="6" width="598" height="266" />
</p>
<p align="center">
<em><strong>Figure 3.  Mesh for each windshield position</strong></em>
</p>
<p>
<br />
The following entity types can be Suppressed/Unsuppressed:
</p>
<ul>
	<li>
	Geometry/Patches
	</li>
	<li>
	Domains
	</li>
	<li>
	Sources
	</li>
	<li>
	Gaps
	</li>
</ul>
<p>
NOTE: If you suppress a geometry part that has a source associated with it, you also need to
suppress the source. Failing to do so will result in an unintended refinement in the mesh.
</p>
<p>
 
</p>
<p align="right">
<span style="font-size: 12px; font-family: Arial"><em>Note: tested with V2011.0</em>
</span>
</p>
]]></description>
		<link>http://www.esi-cfd.com/faq/index.php?action=artikel&amp;cat=3&amp;id=191&amp;artlang=en</link>
		<pubDate>Wed, 25 Apr 2012 23:21:00 GMT</pubDate>
	</item>
	<item>
		<title><![CDATA[How to export STL files from CFD-GEOM?]]></title>
		<description><![CDATA[A CFD simulation process starts from an accurate representation of the boundaries that usually originates directly from CAD systems. STL and IGES are two of the most common output formats used as a starting point for mesh generation. STL (StereoLithography) files represent 3D surface geometries using a triangular mesh allowing unambiguous transfer of files from one system to another. Each patch in a STL file is defined by three points and an orientation vector.
<p>
 
</p>
<p>
CFD-GEOM, an integrated geometry modeling and grid generation tool, supports the export of geometries and meshes in several different output formats. Traditionally,CFD-GEOM users have been able to write out ASCII STL files with consistent orientation from triangulated surface meshes. From V2008.2, CFD-GEOM also allows export of quad surface meshes (generated as structured or unstructured) into STL files. Quad facets are automatically split into triangles as per STL requirements. For structured meshes, only 2D blocks (not faces) can be exported.
</p>
<p align="center">
<img src="../images/stories/esi_user_tips/ut778_1.png" border="0" alt="Image" title="Image" hspace="6" width="504" height="196" />
</p>
<p align="center">
<em><strong>Figure 1.  &#39;Save STL files&#39; option from File menu</strong></em>
</p>
<p>
These files can be opened later in any tool supporting STL files such as CFD-VisCART and
CFD-VIEW for mesh generation or visualization purposes.
</p>
<p align="center">
<img src="../images/stories/esi_user_tips/ut778_2.png" border="0" alt="Image" title="Image" hspace="6" width="595" height="244" />
</p>
<p align="center">
<em><strong>Figure 2.  Examples of exported STLs from triangular and quad surface meshes</strong></em>
</p>
<p>
The exported STL files can also be imported into CFD-GEOM as a discrete surface for further manipulations. A newly implemented discrete modeling engine in CFD-GEOM can import and manipulate meshed surfaces from several external grid formats. <span> </span>Some of the available tools include:
</p>
<ol style="margin-top: 0in">
	<li>Creation of discrete surfaces from lines and CAD surfaces</li>
	<li>Extracting outlines and critical features</li>
	<li>Split at outlines and critical features</li>
	<li>Boolean operations on closed surfaces</li>
</ol>
<p align="center">
<img src="../images/stories/esi_user_tips/ut778_3.png" border="0" alt="Image" title="Image" hspace="6" width="590" height="478" />
</p>
<p align="center">
<em><strong>Figure 3.  Discrete surface operations showing union of different closed surfaces, <br />
intersection with a plane, and splitting using outlines and critical features</strong></em>
</p>
<p>
<br />
In future releases, CFD-GEOM users could expect more powerful features including re-meshing of imported discrete surfaces and tet mesh generation from re-meshed discrete surfaces.
</p>
]]></description>
		<link>http://www.esi-cfd.com/faq/index.php?action=artikel&amp;cat=2&amp;id=24&amp;artlang=en</link>
		<pubDate>Wed, 18 Apr 2012 21:11:00 GMT</pubDate>
	</item>
	<item>
		<title><![CDATA[Is it possible to work with cell-center data with CFD-VIEW in batch mode?]]></title>
		<description><![CDATA[<p>
Many improvements have been made in CFD-VIEW that allows the manipulation of cell-center data.
The latest cell-center data additions implemented in CFD-VIEW V2011.0 include, for example,
support for the MinMax Probe and the Calculator.
</p>
<p>
A recent feature improvement makes working with cell-center data even more versatile,
as it allows users to work with such data in batch mode. Indeed, the CFD-VIEW scripting function
<strong>ImportDTF</strong> has been extended to include most of the options available from the GUI
“Import Data File” facility, shown in figure 1 below. One of these added options is the
“Cell” option, meaning that cell-center data can now be fully used with CFD-VIEW
scripting, whether from the GUI or in batch mode.
</p>
<p align="center">
<img src="../images/stories/esi_user_tips/ut889_1.png" border="0" alt="Image" title="Image" hspace="6" width="506" height="459" />
</p>
<p align="center">
<em><strong>Figure 1.  CFD-VIEW GUI “Import Data File” facility</strong></em>
</p>
<p>
<br />
The improved ImportDTF scripting function has the following prototype:
</p>
<p>
ImportDTF(filename, importMethod=DTF_ZONE_BASED, simnum=1, cell=0, spray=DTF_SPRAY_NONE, blanking=0,
grouping=0, unscaled=0, nozero=0, animation=0)
</p>
<p>
Note that in usage, the names of the arguments should not be included, only the values should.
For example if one wants to import a DTF in Zone Based mode, with Formatted Spray and Grouping
options, one would use:
</p>
<p>
ImportDTF(“C:/docs/filename.DTF”, <strong>DTF_ZONE_BASED</strong>, 1, 0,
<strong>DTF_SPRAY_FORMATTED</strong>, 0, <strong>1</strong>, 0, 0, 0)
</p>
<p>
 
</p>
<p>
<strong><span style="font-size: 12pt">Example</span></strong>
</p>
<p>
Following is an example of a CFD-VIEW script that makes use of the ImportDTF function and the
Calculator with cell-center data.
</p>
<p>
The simulation used is a 2D radial flow, as depicted in figure 2 below. 
</p>
<p align="center">
<img src="../images/stories/esi_user_tips/ut889_2.png" border="0" alt="Image" title="Image" hspace="6" width="594" height="467" />
</p>
<p align="center">
<em><strong>Figure 2.  Radial velocity simulation example -<br />
Nodal velocity magnitude and vectors displayed</strong></em>
</p>
<p>
<br />
The script imports the DTF with cell-center data and calculates the cell-center radial and
tangential velocity components in polar coordinates. It should be expected that the tangential
component will essentially be zero, and that the radial component will carry the full magnitude of
the velocity.
</p>
<p>
Below are the details of this script, which makes use of the improved ImportDTF function with
“cell” option, as well as the extended calculator functionality for cell-center data
support.
</p>
<p align="center">
<img src="../images/stories/esi_user_tips/ut889_3.png" border="0" alt="Image" title="Image" hspace="6" width="562" height="552" />
</p>
<p>
<br />
If you run this script in batch mode (&lt;XCFD-VIEW -nogui -s polar_velocity.py&gt;) and open the
resulting MDL file, you can visualize the cell-center polar velocity components, presented in
figure 3.
</p>
<p align="center">
<br />
<img src="../images/stories/esi_user_tips/ut889_4.png" border="0" alt="Image" title="Image" hspace="6" width="599" height="298" />
</p>
<p align="center">
<em><strong>Figure 3.  Cell-center polar velocity components</strong></em>
</p>
<p>
 
</p>
<p>
You can download the DTF and Python script files used in the example by clicking on this
<a href="../images/stories/esi_user_tips/polar_velocity.zip">link</a>.
</p>
<p>
 
</p>
<p align="right">
<span style="font-size: 12px; font-family: Arial"><em>Note: tested with V2011.0</em>
</span>
</p>
]]></description>
		<link>http://www.esi-cfd.com/faq/index.php?action=artikel&amp;cat=6&amp;id=190&amp;artlang=en</link>
		<pubDate>Tue, 10 Apr 2012 22:34:00 GMT</pubDate>
	</item>
</channel>
</rss>
