Differences between revisions 2 and 5 (spanning 3 versions)

Using Vampir on JUROPA

Load vampir modules:

module load vampirtrace
module load vampir

-  ⇤ ← Revision 2 as of 2010-03-16 12:30:46 → 
  Size: 583
  Editor: NicoleThomas
  Comment:
+   ← Revision 5 as of 2010-07-19 11:31:50 → ⇥
  Size: 839
  Editor: NicoleThomas
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
+## page was renamed from JuropaVampir
-Line 3:
+Line 4:
-Vampir modules are visible after:
{{{
+ * Vampir modules are visible after:
 {{{
-Line 6:
+Line 7:
-}}}
+ }}}
-Line 8:
+Line 9:
-Load vampir modules:
{{{
+ * Load vampir modules:
 {{{
-Line 12:
+Line 13:
-}}}
+ }}}
-Line 14:
+Line 15:
-Compile and link with 
{{{
+ * Compile and link with 
 {{{
-Line 17:
+Line 18:
-}}}
+ }}}
-Line 19:
+Line 20:
-Possibly it is necessary to extend the LD_LIBRARY_PATH in the job script:
{{{
+ *  Possibly it is necessary to extend the LD_LIBRARY_PATH in the job script:
 {{{
-Line 22:
+Line 23:
-}}}
+ }}}
-Line 24:
+Line 25:
-After execution with real input data a trace file ''progname.otf'' is generated.
+ (The option "--exports=LD_LIBRARY_PATH" in mpiexec-command doesn't help.) <<BR>><<BR>>
-Line 26:
+Line 27:
-Analyse trace file with vampir:
{{{
+ This is not necessary if the modules (UNITE, vampir, vampirtrace) are loaded in .bashrc!



 * After execution with real input data a trace file ''progname.otf'' is generated.

 * Analyse trace file with vampir:
 {{{
-Line 29:
+Line 36:
-}}}
+ }}}