Changes between Version 16 and Version 17 of AnugaParallel


Ignore:
Timestamp:
Jan 11, 2012, 7:35:30 AM (12 years ago)
Author:
steve
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • AnugaParallel

    v16 v17  
    88
    99
    10 Make sure you have setup your PYTHONPATH to point to location of the source directory
     10Make sure you have setup your PYTHONPATH to point to the anuga source directory
    1111
    1212For instance I have the following line in my .bashrc file
     
    2020python test_all.py
    2121}}}
    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).
     22from 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).
    2323
    2424
    2525== anuga_parallel ==
    2626
    27 Now to get anuga_parallel to work, we need to install some other packages.
     27Now 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}}}.
    2828
    2929=== MPI ===
     
    3737 
    3838
    39 Make sure mpi works. You should be able to run a program in parallel. Try something as simple as
     39Make sure mpi works. You should be able to run a program in parallel. Something as simple as
    4040
    4141{{{
     
    5454http://code.google.com/p/pypar/
    5555
    56 (There is an old version on sourceforge, don't use that)
     56(There is an old version on sourceforge, do not use that)
    5757
    5858Install pypar following the instructions in the download. You should be able use the standard command
     
    8080
    8181
    82 Make sure the pypar examples work
     82Also make sure the pypar examples work
    8383
    8484
     
    111111}}}
    112112
     113By the way, it is sometimes useful to fire up a new console to see if these
     114installations work in a clean console.
    113115
    114116=== PYMETIS ===
     
    135137=== ANUGA_PARALLEL  ===
    136138
    137 Should now be ready to run some parallel anuga code. Go back to the anuga_parallel directory and run test_all.py
     139You should now be ready to run some parallel anuga code. Go back to the anuga_parallel directory and run test_all.py
    138140
    139141Hopefully that all works.
     
    190192Suppose your parallel code produced 3 sww files, domain_P3_0.sww domain_P3_1.sww and domain_P3_2.sww
    191193
    192 The base name would be "domain" and the number of processors would be 3. To stitch these 3 files together either run the sww_merge.py as a script with the command
    193 
    194 {{{
    195 python /dir/to/anuga/utilities/sww_merge.py -f domain -np 3
    196 }}}
    197 
    198 or add the following command at the end of your simulation script
     194The 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{{{
     197python /home/username/anuga_core/source/anuga/utilities/sww_merge.py -f domain -np 3
     198}}}
     199
     200or you can add the following command at the end of your simulation script
    199201
    200202{{{
    201203domain.sww_merge()
    202204}}}
     205
     206if you want to keep the individual parallel sww files or
     207
     208{{{
     209domain.sww_merge(delete_old=True)
     210}}}
     211
     212if you are happy for the individual sww files to be deleted after the merge operation.