| 252 | | The instructions below are machine-agnostic--they are good for any cluster, as long as you are using a valid AstroBEAR repository and your environment has been set up properly (see above). |
| 253 | | |
| 254 | | [[CollapsibleStart(Setting Up A Run Directory)]] |
| 255 | | |
| 256 | | These directions assume that you have already compiled a problem module. If you have not done this yet, see "Setting up and Compiling A Problem" above. |
| 257 | | |
| 258 | | |
| 259 | | 1. Move to your system's scratch directory. Most well-managed clusters have a directory like this; it's just a place on a high-volume drive for people to run jobs that produce large amounts of data. The scratch directories for our more heavily-used clusters are listed below: |
| 260 | | {{{ |
| 261 | | grass: /grassdata/<username> |
| 262 | | bluehive: /scratch/<username> |
| 263 | | bluegene: /scratch/<username> |
| 264 | | itasca: /scratch1/<username> |
| 265 | | }}} |
| 266 | | |
| 267 | | 2. Create a run directory {{{run_dir}}}. Then, create a subdirectory {{{out}}} within {{{run_dir}}}: |
| 268 | | {{{ |
| 269 | | mkdir run_dir |
| 270 | | mkdir run_dir/out |
| 271 | | }}} |
| 272 | | The {{{out/}}} directory is where AstroBEAR will store its output files. |
| 273 | | |
| 274 | | |
| 275 | | 3. If you are running a problem that uses a source-term lookup table, then copy the {{{TABLES}}} directory from {{{source}}} into your problem directory: |
| 276 | | {{{ |
| 277 | | cp -r <astrobear_path>/source/TABLES run_dir |
| 278 | | }}} |
| 279 | | |
| 280 | | 4. Put the problem's data files in {{{run_dir}}}. If you are running a sample problem that came with AstroBEAR, such as {{{FieldLoopAdvection}}}, then the data files can be found in the problem directory inside {{{modules}}}. |
| 281 | | |
| 282 | | 5. Copy the {{{astrobear}}} file from your AstroBEAR directory into your run directory: |
| 283 | | {{{ |
| 284 | | cp astrobear <rundir_path>/run_dir |
| 285 | | }}} |
| 286 | | AstroBEAR is not intended to be run without MPI, so be sure to use the {{{mpiexec}}} command even if you are running a single-processor job. On the plus side, you no longer have to change your data files every time you want to change the number of processors, since AstroBEAR handles decomposition automatically. |
| 287 | | [[CollapsibleEnd]] |
| 288 | | |
| 289 | | [[BR]] |
| 290 | | Once you have successfully built AstroBEAR and set up a problem directory, you can try [RunningAstroBear running the code]. |
