Skip to content

Connecting to Brain

Jump to bottom
John Yocum edited this page Apr 9, 2024 · 18 revisions

Brain is accessible via SSH (command-line) and X2Go (graphical environment). For tasks involving batch operations, SSH connections are preferred. You simply connect, queue your job, and logout. For interactive operations, the method of connection will depend on the software you wish to use. If your toolchain (or pipeline) is consists of command-line software, SSH may offer a better (more responsive) experience. However, if you need to use a graphical application, such as RStudio, you'll need to use X2Go.

NOTE: Regardless of the method you use, for interactive sessions, a session is typically limited to running one job at a time. However, you may run multiple jobs under the same session, if you use a utility like Screen within the session.

For security purposes, access to Brain is restricted by user, group, and IP address. Direct access is permitted from DEOHS desktop computers, and remote computing environments. For off-campus access, you'll need to establish an SSH session via Vector, either as a shell or tunnel.

SSH

SSH is the primary means of accessing Brain. You are free to use any SSH client you like. For Windows users, this will typically be PuTTY. For Apple users, the builtin OpenSSH client is most popular.

  • Host / Server: brain.deohs.washington.edu
  • Username: Your UW NetID
  • Password: Your UW NetID Password

Below are some guides on using common SSH clients:

NOTE: If you find that your SSH session disconnects after being idle for a period of time, you can try enabling the keepalive feature of your SSH client. In PuTTY, you'll find this under Connection > "Sending of null packets to keep session active". A setting of 300 to 600 seconds is reasonable.

X2Go

Session

  • Session name: Brain
  • Host: brain.deohs.washington.edu
  • Login: Your NetID
  • Session type: ICEWM

If you are connecting from a system other than a DEOHS (dept.) desktop, you will need to use an SSH tunnel. Check the box "Use Proxy server for SSH connection". Then, under "Proxy server", use the following:

  • Type: SSH
  • Host: <address of SSH proxy server - ask your IT dept.>
  • Same login as on X2Go Server: Checked
  • Same password as on X2Go Server: Checked

Connection

  • Connection speed: WAN
  • Compression: 256-rdp-compressed

NOTE: You may want to play with the compression setting to find what works best for you. Keep in mind, some of the options can use a lot of network bandwidth, which may perform poorly when connecting via wifi or from off campus. We recommend the 256-rdp-compressed, as it offers a good balance of low bandwidth, along with great image quality.

XRDP

XRDP uses Microsoft Remote Desktop to connect to a Linux system. The experience does have some limitations compared to X2Go, such as:

  • Can't change display resolution on an existing session
  • Can't copy-paste between your computer and the server
  • No audio support

However, for macOS users, this may offer a better user experience compared to X2Go.

NOTE: These instructions currently assume you are connecting from a DEOHS wired subnet. A revision to this process enabling access from other networks can be expected.

  1. Connect to the head node using SSH, as outlined previously on this page
  2. Configure Xorg (graphical display system) to default to using the IceWM environment

    • Create a file called "~/.Xclients" containing the following content (easiest editor option is "nano ~/.Xclients"):

      #!/usr/bin/bash

      exec /usr/bin/icewm-session

    • Make this file executable with this shell command: chmod +x ~/.Xclients

  3. Download the Remote Desktop configuration file for BRAIN from, https://portal.deohs.washington.edu/gatekeeper, and double-click it to connect. For the initial prompt use your UW NetID, and approve the Duo push on your phone.
Clone this wiki locally