|
| 1 | +# Compute FAQ |
| 2 | + |
| 3 | +Quick answers for getting onto the hub at OHW26. For the full walkthrough with screenshots, see the [JupyterHub preparation page](../../resources/prep/jupyterhub.md). |
| 4 | + |
| 5 | +## What are we using for compute? |
| 6 | + |
| 7 | +[CryoCloud](https://book.cryointhecloud.com/) — a community JupyterHub, run on [2i2c](https://2i2c.org) infrastructure, where we can set up pre-configured compute environments for the tutorials. We use it for tutorials and for project work. |
| 8 | + |
| 9 | +The hub is at [https://hub.cryointhecloud.com](https://hub.cryointhecloud.com). |
| 10 | + |
| 11 | +## What do I need to do before I log in? |
| 12 | + |
| 13 | +Two things, both on GitHub: |
| 14 | + |
| 15 | +1. **Accept the invitation** to the [OceanHackWeek GitHub organization](https://github.com/oceanhackweek), so that you show up in [`ohw26-participants`](https://github.com/orgs/oceanhackweek/teams/ohw26-participants). |
| 16 | +2. **Make your organization membership public.** Find yourself on the team page above, open your profile within the organization (a URL like `https://github.com/orgs/oceanhackweek/people/YOUR-USERNAME`), and check that **Membership** reads `public` rather than `private`. |
| 17 | + |
| 18 | +CryoCloud works out what you can access from your GitHub team membership, so it can't see you if your membership is private. |
| 19 | + |
| 20 | +## What happens the first time I log in? |
| 21 | + |
| 22 | +GitHub will ask you to **authorize `nasa-cryo-prod`** (the CryoCloud deployment, run by 2i2c) to read your organization and team membership. |
| 23 | + |
| 24 | +```{admonition} Grant access to the oceanhackweek organization |
| 25 | +:class: important |
| 26 | +
|
| 27 | +On the authorization screen, make sure **`oceanhackweek`** is granted — if it shows an `✕` with a **Grant** button next to it, click **Grant** before you authorize. |
| 28 | +``` |
| 29 | + |
| 30 | +## Which environment and how much RAM should I pick? |
| 31 | + |
| 32 | +You choose both on the **Server Options** page, every time you start a server: |
| 33 | + |
| 34 | +- **Environment** — the **OceanHackWeek Python Image** for the tutorials and most project work. If you're working in R, pick the **Py-Rocket** R image instead. |
| 35 | +- **Resource Allocation** — **8 GB of RAM** should be enough for the tutorials. Pick the smallest allocation that does the job; the compute is shared and donated. |
| 36 | + |
| 37 | +## Why is it taking so long to start? |
| 38 | + |
| 39 | +Starting a new node and pulling our environment can take several minutes, especially when everyone logs in at once at the beginning of a tutorial. Be patient rather than reloading repeatedly. |
| 40 | + |
| 41 | +## How do I get the tutorials? |
| 42 | + |
| 43 | +Use the nbgitpuller link for the profile you're running: |
| 44 | + |
| 45 | +::::{tab-set} |
| 46 | + |
| 47 | +:::{tab-item} Python |
| 48 | + |
| 49 | +[Pull the tutorials into JupyterLab](https://hub.cryointhecloud.com/hub/user-redirect/git-pull?repo=https%3A%2F%2Fgithub.com%2Foceanhackweek%2Fohw-tutorials&urlpath=lab%2Ftree%2Fohw-tutorials%2F&branch=OHW26) |
| 50 | + |
| 51 | +::: |
| 52 | + |
| 53 | +:::{tab-item} R |
| 54 | + |
| 55 | +[Pull the tutorials into RStudio](https://hub.cryointhecloud.com/hub/user-redirect/git-pull?repo=https%3A%2F%2Fgithub.com%2Foceanhackweek%2Fohw-tutorials&urlpath=rstudio%2F&branch=OHW26) |
| 56 | + |
| 57 | +::: |
| 58 | + |
| 59 | +:::: |
| 60 | + |
| 61 | +Clicking the link again later will pull in any updates and merge them with your own changes. See the [extended discussion](../../resources/prep/jupyterhub.md#how-do-i-get-the-tutorial-repository) for the details, and for the `git`-based alternative. |
| 62 | + |
| 63 | +## What should I do when I'm finished for the day? |
| 64 | + |
| 65 | +**Please shut down your server.** Go to `File > Hub Control Panel` (or straight to [https://hub.cryointhecloud.com/hub/home](https://hub.cryointhecloud.com/hub/home) if you've closed the tab), then click **Stop My Server**. |
| 66 | + |
| 67 | +`File > Log Out` does *not* shut the server down. |
| 68 | + |
| 69 | +```{admonition} You will not lose your work |
| 70 | +:class: important |
| 71 | +
|
| 72 | +Stopping your server does **not** delete any of your files. It just releases the compute, like turning off your desktop at the end of the day. |
| 73 | +``` |
| 74 | + |
| 75 | +## Can I keep using CryoCloud after OceanHackWeek? |
| 76 | + |
| 77 | +Yes. Go through CryoCloud's own [getting started instructions](https://book.cryointhecloud.com/getting-started/), including the survey. You'll be invited to their Slack channel, which is how the hub admins and users stay in touch. |
| 78 | + |
| 79 | +Two notes on that form: |
| 80 | + |
| 81 | +- **Award number** — if you don't have a grant number, enter `OceanHackWeek`. It doesn't bill any grant; it's used for tracking and for justifying their compute credits. |
| 82 | +- **Institution** — the list is a bit US-centric at the moment. If one of the options is a reasonable match but there's a better term for your situation, put that down under *Other*, so the form can be improved. |
| 83 | + |
| 84 | +## Something's broken and this page didn't help |
| 85 | + |
| 86 | +Ask in the `#ohw26_helpdesk` Slack channel. See the [Getting Help page](getting_help.md) for the other help groups. |
0 commit comments