Information about software packages installed on the ICHEC systems.
Fionn: 4.1 / 4.1.1 / 4.2
Two Allinea tools are provided on Fionn: DDT and MAP. DDT (The Distributed Debugging Tool) is a comprehensive graphical debugger for scalar, multi-threaded and large-scale parallel applications that are written in C, C++ and Fortran.
While MAP is a profiling tool for analysing MPI and multi-threaded applications that provides information on both serial and parallel parts of your code.
As DDT and MAP are both graphic tools, you'll need both a X11 server running on you own machine, and X11 forwarding via a ssh connection. If you are working on a Unix-like machine, Linux, Mac OS X etc., the X11 server should be present by default. If you are working on a MS Windows system, you will probably need to install one. Xming is a common choice. Finally, X11 forwarding over your connection should be enabled by simply adding the - X option to your ssh command line:
To load both MAP and DDT type:
Dealing with batch Submission
The first time you run DDT or MAP, a few extra steps are required in order to ensure it works with the batch system. These settings will be remembered for future sessions. In the same way as other jobs, your debugging job has to be launched through the batch manager via a PBS script. However as this script's purpose is only to explain to DDT and MAP the way in which it will have to submit debug and profiling jobs, it can be quite simple. Moreover, you should be able to reuse the same script for all your debugging sessions, as the script will be based on some special tags that DDT and MAP will interpret and adapt to refer to its current needs. The most useful tags are shown in this table. These tags will permit us to write template scripts which can be adapted to most of your actual jobs. An example script is included in the templates subdirectory of the package, note that this has the '.qtf' extension. This is the one we shall use in this example. Now, in order to configure DDT and MAP start either program.
Your DDT and MAP environments should now be ready to permit you to run your first debugging or profiling job.
When you are ready to start, type:
- At DDT start, click on the "Run and Debug a Program" button. Here, select your binary to debug and adjust the number of nodes. You can now simply click on the Submit button, and wait for your job to be launched by the batch scheduler. During this phase, the state of the batch queues is updated continuously with the command you provided in the Job Submission dialogue. You can also cancel your job if needed with the appropriate button.
- After a brief wait, if everything went well, your job should start and then you should get a new window where you can your debugging session.
When considering the walltime necessary for your job to run, you must consider that fact that the MAP needs to analyse your code at the end of the run. This can take up to 10 or 20 minutes on top of the normal program runtime and this needs to be allowed for. MAP will also increase the run time by about 5%, so take this into account too. Unlike DDT the analysis is done after the program has completed and thus you can spend as long as you want analysing the profile without worrying about your budget! When you are ready to start, type:
- At MAP start, click on the "Profile" button. Here, select your binary to debug, adjust the number of nodes to use and number of MPI process per node to launch. You can now simply click on the Submit button, and wait for your job to be launched by the batch scheduler. During this phase, the state of the batch queues is updated continuously with the command you provided in the Job Submission dialogue. You can also cancel your job if needed with the appropriate button.
- After a brief wait, if everything went well, your job should start and then you should get a window where MAP prints the output of your program.
- MAP will now run your program and then analyse it. This can take a little time. Worth noting is that you can come back later by using the 'Load Profile Data File' on the main screen after start-up.
For more information see the Allinea website.