Template:RT3D Code Reaction Workflow: Difference between revisions

From XMS Wiki
Jump to navigationJump to search
No edit summary
No edit summary
Line 12: Line 12:
|-
|-
|
|
# In the first method, all reaction parameter values are explicitly assigned within the reaction module prior to compilation. This is not an efficient method since it requires recompilation of the reaction routine whenever a reaction parameter value is modified. However, this method is recommended for testing a new reaction module with the BATCHRXN utility.
:# In the first method, all reaction parameter values are explicitly assigned within the reaction module prior to compilation. This is not an efficient method since it requires recompilation of the reaction routine whenever a reaction parameter value is modified. However, this method is recommended for testing a new reaction module with the BATCHRXN utility.
# In the second method, all of the reaction parameter values are spatially constant but are assigned/modified externally, as input data, via the RCT file (to run RT3D) or batch.in file (to run BATCHRXN).
:# In the second method, all of the reaction parameter values are spatially constant but are assigned/modified externally, as input data, via the RCT file (to run RT3D) or batch.in file (to run BATCHRXN).
# In the third method, some or all of the reaction parameters are treated as spatially variable (i.e., a different value may be assigned to each cell). The parameter values should be externally assigned/modified as input data via the RCT file. This option should be used with caution because it may require significant computer resources, both execution time and memory.
:# In the third method, some or all of the reaction parameters are treated as spatially variable (i.e., a different value may be assigned to each cell). The parameter values should be externally assigned/modified as input data via the RCT file. This option should be used with caution because it may require significant computer resources, both execution time and memory.


|}
|}
Line 22: Line 22:
|-
|-
|
|
 
:#
|}
|}
{| class="mw-collapsible mw-collapsed" style="width:100%; border:1px solid #CDB7B5; margin-bottom:0.4em;"
{| class="mw-collapsible mw-collapsed" style="width:100%; border:1px solid #CDB7B5; margin-bottom:0.4em;"

Revision as of 19:02, 17 October 2016

1. Select package coding approach.
  1. Dynamically linked library (DLL) DLL option.
  2. Linked subroutine option
2. Select method for coding a new user-defined package.
  1. In the first method, all reaction parameter values are explicitly assigned within the reaction module prior to compilation. This is not an efficient method since it requires recompilation of the reaction routine whenever a reaction parameter value is modified. However, this method is recommended for testing a new reaction module with the BATCHRXN utility.
  2. In the second method, all of the reaction parameter values are spatially constant but are assigned/modified externally, as input data, via the RCT file (to run RT3D) or batch.in file (to run BATCHRXN).
  3. In the third method, some or all of the reaction parameters are treated as spatially variable (i.e., a different value may be assigned to each cell). The parameter values should be externally assigned/modified as input data via the RCT file. This option should be used with caution because it may require significant computer resources, both execution time and memory.
3. Edit source code of the reaction module.
4. Compile source code.
Retrieved from "https://www.xmswiki.com/index.php?title=Template:RT3D_Code_Reaction_Workflow&oldid=113760"