VNC: Difference between revisions

Jump to navigation Jump to search

VNC (view source)

Revision as of 00:09, 13 April 2024

821 bytes removed ,  6 months ago
no edit summary
No edit summary
No edit summary
Line 298: Line 298:


<!--T:107-->
<!--T:107-->
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:
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.  However when you login to gra-vdi you will discover there are no modules loaded by default:


<!--T:176-->
<!--T:176-->
Line 307: Line 307:


<!--T:177-->
<!--T:177-->
Therefore, before running any graphical software on gra-vdi you must first manually load one of following ...
Before you can load any software module on gra-vdi you must first manually load either the global <code>StdEnv</code> environment or the local <code>SnEnv</code> environment.  


== CVMFS == <!--T:130-->
== StdEnv == <!--T:130-->


<!--T:132-->
<!--T:131-->
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 to gra-vdi over tigervnc.  To load them, open a new terminal window on gra-vdi and run the following:
Most users will find it sufficient to load the StdEnv module on gra-vdi.  Doing so will provide access to the same software modules that are loaded by default on the clusters:


<!--T:155-->
{{Commands|prompt=[name@gra-vdi4]$  
{{Commands|prompt=[name@gra-vdi4]$  
|module load CcEnv StdEnv/2020
|module load CcEnv StdEnv/2023
|module avail
|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:
== SnEnv ==  <!--T:132-->
 
<!--T:155-->
In some rare cases users will need to load a locally installed module(s) on gra-vdi.  To do this the <code>SnEnv</code> must first be loaded:


<!--T:156-->
<!--T:156-->
Line 332: Line 334:


<!--T:110-->
<!--T:110-->
The nix module on gra-vdi provides open-source software optimized to use accelerated OpenGL whenever possible. To load the nix module do:
Instead of loading SnEnv or StdEnv users may want to use NIX which provides open-source software optimized to use accelerated OpenGL whenever possible. NIX can be used by loading the   following <code>nix</code> module which is currently only available on gra-vdi and graham:


<!--T:151-->
<!--T:151-->
Line 340: Line 342:


<!--T:112-->
<!--T:112-->
The nix and nix-env commands are now in your path to install (and use) nix software packages within your personal nix environment.
The nix and nix-env commands will now be in your path to install (and use) nix software packages inside your personal nix environment.


<!--T:114-->
<!--T:114-->
Roberpj
cc_staff
1,857

edits

Retrieved from "https://docs.alliancecan.ca/wiki/Special:MobileDiff/152121"

Navigation menu