We suggest that you use the Open OnDemand terminal interface hosted by the CRNCH Rogues Gallery if you are not able to download and use the local VM Image.
Please use the spreadsheet here to reserve a username to use for the duration of the tutorial. The organizers will share a password with you for your particular username.
- Log into rg-ood.crnch.gatech.edu with your GT username and password. For a tutorial, this will be provided to you along with a temporary password.
- Select the
Vortex Tutorialoption under theReconfigtab.
- Select the
- Check the fields (we recommend using 2 vCPUs) and hit “Launch” to start a terminal job.
- Wait about 30 seconds to one minute for the job to be launched on the server. When it switches to “Running”, you should be able to click
Connectto open a remote terminal on the server.
- This new window will have a tmux instance. Note that the escape for this particular instance is
Ctrl+Aso to create a new window you would useCtrl+Aand thenc.
- When you are done you can close the web window and your scheduled job will terminate automatically. Alternatively, you can go back to your
My Interactive Sessionstab in the Open OnDemand portal and hitDeleteto cancel your scheduled session. HitConfirmto delete the currently running job.- Note that your session will stay running for the length of the specified job (usually 1 hour by default).
Once you log in, your environment should already be set up. However, if you need to reinitialize your environment you can run the environment setup script.
$ . micro-tutorial-2022/set_vortex_env.sh
The tutorial repo is located under ~/micro-tutorial-2022/vortex_tutorials.
-
When launching a new job, the job may fail to launch with an I/O error.
Failed to submit session with the following error: sbatch: error: Batch job submission failed: I/O error writing script/environment to file.- Try to relaunch the job. This may just be related to small OOD bugs.
-
When opening a VNC or Virtual Desktop session, you get the error "Failed to establish a websocket connection".
- Clear the cache in your web browser, relogin and try to launch the job again. Specifically you may need to clear your cookies for gatech.edu domains.