Changes between Version 14 and Version 15 of MpiApps


Ignore:
Timestamp:
Mar 19, 2011, 2:18:52 PM (14 years ago)
Author:
carlgt1
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MpiApps

    v14 v15  
    55It is preferable to setup your MPI project using a BOINC "plan class" mechanism, using the "mt" (multithreaded) app plan.  This will enable the BOINC client to know that this job will use all available CPUs (and not try to run more than one workunit at a time), and will pass a command-line argument "--nthreads N" to the app (or wrapper) so that appropriate setup on the client can be done to run the number of processors available (i.e. -np 2 or 4 or 8 etc).
    66
    7 The "--nthreads N" argument will be the last argument passed to your wrapper (if using the wrapper) and your programs, so you can have a program that sets up your workunit at run-time to use "N" processors  (i.e. substitution in Fortran namelists NPROC etc).
     7If you use the flag <append_cmdline_args/> in your job.xml wrapper specification file, the "--nthreads N" argument will be the last argument passed to your wrapper and your programs, so you can have a program that sets up your workunit at run-time to use "N" processors  (i.e. substitution in Fortran namelists NPROC etc).
    88
    99----