Servers

Atlas Server

See: https://www.hep.technion.ac.il/DokuWiki/doku.php/danagroup:start

(you'll need your Atlas login credentials view/edit this content)

Remote Access to Group Computers

Desktop machines owned by the group are setup to allow remote access via ssh (secure shell). To do so, you must have

1. an existing user account on the machine
2. an ssh client installed on the machine you are using to perform the remote login
3. access to the Technion VPN for off-campus logins

If you need a user account, please contact Mark Fuller, the lab manager. He will provide you with a username and the machine address.

For those logging in from Windows, please see instructions here for installing the PuTTY client. Follow the instructions to enable X11 forwarding to run graphical applications over ssh. If logging in from Windows, you will need a local X11 server on your Windows computer - one option is XMing. By running the bundled executable xlaunch.exe, you may provide the X server configuration and pass the required parameters to PuTTY for login via ssh.

If you encounter a "connection refused" error, you may need to modify the X11 server settings.

Connecting

To connect via ssh, run the command ssh -Y $USERNAME@$ADDRESS (where $USERNAME and $ADDRESS are the variables you have been provided) and follow the commend prompts to enter your password and login. The -Y is needed to allow graphical programs to run. PuTTY users may have already turned on X forwarding by default.

Launching graphical applications

At the command prompt, enter the program name followed by & (to background the process) and enter. Some of the graphical applications you are most likely to launch are (N.B. $ just means "at a regular prompt"):

1. PyCharm Python IDE (select from toolbox menu): $ jetbrains-toolbox&
2. VS Codium IDE (same as Visual Studio Code): $ codium&
3. Nautilus file browser: $ nautilus&

If you forget the &, the application will take over the terminal until it is closed! If this happens, don't panic - there is an easy way to fix it:

1. From the terminal, ctrl+z to pause the application
2. A message in the terminal will appear (followed by a command prompt): [$n]+ Stopped $PROGRAM where $n is an integer and $PROGRAM is the application name
3. At the terminal command prompt, enter bg $n ($n is the integer!) and enter to background the application