Allinea: DDT - Revision history

K mouza: /* Note */

2015-03-30T16:20:13Z

Note

K mouza: /* Note */

2015-03-30T15:52:04Z

Note

K mouza: /* Type of application */

2015-03-30T15:51:34Z

Type of application

K mouza: /* Note */

2015-03-30T15:49:26Z

Note

K mouza: /* Type of application */

2015-03-30T15:49:08Z

Type of application

K mouza: /* Type of application */

2015-03-30T15:48:24Z

Type of application

K mouza at 10:54, 30 March 2015

2015-03-30T10:54:15Z

K mouza: /* Arrays */

2014-10-29T15:26:45Z

Arrays

K mouza: /* Arrays */

2014-10-29T15:21:54Z

Arrays

K mouza: /* Arrays */

2014-10-29T15:21:16Z

Arrays

@@ Line 7: / Line 7: @@
 #*If the application needs command line arguments or stdin input, these can be provided in the "Arguments" and "stdin file" fields, respectively.
-==== Note ====
+==== Notes ====
-'''For all the following application types, make sure to load the appropriate modules in the same terminal as the DDT will be run, or have the modules be loaded in the <tt>.bashrc</tt> file. Otherwise, libraries will be missing.'''
+*'''For all the following application types, make sure to load the appropriate modules in the same terminal as the DDT will be run, or have the modules be loaded in the <tt>.bashrc</tt> file. Otherwise, libraries will be missing.'''
 === MPI applications ===

@@ Line 7: / Line 7: @@
 #*If the application needs command line arguments or stdin input, these can be provided in the "Arguments" and "stdin file" fields, respectively.
-=== Note ===
+==== Note ====
 '''For all the following application types, make sure to load the appropriate modules in the same terminal as the DDT will be run, or have the modules be loaded in the <tt>.bashrc</tt> file. Otherwise, libraries will be missing.'''

@@ Line 29: / Line 29: @@
 *'''Intel MPI 4.1.3:''' Load the <tt>intel/compiler/64/14.0/2013_sp1.3.174</tt> and <tt>intel-mpi/64/4.1.3/049</tt> modules.
 *'''MPICH 3.1 compiled with GCC:''' Load the <tt>mpich/ge/gcc/64/3.1</tt> module.
 == Debug the application ==

@@ Line 9: / Line 9: @@
 === Note ===
-For all the following application types, make sure to load the appropriate modules in the same terminal as the DDT will be run, or have the modules be loaded in the <tt>.bashrc</tt> file. Otherwise, libraries will be missing.
+'''For all the following application types, make sure to load the appropriate modules in the same terminal as the DDT will be run, or have the modules be loaded in the <tt>.bashrc</tt> file. Otherwise, libraries will be missing.'''
 === MPI applications ===

@@ Line 7: / Line 7: @@
 #*If the application needs command line arguments or stdin input, these can be provided in the "Arguments" and "stdin file" fields, respectively.
-'''Note:''' For all the following application types, make sure to load the appropriate modules in the same terminal as the DDT will be run, or have the modules be loaded in the <tt>.bashrc</tt> file. Otherwise, libraries will be missing.
+=== Note ===
 === MPI applications ===

@@ Line 6: / Line 6: @@
 #Fill the "Äpplication" field with the exact path of the executable to be run
 #*If the application needs command line arguments or stdin input, these can be provided in the "Arguments" and "stdin file" fields, respectively.
 === MPI applications ===
@@ Line 19: / Line 21: @@
 Different MPI libraries need different settings. First of all be sure that the application is compiled with the <tt>mpicc</tt> command of the corresponding library.
-*'''OpenMPI 1.8.1 compiled with Intel compiler:''' Load the <tt>intel/compiler/64/14.0/2013_sp1.3.174</tt> module from the same terminal as DDT is run, otherwise an error message will appear stating that the <tt>libimf.so</tt> shared library cannot be found.
+*'''OpenMPI 1.8.1 compiled with Intel compiler:''' Load the <tt>intel/compiler/64/14.0/2013_sp1.3.174</tt> module.
 *'''OpenMPI 1.8.1 compiled with GCC:''' Just follow the above steps. No other changes must be made.
