Changes between Version 10 and Version 11 of doc/app/machine/hlrnIII


Ignore:
Timestamp:
Jan 30, 2015 2:33:16 PM (10 years ago)
Author:
suehring
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/app/machine/hlrnIII

    v10 v11  
    106106      DATA_2D_XY_NETCDF, DATA_2D_XZ_NETCDF, DATA_2D_YZ_NETCDF, DATA_2D_XY_AV_NETCDF, DATA_2D_XZ_AV_NETCDF and DATA_2D_YZ_AV_NETCDF. You can copy these files to the
    107107      standard output directory and you can rename them, e.g. DATA_2D_XY_NETCDF to <job_name>_xy.nc.
     108
     109== How to use the '''allinea'''-debugger on hlogin and blogin ==
     110
     111Starting from Rev 1550,  PALM allows using of the '''allinea'''-debugger on hlogin and blogin within interactive sessions.
     112The following gives a brief instruction how to apply the '''allinea'''-debugger:
     113
     114   1. Add an additional block {{{"lccrayb parallel debug"}}} (please note that the "debug" is mandatory) in the '''mrun''' configuration file (equivalent for lccrayh) ({{{.mrun.config}}}) which has to contain a line:
     115{{{
     116      %allinea      true           lccrayb parallel debug
     117}}}
     118      Moreover, add the module ddt to the %modules flag as indicated by the following:
     119{{{
     120      %modules      ddt:fftw: ...  lccrayb parallel debug
     121}}}
     122
     123   2. Copy {{{.mrun.config}}} into directory {{{~/palm/current_version}}} on hlogin/blogin. Also copy parameter-file and other files required for the run to the respective subdirectories under {{{~/palm/current_version}}} (e.g. {{{JOBS/USERCODE...}}}).
     124
     125   3. Log in on hlogin/blogin (it is essential to use "{{{-X}}}" as ssh-option !!) and execute the following commands to launch an interactive session on the computing nodes (e.g. for a debug-run with 4 cores on one node):
     126{{{
     127      msub -I -X -l nodes=1:ppn=4 -l walltime=1000 -q mpp1testq
     128                  # starts a so-called interactive job
     129      module load ddt
     130
     131      mrun -d ....
     132           # usual mrun-call, options as required by user, but WITHOUT option -h and WITHOUT option -b
     133           # values given for -X and -T options must match the msub settings,
     134           # e.g. in this case "-X4 -T4"
     135}}}
     136   After short time, the '''allinea'''-window should open (if mpp1testq is filled with other jobs, you may have to wait for a longer time, alternatively you can also try to run on mpp2testq).
     137
     138   4. Within the '''allinea'''-window go to ''Application'' and select ''a.out'' (located within the current working-directory).   
     139
     140   5. Now you can "RUN" '''allinea'''. Enjoy debugging. 
     141
     142   6. After closing the '''allinea''' session, don't forget to leave the interactive job with "{{{exit}}}" command. If you did not use the entire requested {{{walltime}}} for debugging, you should cancel your interactive session on the computing nodes by the "{{{canceljob}}}"-command. 
     143
     144The HLRNIII provides a brief online documentation for '''alinea''' (see https://www.hlrn.de/home/view/System3/AllineaDDT for details).