This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
survival_guide [2020/05/26 15:06] ccrosby [The user interface (not)] |
survival_guide [2022/02/01 18:38] (current) alopis |
||
|---|---|---|---|
| Line 8: | Line 8: | ||
| - The computers that make up the HPC cluster do not run faster than a good desktop computer, nor do they usually have particularly impressive amounts of memory. | - The computers that make up the HPC cluster do not run faster than a good desktop computer, nor do they usually have particularly impressive amounts of memory. | ||
| - The system is designed to be used in batch mode. The user prepares a job, submits it to the queue, and the system executes it when the requested amount of resources become available. | - The system is designed to be used in batch mode. The user prepares a job, submits it to the queue, and the system executes it when the requested amount of resources become available. | ||
| - | - You can request an interactive session, which will give you access to a compute node in the cluster. | + | - You can request an interactive session, which will give you access to a compute node in the cluster. |
| - Access to the system is by means of secure-shell (ssh). | - Access to the system is by means of secure-shell (ssh). | ||
| - Data can be copied to or from the system by means of secure copy (scp) or rsync. | - Data can be copied to or from the system by means of secure copy (scp) or rsync. | ||
| Line 19: | Line 19: | ||
| ===== The user interface (not) ===== | ===== The user interface (not) ===== | ||
| - | Although personal computers running Linux have user interfaces that are very similar to Windows or Mac, the ssh-login to the HPC cluster runs in command line text mode only, by default using the Bash shell. | + | Although personal computers running Linux have user interfaces that are very similar to Windows or Mac, the ssh-login to the HPC cluster runs in command line text mode only, by default using the Bash shell. |
| * **ls** - provide a list of the files in the current directory | * **ls** - provide a list of the files in the current directory | ||
| - | * **ls** -l - provide a more detailed listing of the files in the current directory | + | * **ls -l** - provide a more detailed listing of the files in the current directory |
| * **pwd** - gives the current directory path (Present Working Directory) | * **pwd** - gives the current directory path (Present Working Directory) | ||
| * **mkdir** - create a new directory | * **mkdir** - create a new directory | ||
| * **cd** - change to a new directory | * **cd** - change to a new directory | ||
| + | * **cp** - copy a file (remember to specify the file **and** the location to copy it to) | ||
| + | * **mv** - move a file (either rename it or cut/paste it into a directory). | ||
| * **rmdir** - remove a directory | * **rmdir** - remove a directory | ||
| * **rm** - remove a file | * **rm** - remove a file | ||
| Line 37: | Line 39: | ||
| Here are examples of the most common module operations that you will need to use on the cluster: | Here are examples of the most common module operations that you will need to use on the cluster: | ||
| * **module avail** - To list all available packages | * **module avail** - To list all available packages | ||
| + | * **module avail 2>&1 | grep // | ||
| * **module avail chpc** - List just the chpc modules group - this contains most of the useful modules | * **module avail chpc** - List just the chpc modules group - this contains most of the useful modules | ||
| * **module avail chpc/ | * **module avail chpc/ | ||
| Line 42: | Line 45: | ||
| * **module load chpc/ | * **module load chpc/ | ||
| * **module list** - To list all the modules which you have already loaded in this session | * **module list** - To list all the modules which you have already loaded in this session | ||
| - | * **module | + | * **module |
| * **module purge** - to unload all modules that you have loaded | * **module purge** - to unload all modules that you have loaded | ||
| Line 59: | Line 62: | ||
| For GCC and the Intel compilers, however, you will have to load the modules that you wish to link your code against separately. | For GCC and the Intel compilers, however, you will have to load the modules that you wish to link your code against separately. | ||
| - | Finally, there are a few software packages (mostly those that are commercially licensed, such as Ansys/ | + | Finally, there are a few software packages (mostly those that are commercially licensed, such as Ansys/ |
| ==== Installing New Software on Lengau ==== | ==== Installing New Software on Lengau ==== | ||