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
</div><!-- fragment --><h3><aclass="anchor" id="autotoc_md9"></a>
330
329
Hard Coded Patches</h3>
331
330
<p>Some patch configurations are not adequately handled with the above analytic variable definitions. In this case, a hard coded patch can be used. Hard coded patches can be added by adding additional hard coded patch identifiers to <code>src/pre_process/include/1[2,3]dHardcodedIC.fpp</code>. For example, to add a 2D Hardcoded patch with an id of 200, one would add the following to <code>src/pre_process/include/2dHardcodedIC.fpp</code></p>
</div><!-- fragment --><p>and use <code>patch_icpp(i)%geometry = 7</code> and <code>patch_icpp(i)%hcid = 200</code> in the input file. Additional variables can be declared in <code>Hardcoded1[2,3]DVariables</code> and used in <code>hardcoded1[2,3]D</code>. As a convention, any hard coded patches that are part of the MFC master branch should be identified as 1[2,3]xx where the first digit indicates the number of dimensions.</p>
<divclass="textblock"><p>The purpose of the module is primarily to read in the files that contain the inputs, the initial condition data and the grid data that are provided by the user. The module is additionally tasked with verifying the consistency of the user inputs and completing the grid variablesThe purpose of the module is primarily to read in the files that contain the inputs, the initial condition data and the grid data that are provided by the user. The module is additionally tasked with verifying the consistency of the user inputs and completing the grid variables. This module also also allocating, initializing I/O, and deallocating the relevant variables on both cpus and gpus as well as setting up the time stepping, domain decomposition and I/O procedures. </p>
0 commit comments