Skip to content

Latest commit

 

History

History
86 lines (52 loc) · 4.56 KB

server.md

File metadata and controls

86 lines (52 loc) · 4.56 KB

Workshop Server (and how to download at home)

The workshops are running on a set of cloud servers provided by the Oracle Cloud Infrastructure.

These have been configured to provide enough resource for lots of people to log in at the same time (the Oracle server has 48 virtual cores - Intel(R) Xeon(R) Platinum 8167M CPU @ 2.00GHz - and 314 GB RAM!). There are no usernames or passwords. To log in, please click the below link (will open in new tab):

Log in to the Oracle server

Please only click this once, as it will log you into a new session. This may take between 30-60 seconds, so please be patient. DO NOT CLICK MULTIPLE TIMES, else you will launch too many sessions and may block anyone else from connecting.

Reconnecting to the server

If you accidentally close the browser page you can reconnect to the server with your existing login using the below link (opens in new tab):

Reconnect to the Oracle server

Logging out when you are finished

PLEASE LOG OUT WHEN YOU ARE FINISHED. You can log out by clicking on the "Logout" icon in the top right of the screen. Logging out will free up your session so that it can be used by someone else.

Note that you will be kept logged in for as long as the server page is open in your browser. You will only be automatically logged out about 60 minutes after you have closed the server page.

Also please note that all of your files will be deleted after you log out from the server. There is no way for us to save or retrieve your files. Please ensure you download anything you need before logging out.

Backup servers

If for some reason the workshop server above is not available, you can try the backup server below.

Browser compatibility

The 3D molecule viewer embedded in the Jupyter notebooks requires that you access the workshop using a modern browser that supports WebSockets (e.g chrome, firefox, safari, edge and modern versions of internet explorer). You can test if your browser supports WebSockets by visiting this page.

Server details

Once logged in, you will find a JupyterHub browser with directories for all of the workshops. The instructions that come with each workshop will tell you which directory to use.

You will be allocated up to 2 cores and 5 GB of memory on the server, as it is intended for demonstration and training rather than production calculations.

Running the workshop at home

The server will remain online for the foreseeable future, and you are welcome to log in and use it after the workshop week is over.

All software used during the workshop is open source, and so the workshop server image is available for free download. It is available on docker. You can download and run it on your own computer by installing docker and then typing;

docker run -it chryswoods/bss-workshop:latest

The image is several gigabytes in size, so may take a while to download (and you must have at least 10GB of free disk space).

This will download and run the image, starting a Jupyter browser which you can connect to using the URL that will be printed out, looking something like;

    Copy/paste this URL into your browser when you connect for the first time,
    to login with a token:
        http://localhost:8888/?token=2759c17079a3922e7942946e4933b92a1cc06013d22615f7

Note that the image can only be run on computers with X86-64 processors that support AVX instructions (e.g. like most Intel processors since 2011).

The workshop image will be updated over time. To get the latest version please run

docker pull chryswoods/bss-workshop:latest

You should also run the command

update_workshops

inside the bash terminal in the Jupyter session to ensure that you have updated the workshop material itself to the latest version.

If you are running the image on a Mac in OS X, then be aware that the OS X version of docker can silently corrupt libraries. If you find that Python modules cannot import because the library is not recognised as "elf", then you need to re-install the module. For example, if mdtraj cannot import, then you can reinstall using

conda install mdtraj