You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<li><b>Add the module to <spanclass="tt">docs/module_categories.json</span></b> so it appears in this page</li>
404
404
</ol>
405
405
<p>Follow the pattern of existing modules like <spanclass="tt">m_body_forces</span> (simple) or <spanclass="tt">m_viscous</span> (more involved) as a template.</p>
<li><spanclass="tt">cantera_file</span> specifies the chemical mechanism file. If the file is part of the standard Cantera library, only the filename is required. Otherwise, the file must be located in the same directory as your <spanclass="tt">case.py</span> file</li>
<tdclass="markdownTableBodyRight"><spanclass="tt">bc_[x,y,z]%isothermal_in</span></td><tdclass="markdownTableBodyCenter">Logical </td><tdclass="markdownTableBodyLeft">Enable isothermal wall at the domain entrance (minimum coordinate). </td></tr>
1315
+
<trclass="markdownTableRowEven">
1316
+
<tdclass="markdownTableBodyRight"><spanclass="tt">bc_[x,y,z]%isothermal_out</span></td><tdclass="markdownTableBodyCenter">Logical </td><tdclass="markdownTableBodyLeft">Enable isothermal wall at the domain exit (maximum coordinate). </td></tr>
1317
+
<trclass="markdownTableRowOdd">
1318
+
<tdclass="markdownTableBodyRight"><spanclass="tt">bc_[x,y,z]%Twall_in</span></td><tdclass="markdownTableBodyCenter">Real </td><tdclass="markdownTableBodyLeft">Temperature [K] of the entrance isothermal wall. </td></tr>
1319
+
<trclass="markdownTableRowEven">
1320
+
<tdclass="markdownTableBodyRight"><spanclass="tt">bc_[x,y,z]%Twall_out</span></td><tdclass="markdownTableBodyCenter">Real </td><tdclass="markdownTableBodyLeft">Temperature [K] of the exit isothermal wall. </td></tr>
1321
+
</table>
1322
+
<p>This boundary condition can be used for fixed-temperature (isothermal) walls at the domain extremities. It is exclusively available for reacting flows and requires chemistry to be enabled. It properly evaluates heat and species fluxes at the interface when <spanclass="tt">chemistry = 'T'</span>, <spanclass="tt">chem_params%diffusion = 'T'</span>, and the corresponding domain boundary is set to a slip wall (<spanclass="tt">bc_[x,y,z]%%[beg,end]</span> = -15) or a no-slip wall (<spanclass="tt">bc_[x,y,z]%%[beg,end]</span> = -16).</p>
<li>These parameters are for NVIDIA Grace-Hopper and similar architectures with hardware-managed unified memory. They allow MFC to run problems larger than GPU memory by paging data between host and device.</li>
<p>*: This boundary condition is only used for <spanclass="tt">bc_y%beg</span> when using cylindrical coordinates (<spanclass="tt">cyl_coord = 'T'</span> and 3D). For axisymmetric problems, use <spanclass="tt">bc_y%beg = -2</span> with <spanclass="tt">cyl_coord = 'T'</span> in 2D.</p>
1362
1377
<p>The boundary condition supported by the MFC are listed in table <aclass="el" href="#boundary-conditions" title="Boundary conditions">Boundary Conditions</a>. Their number (<spanclass="tt">#</span>) corresponds to the input value in <spanclass="tt">input.py</span> labeled <spanclass="tt">bc_[x,y,z]%[beg,end]</span> (see table <aclass="el" href="#sec-simulation-algorithm" title="6. Simulation Algorithm">Simulation Algorithm Parameters</a>). The entries labeled "Characteristic." are characteristic boundary conditions based on Thompson <aclass="el" href="citelist.html#CITEREF_thompson87">[47]</a> and Thompson <aclass="el" href="citelist.html#CITEREF_thompson90">[48]</a>.</p>
<li><spanclass="tt">%support = 10</span> specifies an annular transducer array in 2D axisymmetric simulation. It is identical to <spanclass="tt">%support = 9</span> in terms of simulation parameters. It physically represents the a annulus obtained by revolving the arc in <spanclass="tt">%support = 9</span> around the x-axis.</li>
1510
1525
<li><spanclass="tt">%support = 11</span> specifies a circular transducer array in 3D simulation. The total aperture of the array is <spanclass="tt">%aperture</span>, which is similar to <spanclass="tt">%support = 7</span>. The parameters <spanclass="tt">%num_elements</span>, <spanclass="tt">%element_polygon_ratio</span>, and <spanclass="tt">%rotate_angle</span> 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 <spanclass="tt">%num_elements</span>. 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>
<p><b>Learn by example:</b> The cases below are curated from MFC's <spanclass="tt">examples/</span> directory and are validated, working configurations. Use them as blueprints for building your own simulations. </p>
<p>💡 <b>Tip:</b> If you encounter a validation error, check the relevant section above or review <ahref="https://github.com/MFlowCode/MFC/blob/master/toolchain/mfc/case_validator.py"><spanclass="tt">case_validator.py</span></a> for complete validation logic.</p>
<p>Welcome to the MFC master script. This tool automates and manages building, testing, running, and cleaning of MFC in various configurations on all supported platforms. The README documents this tool and its various commands in more detail. To get started, run <spanclass="tt">./mfc.sh build -h</span>.</p>
<tdclass="markdownTableBodyNone"><aclass="el" href="#count_diff" title="count_diff"><code>count_diff</code></a></td><tdclass="markdownTableBodyNone">- </td><tdclass="markdownTableBodyNone">Compare LOC between branches. </td></tr>
<tdclass="markdownTableBodyNone"><spanclass="tt">-o</span>, <spanclass="tt">--output</span></td><tdclass="markdownTableBodyNone">Base name of output file. </td><tdclass="markdownTableBodyNone">- </td></tr>
0 commit comments