rsnt_translations
56,420
edits
ARM software: Difference between revisions
Jump to navigation
Jump to search
Marked this version for translation
(Use VNC to fix the laggy interface issue) |
(Marked this version for translation) |
||
| Line 104: | Line 104: | ||
5. When done, exit the shell to terminate the allocation. | 5. When done, exit the shell to terminate the allocation. | ||
== Using VNC to fix the lag == | == Using VNC to fix the lag == <!--T:51--> | ||
<!--T:52--> | |||
[[File:DDT-VNC-1.png|400px|thumb|right|DDT on '''gra-vdi.computecanada.ca''']] | [[File:DDT-VNC-1.png|400px|thumb|right|DDT on '''gra-vdi.computecanada.ca''']] | ||
[[File:DDT-VNC-2.png|400px|thumb|right|Program on '''graham.computecanada.ca''']] | [[File:DDT-VNC-2.png|400px|thumb|right|Program on '''graham.computecanada.ca''']] | ||
<!--T:53--> | |||
The instructions above use X11 forwarding. X11 is very sensitive to packet latency. As a result, unless you happen to be on the same campus as the computer cluster, the ddt interface will likely be laggy and frustrating to use. This can be fixed by running ddt under VNC. | The instructions above use X11 forwarding. X11 is very sensitive to packet latency. As a result, unless you happen to be on the same campus as the computer cluster, the ddt interface will likely be laggy and frustrating to use. This can be fixed by running ddt under VNC. | ||
<!--T:54--> | |||
To do this, follow the directions on our [[VNC|VNC page]] to setup a VNC session. If your VNC session is on the compute node, then you can directly start your program under ddt as above. If you VNC session is on the login node or you are using the graham vdi node, then you need to manual launch the job as follows. From the ddt startup screen | To do this, follow the directions on our [[VNC|VNC page]] to setup a VNC session. If your VNC session is on the compute node, then you can directly start your program under ddt as above. If you VNC session is on the login node or you are using the graham vdi node, then you need to manual launch the job as follows. From the ddt startup screen | ||
<!--T:55--> | |||
* pick ''manually launch backend yourself'' job start option, | * pick ''manually launch backend yourself'' job start option, | ||
* enter the appropriate information for your job and press the ''listen'' button, and | * enter the appropriate information for your job and press the ''listen'' button, and | ||
* press the ''help'' button the right of ''waiting for you to start the job...''. | * press the ''help'' button the right of ''waiting for you to start the job...''. | ||
<!--T:56--> | |||
This will then give you the command you need to run to start your job. Allocate a job on the cluster and start your program as directed. As example of doing this would be (where $USER is your username and $PROGAM ... is the command to start your program) | This will then give you the command you need to run to start your job. Allocate a job on the cluster and start your program as directed. As example of doing this would be (where $USER is your username and $PROGAM ... is the command to start your program) | ||
<!--T:57--> | |||
<source lang="bash">[name@cluster-login:~]$ salloc ... | <source lang="bash">[name@cluster-login:~]$ salloc ... | ||
[name@cluster-node:~]$ /cvmfs/restricted.computecanada.ca/easybuild/software/2020/Core/allinea/20.2/bin/forge-client --ddtsessionfile /home/$USER/.allinea/session/gra-vdi3-1 $PROGRAM ... | [name@cluster-node:~]$ /cvmfs/restricted.computecanada.ca/easybuild/software/2020/Core/allinea/20.2/bin/forge-client --ddtsessionfile /home/$USER/.allinea/session/gra-vdi3-1 $PROGRAM ... | ||