Changes between Version 3 and Version 4 of Tutorials/RunTestProblem

Show
Ignore:
Timestamp:
09/05/08 12:42:40 (5 years ago)
Author:
sskory
Comment:

Eh, a few fixes.

Legend:

Unmodified
Added
Removed
Modified
  • Tutorials/RunTestProblem

    v3 v4  
    11= How to run an Enzo test problem = 
    22 
    3 Enzo comes with a set of pre-written parameter files which are used to test Enzo. This is useful when migrating to a new machine, with different compilers, or when new versions of compilers and libraries are introduced. Also, all the test problems should run to completion, which is generally not a guarantee! 
     3Enzo comes with a set of pre-written parameter files which are used to test Enzo. This is useful when migrating to a new machine with different compilers, or when new versions of compilers and libraries are introduced. Also, all the test problems should run to completion, which is generally not a guarantee! 
    44 
    55At the top of each enzo parameter file is a line like {{{ProblemType = 23}}}, which tells enzo the type of problem. You can see how this affects enzo by inspecting {{{src/enzo/InitializeNew.C}}}. In this case, you'll find this is used: 
     
    3333== !ShockPool3D test == 
    3434 
    35 Here's what the parameter file looks like for the !ShockPool3D.enzo test problem: 
    36  
    37 {{{ 
    38 # 
    39 # AMR PROBLEM DEFINITION FILE: 3D Shock Propogation test 
    40 # 
    41 #  define problem 
    42 # 
    43 ProblemType            = 3        // Shock Pool 
    44 TopGridRank            = 3 
    45 TopGridDimensions      = 50 50 50 
    46 RightFaceBoundaryCondition = 1 1 1  // set right faces to outflow 
    47 HydroMethod            = 0 
    48 # 
    49 ShockPoolAngle          = 30.0    // angle relative to x-axis (in degrees) 
    50 ShockPoolMachNumber     = 2.0  
    51 #ShockPoolSubgridLeft    = 0.38   // start of subgrid 
    52 #ShockPoolSubgridRight   = 0.62   // end of subgrid 
    53 # 
    54 #  set I/O and stop/start parameters 
    55 # 
    56 StopTime               = 0.4 
    57 dtDataDump             = 0.1 
    58 # 
    59 #  set Hydro parameters 
    60 # 
    61 Gamma                  = 1.4 
    62 CourantSafetyNumber    = 0.5 
    63 PPMDiffusionParameter  = 0       // diffusion off 
    64 PPMFlatteningParameter = 0       // flattening on 
    65 PPMSteepeningParameter = 0       // steepening on 
    66 # 
    67 #  set grid refinement parameters 
    68 # 
    69 StaticHierarchy           = 0    // static hierarchy 
    70 RefineBy                  = 4    // refinement factor 
    71 MaximumRefinementLevel    = 1 
    72 CellFlaggingMethod        = 1 
    73 MinimumEfficiency         = 0.5 
    74 # 
    75 #  set some misc global parameters 
    76 # 
    77 tiny_number            = 1.0e-6  // fixes velocity slope problem 
    78 }}} 
    79  
    80 Note the dtDataDump line, it may be commented out in your copy of enzo. If you keep it commented out, there will be no output saved to disk. 
    81  
    82 Once you've [wiki:/UserGuide/BuildingEnzo compiled enzo], make a directory to run the test problem in. Copy {{{enzo.exe}}} and {{{ShockPool3D.enzo}}} into that directory. On [http://www.nics.tennessee.edu/computing-resources/kraken Kraken], to run in an interactive queue, type: 
     35The !ShockPool3D is a purely hydrodynamical simulation testing a shock with non-periodic boundary conditions. Once you've [wiki:UserGuide/BuildingEnzo compiled enzo], make a directory to run the test problem in. Copy {{{enzo.exe}}} and {{{ShockPool3D.enzo}}} into that directory. On [http://www.nics.tennessee.edu/computing-resources/kraken Kraken], to run in an interactive queue, type: 
    8336 
    8437{{{ 
     
    9245}}} 
    9346 
    94 I am running the test problem on 16 processors, I've turned on the debug flag ({{{-d}}}), and I'm piping the standard output to a file ({{{01.log}}}). This took about 1:20 to run on Kraken. 
     47I am running the test problem on 16 processors, I've turned on the debug flag ({{{-d}}}), and I'm piping the standard output to a file ({{{01.log}}}). This took about an hour and twenty minutes to run on Kraken. 
    9548 
    9649If you want to keep track of the progress of the run, in another terminal type: