Changes between Version 4 and Version 5 of MpiApps


Ignore:
Timestamp:
Feb 24, 2011, 12:10:25 PM (13 years ago)
Author:
carlgt1
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MpiApps

    v4 v5  
    2929Note that Windows Firewall will block these programs (as well as your MPI app) upon first launch.  This is path-dependent, so if you change these filenames it will "count" as a new program for Windows to block.  Hence it is probably more sensible to make a zip-file bundle of your programs, and track changes by the wrapper and job.xml file.  Otherwise every new application version you make, Windows Firewall will see it as a new potentially threatening program, and your users will have to allow this newly named program through. 
    3030
    31 Here is an example wrapper job.xml file for a Windows MPI app.  I assume you will zip the above files and put them in a subdirectory "bin" of your boinc project dir (using a small program called "movefiles"):
     31Here is an example wrapper job.xml file for a Windows MPI app.  I assume you will zip the above files and put them in a subdirectory "bin" of your boinc project dir (using a small program called "movefiles").  So the first task is "movefiles" which unzips the programs, then the next task is to run the smpd.exe MPI daemon/service locally, and then the final task is to run the MPI job.  You will probably have another post-processing task after that.
    3232
    3333{{{
     
    4141    <task>
    4242        <application>bin/smpd.exe</application>
     43        <daemon/>
    4344        <exec_dir>$PROJECT_DIR</exec_dir>
    4445        <stdin_filename></stdin_filename>
     
    5657}}}
    5758
     59Here's an example wrapper job.xml file for a Linux or Mac application with multiple non-MPI and MPI tasks:
     60
     61
     62{{{
     63
     64<job_desc>
     65    <task>
     66        <application>movefiles</application>
     67        <stdin_filename></stdin_filename>
     68        <stdout_filename>stdout.txt</stdout_filename>
     69        <command_line>wu_lin.zip</command_line>
     70        <setenv>LD_LIBRARY_PATH=$PROJECT_DIR:/usr/lib</setenv>
     71    </task>
     72    <task>
     73        <application>mpiexec</application>
     74        <exec_dir>$PROJECT_DIR/bin</exec_dir>
     75        <stdin_filename></stdin_filename>
     76        <stdout_filename>stdout.txt</stdout_filename>
     77        <command_line>-np 4 ./xmeshfem3D</command_line>
     78        <setenv>DYLD_LIBRARY_PATH=$PROJECT_DIR</setenv>
     79        <setenv>LD_LIBRARY_PATH=$PROJECT_DIR:/usr/lib</setenv>
     80    </task>
     81    <task>
     82        <application>movefiles</application>
     83        <stdin_filename></stdin_filename>
     84        <stdout_filename>stdout.txt</stdout_filename>
     85        <command_line>copymesh</command_line>
     86        <setenv>LD_LIBRARY_PATH=$PROJECT_DIR:/usr/lib</setenv>
     87    </task>
     88    <task>
     89        <application>mpiexec</application>
     90        <exec_dir>$PROJECT_DIR/bin</exec_dir>
     91        <stdin_filename></stdin_filename>
     92        <stdout_filename>stdout.txt</stdout_filename>
     93        <command_line>-np 4 ./xgenerate_databases</command_line>
     94        <setenv>LD_LIBRARY_PATH=$PROJECT_DIR:/usr/lib</setenv>
     95    </task>
     96    <task>
     97        <application>mpiexec</application>
     98        <exec_dir>$PROJECT_DIR/bin</exec_dir>
     99        <stdin_filename></stdin_filename>
     100        <stdout_filename>stdout.txt</stdout_filename>
     101        <command_line>-np 4 ./xspecfem3D</command_line>
     102        <setenv>LD_LIBRARY_PATH=$PROJECT_DIR:/usr/lib</setenv>
     103    </task>
     104</job_desc>
     105
     106
     107}}}