Cookies on this website

We use cookies to ensure that we give you the best experience on our website. If you click 'Accept all cookies' we'll assume that you are happy to receive all cookies and you won't see this message again. If you click 'Reject all non-essential cookies' only necessary cookies providing core functionality such as security, network management, and accessibility will be enabled. Click 'Find out more' for information on how to change your cookie settings.

Starting and using a Linux remote desktop

When you select the Remote Desktop option from the Interactive Apps menu you will be presented with a form to define the facilities you require for your remote desktop session.

Interactive Apps menu

New desktop configuration screenNew desktop configuration screen

 

For most uses, the 'Standard' session will be adequate, if you can use this option please do, as this ensures we can support many more sessions. This session will give you 2 (virtual) cores and 15GB of memory and is fine for running FSLEyes, web browsing, submitting cluster tasks and similar tasks.

Next enter a duration - minimum 0.1 day, maximum 10 days. This is the maximum duration of your session, and fractions allow for the requesting of sessions lasting from 2.4 hours. 

Finally, if you job absolutely requires a CUDA device then you can select the GPU type from the drop-down menu, which will expose an additional option for quantity of GPUs {default 1). The duration of your session will auto-adjust if it is greater than the maximum allowed on a GPU (60 hours) - you will see '3' in the duration box (due to the way the web site works), but this will be reduced automatically to 60 hours when the session is requests.

We have very limited numbers of GPU enabled hosts, so you may experience significant delays in obtaining your session.

Now click on Launch to request a desktop session.

If you see a red box appear titled 'Failed to submit session with the following error' and detail talking about 'Job violates accounting/QOS policy' then you have requested a second desktop session - this is not allowed for fair-share reasons.

Error box you will see at the top of the page if you already have a session running

If you are certain you need more resources than the default then you can select 'Advanced' from the drop-down, revealing options for RAM and cores/threads. We have limited resources, so the RAM, in particular is in short supply, so any session requesting more than 32GB of RAM may have a significant wait before it can be fulfilled.

Accessing the desktop session

If you have just requested a session you will now be taken to the My Interactive Sessions page. If you are returning to OOD then you can find this page by clicking on the two overlapping squares (on large screens this also has a text label!).
There may be a delay whilst your job starts on the cluster, during this period the pending job will have a blue section header. Once it is running this will turn green.

Open OnDemand Interactive SessionsOpen OnDemand Interactive Sessions

 

In the example here, there are two sessions, a MATLAB one and a FMRIB Desktop, both of which use Virtual Network Computing (VNC) technology to provide the graphical interface. The Interactive sessions card has the following information/links:

  • The header shows the job ID (in parentheses) on the left, the number of course and state on the right
  • Host details the cluster machine the job is running on, Created at, the start time, a count down of the time remaining for the session.
  • The Session ID link takes you to a folder view for the job. This includes logs and files that may assist IT support when diagnosing problems, but ordinarily you don't need to look in here.
  • Submit support ticket takes you to the support submission form. The View Only link may be requested by support so that they can follow along with the issue that you are seeing.
  • The Delete button terminates this session - any unsaved work will be lost.
  • The two sliders along the bottom of the card allow you to adjust the compression level and image quality - increase compression and decrease quality if you are on a slow network link, e.g. WiFi or non-full fibre home internet connections.
    Warning - do NOT set compression to '0' - this is likely to cause 'Incomplete zlib block' errors in the VNC session. 
  • The Launch Remote Desktop button begins your VNC session in a new web browser tab.

The VNC session is provided by noVNC and runs a Mate desktop environment.

To the right of the view is the noVNC menu, click the tag to open the icon bar. The icons within are dependent on the device you are accessing from (touch devices get mouse options), but the basic icons are:

  • 'A' - a pallete with modifier keys that may not map to keys on your keyboard
  • Clipboard - allows for capturing the desktop clipboard or sending your clip board to the remote server
  • Cog - settings, ordinarily you don't need to change these, but you may wish to change the Scaling mode and quality sliders.
  • The final icon disconnects you from noVNC - once disconnected, your current VNC session is terminated - to return to your desktop you will need to relaunch via the My Interactive Sessions page.

The Mate Desktop

The Mate desktop has two panels by default, the top housing the application menus and application launcher icons (file browser, terminal, Firefox web browser and Thunderbird mail client by default) and on the far right the date and time. The bottom panel has a button to show the desktop and then on the far right, four virtual desktop switchers allowing you to organise your windows by task.

Most interactions with the FMRIB cluster will be via the terminal application which provides a command line from which you can launch FSL applications and submit to the cluster via fsl_sub. Most software packages need activating using environment modules - use the module commands to list/activate/deactive.