Changes between Version 7 and Version 8 of Archer/DDT


Ignore:
Timestamp:
01/04/15 11:26:57 (5 years ago)
Author:
grenville
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Archer/DDT

    v7 v8  
    11DDT is a powerful debugging tool which allows you to step interactively through code, apply breakpoints, tracepoints, examine variables, debug memory, and more... 
    22 
    3 Documentation for how to use the tool is available, but how to get it running in the UM infrastructure is less obvious (though not difficult). The instructions given here refer to a UM 8.2 set up - there may be minor changes needed for other versions of the model, but they shouldn't amount to much (contact the CMS if you need further assistance). 
     3Documentation for how to use the tool is available (try http://content.allinea.com/downloads/userguide-forge.pdf), but how to get it running in the UM infrastructure is less obvious (though not difficult). The instructions given here refer to a UM 8.2 set up - there may be minor changes needed for other versions of the model, but they shouldn't amount to much (contact the CMS if you need further assistance). 
    44 
    55You will need some familiarity with where the UM puts its various files and scripts. In particular, you will need a umui_runs directory for the job you wish to debug on ARCHER and you will need to modify the qsatmos script, usually found in $DATAW/bin. 
     
    5454At this stage you are on a job-launcher node (mom3 in this case) and can run aprun directly, ie launch a parallel job directly rather than through the scheduler. 
    5555 
    56 '''5.''' cd to the umui_runs directory for your failing job - the directory created in step '''2''', load the allinea module and run the submit script interactively 
     56'''5.''' cd to the umui_runs directory for the failing job (xlehy in this example), ie the directory created in step '''2''', load the allinea module and run the submit script interactively 
    5757 
    5858{{{ 
     59grenvill@mom3 cd ~/umui_runs/xlehy-091105123 
    5960grenvill@mom3 module load allinea 
    6061grenvill@mom3 ./umuisubmit_run 
     
    6566[[Image(ddt.png,800px,align=center)]] 
    6667 
    67 It is probably best to ensure that the resources needed for job you wish to debug match those requested in the interactive session - in this example we requested 4 interactive nodes and the job was configured to run on 4x12 MPI tasks each with 2 OMP threads for a total of 4 nodes. 
     68It is probably best to ensure that the resources needed for the job you wish to debug match those requested in the interactive session - in this example I requested 4 interactive nodes and the job was configured to run on 4x12 MPI tasks each with 2 OMP threads for a total of 4 nodes.