Changes between Version 16 and Version 17 of AnugaParallel
- Timestamp:
- Jan 11, 2012, 7:35:30 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
AnugaParallel
v16 v17 8 8 9 9 10 Make sure you have setup your PYTHONPATH to point to location of thesource directory10 Make sure you have setup your PYTHONPATH to point to the anuga source directory 11 11 12 12 For instance I have the following line in my .bashrc file … … 20 20 python test_all.py 21 21 }}} 22 from the anuga_core directory and have your installation pass all the unit tests (well nearly all, as this is the development version and there are sometimes a few unit tests that fail).22 from the anuga_core directory and have your installation pass all the unit tests (well nearly all, as this is the development version and there are sometimes a few minor unit tests that fail). 23 23 24 24 25 25 == anuga_parallel == 26 26 27 Now to get anuga_parallel to work, we need to install some other packages .27 Now to get anuga_parallel to work, we need to install some other packages first, in particular {{{MPI}}} for the parallel message passing and {{{pypar}}} a simple python wrapper of {{{MPI}}}. 28 28 29 29 === MPI === … … 37 37 38 38 39 Make sure mpi works. You should be able to run a program in parallel. Try something as simple as39 Make sure mpi works. You should be able to run a program in parallel. Something as simple as 40 40 41 41 {{{ … … 54 54 http://code.google.com/p/pypar/ 55 55 56 (There is an old version on sourceforge, do n't use that)56 (There is an old version on sourceforge, do not use that) 57 57 58 58 Install pypar following the instructions in the download. You should be able use the standard command … … 80 80 81 81 82 Make sure the pypar examples work82 Also make sure the pypar examples work 83 83 84 84 … … 111 111 }}} 112 112 113 By the way, it is sometimes useful to fire up a new console to see if these 114 installations work in a clean console. 113 115 114 116 === PYMETIS === … … 135 137 === ANUGA_PARALLEL === 136 138 137 Should now be ready to run some parallel anuga code. Go back to the anuga_parallel directory and run test_all.py139 You should now be ready to run some parallel anuga code. Go back to the anuga_parallel directory and run test_all.py 138 140 139 141 Hopefully that all works. … … 190 192 Suppose your parallel code produced 3 sww files, domain_P3_0.sww domain_P3_1.sww and domain_P3_2.sww 191 193 192 The base name would be "domain" and the number of processors would be 3. To stitch these 3 files together either run thesww_merge.py as a script with the command193 194 {{{ 195 python / dir/to/anuga/utilities/sww_merge.py -f domain -np 3196 }}} 197 198 or add the following command at the end of your simulation script194 The base name would be "domain" and the number of processors would be 3. To stitch these 3 files together either run sww_merge.py as a script with the command 195 196 {{{ 197 python /home/username/anuga_core/source/anuga/utilities/sww_merge.py -f domain -np 3 198 }}} 199 200 or you can add the following command at the end of your simulation script 199 201 200 202 {{{ 201 203 domain.sww_merge() 202 204 }}} 205 206 if you want to keep the individual parallel sww files or 207 208 {{{ 209 domain.sww_merge(delete_old=True) 210 }}} 211 212 if you are happy for the individual sww files to be deleted after the merge operation.
