Difference between revisions of "DDT"

From UFRC
Jump to navigation Jump to search
m
Line 36: Line 36:
 
# On the main screen, select 'ufrc-ddt' from the Remote Launch pulldown menu
 
# On the main screen, select 'ufrc-ddt' from the Remote Launch pulldown menu
 
# From another window (PuTTY/Terminal/etc.), log into hpg2.rc.ufl.edu as you normally would.  
 
# From another window (PuTTY/Terminal/etc.), log into hpg2.rc.ufl.edu as you normally would.  
# Modify the following command appropriately and use it to schedule your job: <br> <pre> cd /ufrc/<group>/<username>/example-directory <br> sbatch example-job </pre>
+
# Modify the following command appropriately and use it to schedule your job:
# It may take up to 90 seconds for your job to start; once it does, you will get a connection request from ddt running your job. Accept the request and you should be ready to start debugging your application.  
+
 
 +
<source lang=bash>cd /ufrc/<group>/<username>/example-directory  
 +
sbatch example-job  
 +
</source>
 +
 
 +
 
 +
It may take up to 90 seconds for your job to start; once it does, you will get a connection request from ddt running your job. Accept the request and you should be ready to start debugging your application.  
  
 
==Example Job Script==
 
==Example Job Script==
Line 47: Line 53:
 
#SBATCH --mail-type=FAIL,END  #What emails you want
 
#SBATCH --mail-type=FAIL,END  #What emails you want
 
#SBATCH --mail-user=<username>@ufl.edu  #Where
 
#SBATCH --mail-user=<username>@ufl.edu  #Where
#SBATCH --nodes=1    #Request a single processor
+
#SBATCH --nodes=1    #No. of processors requested
#SBATCH --ntasks=1    #Tottal no. of  processors
+
#SBATCH --ntasks=1    #Total no. of  processors
 
#SBATCH --cpus-per-task=1    #No. CPUs per task
 
#SBATCH --cpus-per-task=1    #No. CPUs per task
 
#SBATCH --mem-per-cpu=2000mb  #Per processor memory request
 
#SBATCH --mem-per-cpu=2000mb  #Per processor memory request
Line 54: Line 60:
 
#SBATCH --partition=hpg2-dev
 
#SBATCH --partition=hpg2-dev
  
module load intel/2016.0.109 openmpi/1.10.2 petsc/3.7.0 metis/5.1.0
+
module load <modules_required_for_your_application>
 
module load ddt/6.0
 
module load ddt/6.0
 
cd $SLURM_SUBMIT_DIR
 
which mpiexec
 
printenv
 
hostname
 
  
 
#mpiexec  ./main > resid.dat
 
#mpiexec  ./main > resid.dat

Revision as of 19:50, 5 August 2016

Allinea DDT is a graphical source code debugging analysis tool with the power that you need to take control of software bugs whenever they occur, making it simpler to solve even the most complex multi-threaded or multi-process software problems. Includes Allinea MAP for performance analysis.

This module enables the use of the TotalView software.

Using DDT

First, download the Allinea Forge remote client and install it on your computer:

Create a batch submissions script for the application you want to debug as though you were going to submit it to the queue. Be sure that you add the following sequence before the mpiexec command in your script:

  • ddt --connect --degbug --log ddt-debug.log \

If you need more help creating the script, please use the example job script further down the page. Then, proceed with the following steps:

  1. Start the remote client on your personal device
  2. In the "Remote Launch" pulldown menu, select "Configure..."
  3. Click "Add" and fill in the following information:
    Connection Name: ufrc-ddt
    Host Name: <username>@hpg2.rc.ufl.edu <username>@i21b-s4.ufhpc
    Remote Installation Directory: /apps/allinea/forge/6.0
    Remote Script: <leave blank>
  4. Click "OK"
  5. Click "Close"
  6. On the main screen, select 'ufrc-ddt' from the Remote Launch pulldown menu
  7. From another window (PuTTY/Terminal/etc.), log into hpg2.rc.ufl.edu as you normally would.
  8. Modify the following command appropriately and use it to schedule your job:
cd /ufrc/<group>/<username>/example-directory 
sbatch example-job


It may take up to 90 seconds for your job to start; once it does, you will get a connection request from ddt running your job. Accept the request and you should be ready to start debugging your application.

Example Job Script

#!/bin/bash
#SBATCH --job-name=example-job  #A name for your job
#SBATCH --output my_job-%j.out #Output File
#SBATCH --error my_job-%j.err  #Error File
#SBATCH --mail-type=FAIL,END  #What emails you want
#SBATCH --mail-user=<username>@ufl.edu   #Where
#SBATCH --nodes=1     #No. of processors requested
#SBATCH --ntasks=1    #Total no. of  processors
#SBATCH --cpus-per-task=1    #No. CPUs per task
#SBATCH --mem-per-cpu=2000mb   #Per processor memory request
#SBATCH --time=12:00:00       #Walltime in hh:mm:ss or d-hh:mm:ss
#SBATCH --partition=hpg2-dev

module load <modules_required_for_your_application>
module load ddt/6.0

#mpiexec  ./main > resid.dat
ddt --connect --degbug --log ddt-debug.log \ 
   mpiexec  ./main > resid.dat

Required Modules

Serial

  • {{#lowercase:DDT}}

System Variables

  • HPC_{{#uppercase:DDT}}_DIR
  • HPC_{{#uppercase:DDT}}_BIN