Size: 583
Comment:
|
Size: 614
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 3: | Line 3: |
Vampir modules are visible after: {{{ |
* Vampir modules are visible after: {{{ |
Line 6: | Line 6: |
}}} | }}} |
Line 8: | Line 8: |
Load vampir modules: {{{ |
* Load vampir modules: {{{ |
Line 12: | Line 12: |
}}} | }}} |
Line 14: | Line 14: |
Compile and link with {{{ |
* Compile and link with {{{ |
Line 17: | Line 17: |
}}} | }}} |
Line 19: | Line 19: |
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 22: |
}}} | }}} * After execution with real input data a trace file ''progname.otf'' is generated. |
Line 24: | Line 26: |
After execution with real input data a trace file ''progname.otf'' is generated. Analyse trace file with vampir: {{{ |
* Analyse trace file with vampir: {{{ |
Line 29: | Line 29: |
}}} | }}} |
Using Vampir on JUROPA
- Vampir modules are visible after:
module load UNITE
- Load vampir modules:
module load vampirtrace module load vampir
- Compile and link with
vtf90 -vt:f90 mpif90 progname.f90 ...
- Possibly it is necessary to extend the LD_LIBRARY_PATH in the job script:
LD_LIBRARY_PATH=/usr/local/UNITE/packages/vampirtrace/5.8-parastation-intel/lib:$LD_LIBRARY_PATH
After execution with real input data a trace file progname.otf is generated.
- Analyse trace file with vampir:
vampir progname.otf