cc_staff
1,857
edits
VNC: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 298: | Line 298: | ||
<!--T:107--> | <!--T:107--> | ||
The VDI nodes have special hardware and virtual server configuration | The VDI nodes have a special hardware and persistant virtual server configuration that support direct vncviewer connections and gpu accelerated OpenGL graphics for appropriately configured software applications. The VDI nodes also provide an extra layer of local software modules in addition to the standard global modules. These are made available by loading the SnEnv or StdEnv user environments respectively. On the clusters the StdEnv (and thus all modules in the global software stack) are loaded for you by default. On gra-vdi however when you login no environment or modules are loaded by default thus you will see: | ||
{{Commands|prompt=[name@gra-vdi4]$ | |||
|[user@gra-vdi3:~] module list | |||
|No modules loaded | |||
}} | |||
Therefore, before running any graphical software on gra-vdi you must first manually load one of following ... | |||
== CVMFS == <!--T:130--> | |||
<!--T:132--> | |||
Alliance software modules reside under /cvmfs and are available by default when you log into Graham, Cedar and Béluga. However, these modules are not loaded by default when you connect into gra-vdi over tigervnc. To load them open a new terminal window on gra-vdi and running the following: | |||
<!--T:155--> | |||
{{Commands|prompt=[name@gra-vdi4]$ | |||
|module load CcEnv StdEnv/2020 | |||
|module avail | |||
}} | |||
<!--T:134--> | |||
Alliance software modules will now be available on gra-vdi identical to the clusters. While these modules should always work reliably when running graphical applications on compute nodes, some may have stability issues running on gra-vdi such as sudden crashing or strange graphical artifacts including transparent windows or missing menus. To work around such problems, use an equivalent package from nix as described in the previous section; better graphics performance may also be realized. While the nix module provides a vast number of optimized/stable open-source packages for gra-vdi, it does not provide commercial module equivalents for ANSYS, COMSOL or StarCCM. These can be accessed by opening a new terminal window on gra-vdi and running: | |||
<!--T:156--> | |||
{{Commands|prompt=[name@gra-vdi4]$ | |||
|module load SnEnv | |||
|module avail | |||
}} | |||
== NIX == <!--T:108--> | == NIX == <!--T:108--> | ||
| Line 360: | Line 387: | ||
<!--T:128--> | <!--T:128--> | ||
Note that it is also possible to preload ''vglfaker.so'' via the <code>LD_PRELOAD</code> environment variable. This is generally a bad idea as it applies indiscriminately to all binaries, and those that require a different ''vglfaker.so'' than that set in <code>LD_PRELOAD</code> will then fail; however, it can be used safely in some cases in wrapper scripts. | Note that it is also possible to preload ''vglfaker.so'' via the <code>LD_PRELOAD</code> environment variable. This is generally a bad idea as it applies indiscriminately to all binaries, and those that require a different ''vglfaker.so'' than that set in <code>LD_PRELOAD</code> will then fail; however, it can be used safely in some cases in wrapper scripts. | ||
</translate> | </translate> | ||