Skip to content
Snippets Groups Projects
Commit 636389a1 authored by David Hrbáč's avatar David Hrbáč
Browse files

Typo

parent 7963a0c0
No related branches found
No related tags found
No related merge requests found
......@@ -41,7 +41,8 @@ Please [follow the documentation](shell-and-data-access/).
To have the OpenGL acceleration, **24 bit color depth must be used**. Otherwise only the geometry (desktop size) definition is needed.
_At first VNC server run you need to define a password._
!!! Hint
At first VNC server run you need to define a password.
This example defines desktop with dimensions 1200x700 pixels and 24 bit color depth.
......@@ -97,7 +98,7 @@ $ ssh login2.anselm.it4i.cz -L 5901:localhost:5901
```
x-window-system/
_If you use Windows and Putty, please refer to port forwarding setup in the documentation:_
If you use Windows and Putty, please refer to port forwarding setup in the documentation:
[x-window-and-vnc#section-12](../get-started-with-it4innovations/accessing-the-clusters/graphical-user-interface/x-window-system/)
#### 7. If you don't have Turbo VNC installed on your workstation
......@@ -112,15 +113,15 @@ Mind that you should connect through the SSH tunneled port. In this example it i
$ vncviewer localhost:5901
```
_If you use Windows version of TurboVNC Viewer, just run the Viewer and use address **localhost:5901**._
If you use Windows version of TurboVNC Viewer, just run the Viewer and use address **localhost:5901**.
#### 9. Proceed to the chapter "Access the visualization node"
_Now you should have working TurboVNC session connected to your workstation._
Now you should have working TurboVNC session connected to your workstation.
#### 10. After you end your visualization session
_Don't forget to correctly shutdown your own VNC server on the login node!_
Don't forget to correctly shutdown your own VNC server on the login node!
```bash
$ vncserver -kill :1
......@@ -135,13 +136,16 @@ qviz**. The queue has following properties:
| ---------------------------- | -------------- | ----------------- | ----- | --------- | -------- | ------------- | ---------------- |
| **qviz** Visualization queue | yes | none required | 2 | 4 | 150 | no | 1 hour / 8 hours |
Currently when accessing the node, each user gets 4 cores of a CPU allocated, thus approximately 16 GB of RAM and 1/4 of the GPU capacity. _If more GPU power or RAM is required, it is recommended to allocate one whole node per user, so that all 16 cores, whole RAM and whole GPU is exclusive. This is currently also the maximum allowed allocation per one user. One hour of work is allocated by default, the user may ask for 2 hours maximum._
Currently when accessing the node, each user gets 4 cores of a CPU allocated, thus approximately 16 GB of RAM and 1/4 of the GPU capacity.
!!! Note
If more GPU power or RAM is required, it is recommended to allocate one whole node per user, so that all 16 cores, whole RAM and whole GPU is exclusive. This is currently also the maximum allowed allocation per one user. One hour of work is allocated by default, the user may ask for 2 hours maximum.
To access the visualization node, follow these steps:
#### 1. In your VNC session, open a terminal and allocate a node using PBSPro qsub command
_This step is necessary to allow you to proceed with next steps._
This step is necessary to allow you to proceed with next steps.
```bash
$ qsub -I -q qviz -A PROJECT_ID
......@@ -153,7 +157,7 @@ In this example the default values for CPU cores and usage time are used.
$ qsub -I -q qviz -A PROJECT_ID -l select=1:ncpus=16 -l walltime=02:00:00
```
_Substitute **PROJECT_ID** with the assigned project identification string._
Substitute **PROJECT_ID** with the assigned project identification string.
In this example a whole node for 2 hours is requested.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment