Ignore:
Timestamp:
Sep 30, 2010, 2:47:17 PM (14 years ago)
Author:
garnier
Message:

tag geant4.9.4 beta 1 + modifs locales

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/examples/extended/parallel/MPI/README

    r807 r1337  
    1 $Id: README,v 1.2 2007/11/16 14:04:05 kmura Exp $
     1$Id: README,v 1.3 2010/05/18 06:09:09 kmura Exp $
    22==========================================================================
    33Geant4 MPI Interface
     
    1212a Geant4 UI library and a couple of parallelized examples.
    1313Using this interface, users applications can be parllelized with
    14 different MPI compliant libraries, such as LAM/MPI, MPICH2, OpenMPI,
     14different MPI compliant libraries, such as OpenMPI, LAM/MPI, MPICH2,
    1515and so on.
    1616
     
    2525* MPI implementation
    2626
    27 - LAM/MPI (7.1.3)
     27- Open MPI (1.4.2)
     28  http://www.open-mpi.org/
     29
     30- LAM/MPI (7.1.3) (development is terminated. maintenance only)
    2831  http://www.lam-mpi.org/
    2932
    30 - MPICH2 (1.0.6p1)
     33- MPICH2 (1.2.1p1)
    3134  http://www.mcs.anl.gov/research/projects/mpich2/
    32 
    33 - Open MPI (1.2.4)
    34   http://www.open-mpi.org/
    35 
    3635
    3736* Optional
     
    4241----------------
    4342G4MPI UI library is provided in the "mpi_interface" directory.
    44 Start with building the G4MPI UI library according to the instruction 
     43Start with building the G4MPI UI library according to the instruction
    4544in the directory.
    4645
     
    6059  // MPI session (G4MPIsession) instead of G4UIterminal
    6160  G4MPIsession* session= g4MPI-> GetMPIsession();
    62 
    63   // LAM users can use G4tcsh.
    64   G4String prompt= "G4MPI";
    65   G4UItcsh* tcsh= new G4UItcsh(prompt);
    66   session-> SetShell(tcsh);
    6761
    6862  // user application setting
     
    8680For other users (Open MPI/MPICH2), plese use G4csh (default).
    8781
     82In case of OpenMPI, LD_LIBRARY_PATH for OpenMPI runtime libraries
     83should be set at run time. Alternatively, you can add this path
     84to the dynamic linker configuration using `ldconfig`.
     85(needs sys-admin authorization)
     86
    8887
    8988How to use:
     
    93921. Make hosts/cluster configuration of your MPI environment.
    9493
    95 2. Launch MPI runtime environment, typically executing 
     942. Launch MPI runtime environment, typically executing
    9695   lamboot (LAM) / mpdboot (MPICH2).
    9796
     
    119118   execute *        Execute a macro file. (=/control/execute)
    120119   beamOn *         Start a parallel run w/ thread.
    121    .beamOn *        Start a parallel run w/o thread. (=/run/beamOn)
     120   .beamOn *        Start a parallel run w/o thread.
    122121   masterWeight *   Set weight for master node.
     122   wait *           Wait until beamOn-s on all nodes are done. (batch mode only)
    123123   showSeeds *      Show seeds of MPI nodes.
    124124   setMasterSeed *  Set a master seed for the seed generator.
     
    126126
    127127* Notes:
    128 While "/run/beamOn" is executed in foreground, the "/mpi/beamOn"
    129 command invokes beam-on in background, so you can input UI commands
    130 even while event processing.
     128While "/run/beamOn" and "/mpi/beamOn" commands invoke beam-on in background,
     129so you can input UI commands even while event processing.
    131130
    132 The original "/control/execute" and "/run/beamOn" are overwritten 
    133 with "/mpi/execute" and "/mpi/.beamOn" commands, customized for
    134 the MPI interface.
     131The original "/control/execute" and "/run/beamOn" are overwritten
     132with "/mpi/execute" and "/mpi/beamOn" commands respectively,
     133customized for the MPI interface.
    135134
    136135
     
    142141for running examples:
    143142
    144 - G4LEVELGAMMADATA : directory path for the data of 
     143- G4LEVELGAMMADATA : directory path for the data of
    145144                     "low energy electromagnetic processes".
    146145
    147 For running ROOT applications, 
     146For running ROOT applications,
    148147
    149148- ROOTSYS         : root path of the ROOT package
     
    174173  * treat multiple outputs properly:
    175174    each slave node generate a ROOT file, whose file name should
    176     be different from each other. 
     175    be different from each other.
    177176
Note: See TracChangeset for help on using the changeset viewer.