Changes between Version 8 and Version 9 of u/NewUsers


Ignore:
Timestamp:
08/09/11 15:05:48 (13 years ago)
Author:
Erica Kaminski
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • u/NewUsers

    v8 v9  
    1212== Effectively Implementing AMR ==
    1313
    14 There are some additional controls for AMR other than setting the number of levels in global.data. One can also make use of the namelist variable in physics.data named "refineVariableFactor". If this is not currently in your physics.data file, you can add it under the line for InterpOpts. The input for this variable represents the different q array elements.
     14There are some additional controls for AMR other than setting the number of levels in global.data. One can also make use of the namelist variable in physics.data named "refineVariableFactor". If this is not currently in your physics.data file, you can add it under the line for !InterpOpts. The input for this variable represents the different q array elements (rho, px, py, pz, E, Bx, By, Bz, tracer1, tracer2, ..., tracerM).
    1515
    1616Example:
     
    1818refineVariableFactor =  1.d-21,0d0,0d0,0d0,0d0,0d0,0d0,0d0,0d0,0d0,0d0,0d0,0d0
    1919
    20 The input here controls the variable to which refinement is triggered. By setting a slot = 0 means that refinement will not be triggered for this variable. The smaller the number, the less the refinement.
     20The input here controls the variable to which refinement is triggered. By setting a slot = 0 means that refinement will not be triggered for this variable. The smaller the number, the less the refinement. The max value for input to this array is 1, and if this line is not included in your physics.data, all the vector components will be initialized to 1.
    2121
    22 refineVariableFactor is defined in module_control.f90, in the subroutine SetErrFlag.
     22refineVariableFactor is defined in module_control.f90, in the subroutine !SetErrFlag.
    2323
    24 Additionally, one can modify the SetErrFlags subroutine in problem.f90 to indicate precise ''regions'' of refinement.
     24Additionally, one can modify the !SetErrFlags subroutine in problem.f90 to indicate precise ''regions'' of refinement.
    2525
    2626Example: