Changes between Version 2 and Version 3 of Tutorials/RunTestProblem
- Timestamp:
- 09/05/08 12:36:35 (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Tutorials/RunTestProblem
v2 v3 29 29 }}} 30 30 31 The files that end in {{{.enzo}}} are the enzo parameter files, and {{{.inits}}} are inits parameter files. inits files are only used for cosmology simulations, and you can see an example of how to run that [wiki:Tutorials/RunCosmologySimulation here]. Let's try one of the non-cosmology test problems.31 The files that end in {{{.enzo}}} are the enzo parameter files, and {{{.inits}}} are inits parameter files. inits files are only used for cosmology simulations, and you can see an example of how to run that [wiki:Tutorials/RunCosmologySimulation here]. Let's try a couple of the non-cosmology test problems. 32 32 33 33 == !ShockPool3D test == … … 89 89 90 90 {{{ 91 aprun -n 16 ./enzo.exe -d ShockPool3D.enzo > 01. log91 aprun -n 16 ./enzo.exe -d ShockPool3D.enzo > 01.out 92 92 }}} 93 93 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}}}). If you want to keep track of the progress of the run, in another terminal type: 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. 95 96 If you want to keep track of the progress of the run, in another terminal type: 95 97 96 98 {{{ 97 tail -f 01. log98 tail -f 01. log| grep dt99 tail -f 01.out 100 tail -f 01.out | grep dt 99 101 }}} 100 102 101 I find that the first command above gives too verbose output. The second one will show what's more interesting, like the current cycle number and how deep in the AMR hierarchy the run is going (look for {{{Level[n]}}} where {{{n}}} is the zero-based AMR level number). 103 I find that the first command above gives too verbose output. The second one will show what's more interesting, like the current cycle number and how deep in the AMR hierarchy the run is going (look for {{{Level[n]}}} where {{{n}}} is the zero-based AMR level number). This command is especially useful for batch queue jobs where the standard out always goes to a file. 102 104 103 == !GravityTest ===105 == !GravityTest test == 104 106 105 The !GravityTest.enzo problem only tests setting up a gravity field of 5000 particles. Similar to above, a successful run looks like this:107 The !GravityTest.enzo problem only tests setting up the gravity field of 5000 particles. A successful run looks like this and should take less than a second, even on one processor: 106 108 107 109 {{{ … … 115 117 }}} 116 118 117 I've attached a file showing my output from this test problem on Kraken.119 I've attached a file below showing my output from this test problem on Kraken. You may wish to compare your results.
