<a href="md_case.html#autotoc_md28"/>

<a href="md_case.html#autotoc_md29"/>

<a href="md_case.html#autotoc_md3"/>

<a href="md_case.html#autotoc_md4"/>

<a href="md_case.html#autotoc_md5"/>

<a href="md_case.html#autotoc_md6"/>

<a href="md_case.html#autotoc_md7"/>

<a href="md_case.html#autotoc_md8"/>

<a href="md_case.html#autotoc_md9"/>

<a href="md_examples.html"/>

<a href="md_examples.html#autotoc_md32"/>

<a href="md_examples.html#autotoc_md33"/>

<a href="md_examples.html#autotoc_md34"/>

<a href="md_examples.html#autotoc_md75"/>

<a href="md_examples.html#autotoc_md76"/>

<a href="md_examples.html#autotoc_md77"/>

<a href="md_expectedPerformance.html"/>

<a href="md_expectedPerformance.html#autotoc_md80"/>

<a href="md_expectedPerformance.html#autotoc_md81"/>

<a href="md_expectedPerformance.html#autotoc_md82"/>

<a href="md_expectedPerformance.html#autotoc_md86"/>

<a href="md_expectedPerformance.html#autotoc_md87"/>

<a href="md_expectedPerformance.html#autotoc_md88"/>

<a href="md_getting-started.html"/>

<a href="md_getting-started.html#autotoc_md91"/>

<a href="md_getting-started.html#autotoc_md92"/>

<a href="md_getting-started.html#autotoc_md93"/>

<a href="md_getting-started.html#autotoc_md94"/>

<a href="md_papers.html"/>

<a href="md_readme.html"/>

<a href="md_readme.html#autotoc_md98"/>

<a href="md_references.html"/>

<a href="md_running.html"/>

<a href="md_running.html#autotoc_md102"/>

<a href="md_running.html#autotoc_md103"/>

<a href="md_running.html#autotoc_md104"/>

<a href="md_running.html#autotoc_md105"/>

<a href="md_running.html#autotoc_md106"/>

<a href="md_running.html#autotoc_md107"/>

<a href="md_testing.html"/>

<a href="md_testing.html#autotoc_md110"/>

<a href="md_visualization.html"/>

<a href="md_visualization.html#autotoc_md113"/>

<a href="md_visualization.html#autotoc_md114"/>

<a href="md_visualization.html#autotoc_md115"/>

<a href="md_visualization.html#autotoc_md116"/>

<a href="md_visualization.html#autotoc_md117"/>

<a href="md_visualization.html#autotoc_md118"/>

<a href="md_visualization.html#autotoc_md119"/>

<a href="pages.html"/>

<p>*: This boundary condition is only used for <code>bc_y%beg</code> when using cylindrical coordinates (<code>cyl_coord = 'T'</code> and 3D). For axisymmetric problems, use <code>bc_y%beg = -2</code> with <code>cyl_coord = 'T'</code> in 2D.</p>

<p>The boundary condition supported by the MFC are listed in table Boundary Conditions. Their number (<code>#</code>) corresponds to the input value in <code>input.py</code> labeled <code>bc_[x,y,z]%[beg,end]</code> (see table Simulation Algorithm Parameters). The entries labeled "Characteristic." are characteristic boundary conditions based on <a href="references.md#Thompson87">Thompson (1987)</a> and <a href="references.md#Thompson90">Thompson (1990)</a>.</p>

<h2><a class="anchor" id="autotoc_md26"></a>

Patch types</h2>

<table class="markdownTable">

<tr class="markdownTableHead">

<td class="markdownTableBodyRight">21 </td><td class="markdownTableBodyCenter">Model </td><td class="markdownTableBodyCenter">2 &amp; 3 </td><td class="markdownTableBodyCenter">Y </td><td class="markdownTableBodyLeft">Imports a Model (STL/OBJ). Requires <code>model%filepath</code>. </td></tr>

<p>The patch types supported by the MFC are listed in table Patch Types. This includes types exclusive to one-, two-, and three-dimensional problems. The patch type number (<code>#</code>) corresponds to the input value in <code>input.py</code> labeled <code>patch_icpp(j)%geometry</code> where $j$ is the patch index. Each patch requires a different set of parameters, which are also listed in this table.</p>

Immersed Boundary Patch Types</h2>

<table class="markdownTable">

<tr class="markdownTableHead">

<li><code>%support = 10</code> specifies an annular transducer array in 2D axisymmetric simulation. It is identical to <code>%support = 9</code> in terms of simulation parameters. It physically represents the a annulus obtained by revolving the arc in <code>%support = 9</code> around the x-axis.</li>

<li><code>%support = 11</code> specifies a circular transducer array in 3D simulation. The total aperture of the array is <code>%aperture</code>, which is similar to <code>%support = 7</code>. The parameters <code>%num_elements</code>, <code>%element_polygon_ratio</code>, and <code>%rotate_angle</code> specify the number of transducer elements, the ratio of the polygon side length to the transducer element radius, and the rotation angle of the array. The polygon side length is calculated by using the total aperture as the circumcicle diameter, and the number of sides of the polygon as <code>%num_elements</code>. The ratio is used specify the aperture size of each transducer element in the array, as a ratio of the total aperture. The rotation angle is optional and defaults to 0. Physically it represents a circular ring of transducer elements.</li>

Conservative Variables Ordering</h2>

<table class="markdownTable">

<tr class="markdownTableHead">

<td class="markdownTableBodyNone">hypoelastic variables </td><td class="markdownTableBodyNone">N/A </td></tr>

<p>The above variables correspond to optional physics.</p>

Primitive Variables Ordering</h2>

<table class="markdownTable">

<tr class="markdownTableHead">