-*'''MVAPICH2 2.0b compiled with Intel compiler:''' Load the <tt>mvapich2/intel/63/2.0b</tt> and <tt>intel/compiler/64/14.0/2013_sp1.3.174</tt> modules from the same terminal as DDT is run, otherwise missing shared libraries error messages will appear.
+*'''MVAPICH2 2.0b compiled with Intel compiler:''' Load the <tt>mvapich2/intel/63/2.0b</tt> and <tt>intel/compiler/64/14.0/2013_sp1.3.174</tt> modules.
-*'''MVAPICH2 2.0b compiled with GCC:''' Load the <tt>mvapich2/intel/63/2.0b</tt> module from the same terminal as DDT is run.
+*'''MVAPICH2 2.0b compiled with GCC:''' Load the <tt>mvapich2/intel/63/2.0b</tt> module.
-*'''Intel MPI 4.1.3:''' Load the <tt>intel/compiler/64/14.0/2013_sp1.3.174</tt> and <tt>intel-mpi/64/4.1.3/049</tt> modules from the same terminal as DDT is run.
+*'''Intel MPI 4.1.3:''' Load the <tt>intel/compiler/64/14.0/2013_sp1.3.174</tt> and <tt>intel-mpi/64/4.1.3/049</tt> modules.
-*'''MPICH 3.1 compiled with GCC:''' Load the <tt>mpich/ge/gcc/64/3.1</tt> module from the same terminal as DDT is run.
+*'''MPICH 3.1 compiled with GCC:''' Load the <tt>mpich/ge/gcc/64/3.1</tt> module.
 == Debug the application ==

← Older revision		Revision as of 10:54, 30 March 2015
Line 1:		Line 1:
−	~~== Starting Allinea DDT ==~~
−
−	~~Allinea DDT can be started both locally, inside the cluster, and remotely, from a laptop or PC.~~
−
−	*Starting locally
−
−	~~#Connect to server with X forwarding enabled (ssh -X).~~
−	~~#Go in Allinea DDT installation path and run ./ddt (/cm/local/allinea/bin/ for the Boston head node).~~
−
−	*Starting remotely
−
−	~~#Download Allinea tools from their website (http://www.allinea.com/products/downloads/download-allinea-ddt-and-allinea-map).~~
−	~~#Untar and run the installer file.~~
−	~~#Open Allinea DDT and at the Remote Launch menu open the settings and enter the hostname (username@ip_address) and the Allinea installation directory on the server.~~
−	#(Optional) Test the connection by pressing the Test Remote Launch button. (Might be prompted to provide the password, in order to connect to the server). If everything works out, the message "Remote Launch test completed successfully." will appear at the top left corner of the testing window.
−	~~#Press Ok and it will be ready to use.~~
−
	== Type of application ==		== Type of application ==

@@ Line 87: / Line 87: @@
 #*Statistics about the values of the array can be seen under the ''Statistics'' tab.
 #*The array values can be visualised, when pressing the ''Visualise'' button. The resulted graph will by default be a 3D one. An example image is shown below, where each process calculates a different sin curve.
+[[File:sin-curve.png|center|300px]]

← Older revision		Revision as of 15:21, 29 October 2014
Line 88:		Line 88:
	#*The array values can be visualised, when pressing the ''Visualise'' button. The resulted graph will by default be a 3D one. An example image is shown below, where each process calculates a different sin curve.		#*The array values can be visualised, when pressing the ''Visualise'' button. The resulted graph will by default be a 3D one. An example image is shown below, where each process calculates a different sin curve.

−	[[File:sin-curve]]	+	[[File:sin-curve.png]]

@@ Line 78: / Line 78: @@
 If a variable is an array then it can be seen in its dimensional view. Right click on the array and press ''View Array''.
-*If the array is statically allocated, then DDT automatically finds the number and the size of the dimensions.
+#Set the number and the size of the array's dimensions.
-*If the array is dynamically allocated, then DDT automatically finds the number of dimensions, but the user must provide the size for each dimension.
+#*If the array is statically allocated, then DDT automatically finds the number and the size of the dimensions.