Hp XC System 2.x Software Manuel d'utilisateur Page 28
- Page / 154
- Table des matières
- MARQUE LIVRES
Noté. / 5. Basé sur avis des utilisateurs
environment variables, such as PATH and MANPATH, to enable access to various installed
software.
One o f the key features of using m odules is to allow multiple versions of the same software to
be used in your environment in a controlled manner. For example, t wo different versions of the
Intel C compiler can be installed on the system atthesametime–theversionusedisbased
upon which Intel C compiler modulefile is loade d.
The HP XC software provides a number of modulefiles. You can also create your own
modulefiles. Modulefiles may be shared by many users on a system, and users m ay have their
own collection of mod ulefiles to supplem ent or replace th e shared modulefiles.
The f ollowing topics are addressed in the corresponding sections:
• Section 2.2.1 provides additional information on modulefiles.
• Section 2.2.2 discusses what modules are supplied.
• Section 2.2.3 discusses what modules are loaded by d efault.
• Section 2.2.4 discusses how to determine what modules are available.
• Section 2.2.5 discusses how to determine w hich modules are loaded.
• Section 2.2.6 discusses how to load a module.
• Section 2.2.7 discusses how to unload a module.
• Section 2.2.8 discusses module conflicts.
• Section 2.2.9 discusses creating your own module.
For further inform ation about the Modules software supplied with the HP XC system, s ee
the Modules Web site at the following URL:
http://sourceforge.net/projects/modules/
2.2.1 Notes on Modulefiles
A m od ulefile does not provide config uratio n of your environment until it is explicitly loaded.
That is, the specific modulefile for a software product or application must be loaded in your
environment (with the module load comm and ) before the configuration inform ation in
the modulefile is effective.
You or your system administrato r can configure you r environment so that any desired
modulefiles are automatically loaded for you when you log in to the system. You can also load a
modulefile yourself, as described in Section 2.2.6.
The Modules software is initialized when you log in to the HP XC system. It provides access
to the commands that allow you to display information about modulefiles, load or unload
modulefiles, or view a list of available modulefiles.
Modulefiles do not affect packages other than their intended package. For example, a modulefile
for a compiler will not adjust MPI_CC (the environment variable used by H P MPI to control
which compiler to use). A modulefile for a compiler simply makes it easier to access that
particular compiler; it does not try to determine how th e compiler wil l be used.
Similarly, a modulefile for HP MPI w ill no t try to adju st LD_LIBRARY_PATH to correspond to
the compiler that the mpicc com m and uses. The modulefile fo r MPI simply makes it easier to
access the mpi** scripts and libraries. You can specify th e compiler it uses through a variety of
mechanisms long after the modulefile i s loaded.
The previous scenarios were chosen in particular because the HP MPI mpicc command
uses heuristics to try to find a suitable compiler when MPI_CC or other default-overriding
mechanisms are not in effect. It is possible that mpicc will choose a compiler incon sistent
with the most recently l oaded compiler module. This could cause inconsistencies in the use
2-2 Using the System
- HP XC System Software 1
- Contents 3
- 3 Developing Applications 4
- 4 Debugging Applications 5
- 5 Tuning Applications 5
- 6UsingSLURM 5
- 8UsingHP-MPI 6
- 7 Using LSF 6
- 9UsingHPMLIB 7
- 10 Advanced Topics 8
- AExamples 8
- About This Document 11
- HP XC Inform ation 12
- For M ore Information 13
- Supplementary Information 13
- Manpages 14
- Related Information 15
- Typographical Conventions 16
- HP Encourages Your Comments 17
- 1.1 System Architecture 19
- 1.1.3 Storage and I/O 20
- 1.1.4 File System 20
- 1.2 User Environment 22
- 1.3.1 Parallel Applications 23
- 1.3.2 Serial Applications 23
- 1.4 Run-Time E nvironment 24
- 1.4.4 HP-MPI 25
- Using the System 27
- 2.2.1 Notes on Modulefiles 28
- 2.2.2 Supplied Modulefiles 29
- 2.2.6 Loading a Modulefile 30
- 2.2.7 Unloading a M odulefile 31
- 2.2.8 Modulefile Conflicts 31
- 2.2.9 Creating a Mod u lefile 32
- 2.3.1 Introduction 33
- 2.3.5 Launching Jobs 34
- $ man sinfo 39
- $ man -k keyword 39
- Using the System 2-13 39
- Developing Applications 41
- 3.2 Using Compilers 42
- 3.4 Interrupting a Job 43
- 3-4 Developing Applications 44
- Developing Applications 3-5 45
- 3-6 Developing Applications 46
- Developing Applications 3-7 47
- $ module load mpi 48
- $ mpicc -o mycode hello.c 48
- $ mpif90 -o mycode hello.f 48
- 3-8 Developing Applications 48
- 3.8 Developing Libraries 49
- 3.9 Advanced To pics 50
- 3-14 Deve loping Applications 54
- Developing Applications 3-15 55
- Debugging Applications 57
- 4-2 D ebugging Applications 58
- $ totalview 60
- 4-4 D ebugging Applications 60
- Debugging Applications 4-5 61
- 4-6 D ebugging Applications 62
- -verbosity %V %F" 63
- Debugging Applications 4-7 63
- 4-8 D ebugging Applications 64
- Etnus TotalView Version# 65
- Debugging Applications 4-9 65
- $ mpirun -srun -n2 Psimple 66
- 4-10 Debugging Applications 66
- $ squeue 67
- $ scancel --user username 67
- Debugging Applications 4-11 67
- Tuning Applications 69
- Using SLURM 71
- $ srun -N 16 -b myscript.sh 73
- $ srun -A -N 4 myscript.sh 73
- $ srun -a 6543 -j 73
- Using SLURM 6-3 73
- 6.4.2 srun Signal Handling 74
- 6.4.3 srun Run-Mode Options 74
- Using SLURM 6-5 75
- 6-6 Using SLURM 76
- 6.4.5 srun Control Options 77
- 6.4.6 srun I/O Options 78
- Using SLURM 6-9 79
- 6.4.7 srun Constraint Options 80
- Using SLURM 6-11 81
- 6.4.9 Using srun with HP-MPI 82
- 6.4.10 Using srun with LSF 82
- 6.8 Job Accounting 84
- 6.9 Fault Tolerance 84
- 6.10 Security 84
- Using LSF 85
- 7.1.2 Topology Support 86
- 7.1.3 Notes on LSF-HPC 87
- SLURM_JOBID=53 89
- SLURM_NPROCS=4 89
- 7-6 Using LSF 90
- 7.3.1 Getting Status of LSF 91
- $ bhosts 92
- 7-8 Using LSF 92
- 7.4 Submitting Jobs 93
- 7.4.3 Submitting a Serial Job 97
- Using LSF 7-17 101
- 7-18 Using LSF 102
- Using HP-MPI 111
- 8.3.3 Using srun with HP-MPI 114
- 8.3.4 Using LSF and HP-MPI 116
- 8.3.5 MPI Versioning 117
- 8.6 Truncated Messages 118
- 8.5 32-Bit B uilds on XC4000 118
- Using HP-MPI 8-9 119
- 8.9 Environment Variables 120
- 8.9.5 MPI_PIN_PERCENTAGE 121
- 8.9.6 MPI_PAGE_ALIGN_MEM 121
- 8.9.7 MPI_MAX_WINDOW 121
- 8.9.8 MPI_ELANLOCK 121
- 8.9.9 MPI_USE_LIBELAN 121
- 8.9.10 MPI_USE_LIBELAN_SUB 122
- Work-arounds 124
- Using HP MLIB 125
- 9.1.2 MLIB and Module Files 126
- 9.2.1 Platform Sup port 126
- 9.2.2 Library Support 126
- 9.2.3 MPI Parallelism 126
- 9.2.4 Modulefiles and MLIB 127
- 9.2.6 Compiling and Linking 127
- 9.2.7 Licensing 128
- 9.2.8 MLIB Man pages 128
- 9.3.1 Platform Sup port 128
- 9.3.2 Library Support 128
- 9.3.3 MPI Parallelism 129
- 9.3.4 Modulefiles and MLIB 129
- 9.3.5 Compiling and Linking 129
- 9.3.6 Licensing 130
- 9.3.7 MLIB Man pages 130
- Advanced Topics 131
- Examples 135
- $ lshosts 140
- Show the environment: 142
- Run the job: 142
- View the running job: 142
- View the finished job: 142
- Examples A-9 143
- Glossary 145
- Glossary-2 146
- Glossary-3 147
- Glossary-4 148
- Glossary-5 149
- Glossary-6 150
Produits connexes et manuels pour Logiciel Hp XC System 2.x Software
(41 pages)
(81 pages)© 2020, manymanuals.fr. Tous droits réservés | 0.024 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Commentaires sur ces manuels