Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion conf.py
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@

# If true, "(C) Copyright ..." is shown in the HTML footer. Default is True.
html_show_copyright = True
copyright = "2025, OceanHackWeek"
copyright = "2026, OceanHackWeek"


# -- HTML Config -------------------------------------------------
Expand Down
2 changes: 1 addition & 1 deletion ohw26/applicants.md
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,7 @@ We also encourage participants to explore more advanced topics before the hackwe

### Q: I don't know the first thing about version revision/control systems. Can I still apply?

During the hackweek we will use Git and GitHub but you are not expected to be an expert on it. In previous years we have offered refresher in the week prior to the actual OHW event. The organizing committee is deciding whether we can offer this in OHW24. You are welcome to check back here for this info, but we want to emphasize that nothing is better than trying it yourself first -- we recommend the [Software Carpentry lessons](https://swcarpentry.github.io/git-novice/) for learning git basic.
During the hackweek we will use Git and GitHub but you are not expected to be an expert on it. Check the [schedule](schedule.md) for any Git and GitHub sessions during the week. We want to emphasize that nothing is better than trying it yourself first -- we recommend the [Software Carpentry lessons](https://swcarpentry.github.io/git-novice/) for learning git basics.

Note that we will require you to create a [GitHub account](https://github.com/) before completing the application.

Expand Down
16 changes: 8 additions & 8 deletions ohw26/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,12 +27,10 @@ The schedule

The OceanHackWeek program consists of hands-on tutorials, visual presentations, and collaborative hack projects throughout a 5-day period.

<!--
```{admonition} Technical preparations and background for OceanHackWeek!
- Please review the ["Preparation" materials](../resources/prep/index.md) covering basic topics like `Git`, `GitHub`, `conda` package management and the OHW `JupyterHub`
- For tutorials on Python and R scientific tools and techniques that we will use in OceanHackWeek, see the [OHW 2022 tutorials page](../ohw22/tutorials-index/index.md)!
- Please review the ["Preparation" materials](../resources/prep/index.md) covering basic topics like `Git`, `GitHub`, `conda` package management and the OHW `JupyterHub` on [CryoCloud](https://book.cryointhecloud.com/)
- The [Compute FAQ](logistics/faq.md) covers logging in to CryoCloud, picking an environment, and shutting your server down
```
-->

```{image} ../assets/images/ohw_hacking/ohw23-group-pic.jpeg
:alt: OHW23 group picture
Expand Down Expand Up @@ -172,8 +170,10 @@ The events will be all-day workshops (approximately 9am - 5pm). Join us for five

schedule
Organizers <organizers>
<!-- Logistics <logistics/index> -->
<!-- tutorials-index/index -->
<!-- Projects <projects/index> -->
<!-- Information for Applicants <applicants> -->
Logistics <logistics/index>
tutorials-index/index
Tutorials Getting Started <tutorials_getting_started>
Projects <projects/index>
Information for Applicants <applicants>
OHW Fellows <../about/fellows.md>
```
86 changes: 86 additions & 0 deletions ohw26/logistics/faq.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,86 @@
# Compute FAQ

Quick answers for getting onto the hub at OHW26. For the full walkthrough with screenshots, see the [JupyterHub preparation page](../../resources/prep/jupyterhub.md).

## What are we using for compute?

[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.

The hub is at [https://hub.cryointhecloud.com](https://hub.cryointhecloud.com).

## What do I need to do before I log in?

Two things, both on GitHub:

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).
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`.

CryoCloud works out what you can access from your GitHub team membership, so it can't see you if your membership is private.

## What happens the first time I log in?

GitHub will ask you to **authorize `nasa-cryo-prod`** (the CryoCloud deployment, run by 2i2c) to read your organization and team membership.

```{admonition} Grant access to the oceanhackweek organization
:class: important

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.
```

## Which environment and how much RAM should I pick?

You choose both on the **Server Options** page, every time you start a server:

- **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.
- **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.

## Why is it taking so long to start?

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.

## How do I get the tutorials?

Use the nbgitpuller link for the profile you're running:

::::{tab-set}

:::{tab-item} Python

[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)

:::

:::{tab-item} R

[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)

:::

::::

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.

## What should I do when I'm finished for the day?

**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**.

`File > Log Out` does *not* shut the server down.

```{admonition} You will not lose your work
:class: important

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.
```

## Can I keep using CryoCloud after OceanHackWeek?

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.

Two notes on that form:

- **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.
- **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.

## Something's broken and this page didn't help

Ask in the `#ohw26_helpdesk` Slack channel. See the [Getting Help page](getting_help.md) for the other help groups.
23 changes: 6 additions & 17 deletions ohw26/logistics/getting_help.md
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# Getting Help

We know how overwhelming all of this information can be. Here is some for asking questions and figuring out where to turn for help.
We know how overwhelming all of this information can be. Here is some guidance on asking questions and figuring out where to turn for help.

You can ask anything on the Slack `#ohw25_general` channel, any time. Organizers and helpers are monitoring this channel, and some of your fellow hackweek participants may be able to help you! Also, feel free to send a direct message on Slack to any of the organizers or helpers.
You can ask anything on the Slack `#ohw26_general` channel, any time. Organizers and helpers are monitoring this channel, and some of your fellow hackweek participants may be able to help you! Also, feel free to send a direct message on Slack to any of the organizers or helpers.

## Online Resources

Expand All @@ -11,36 +11,25 @@ We provide a number of resources to help get you started on our [Resources page]

## Helpdesk

We've set up the `#ohw25_helpdesk` Slack channel to ask technical questions (or other types of questions, if you'd like).
We've set up the `#ohw26_helpdesk` Slack channel to ask technical questions (or other types of questions, if you'd like).

We will set up some helpdesk Slack user group that you can use to tag your question as, say, about Python. We'll list and describe those groups here. If you know the rough category of help that you may need, please tag one of the helpdesk user groups to get their attention. All help usergroups can be found by typing `@help-` and Slack will prompt with options.
We will set up some helpdesk Slack user group that you can use to tag your question as, say, about Python. We'll list and describe those groups here.

You are also welcome to direct message the helpers if you don't feel comfortable asking questions publicly.

### Slack help groups

- `@help-infrastructure` - For issues regarding the JupyterHub, Slack, Github, and Zoom.
- `@help-projects` - For help with managing projects, for instance asking how to set up a new repo, or organize meetings.
- `@help-python` - Questions about Python programming.
- `@help-r` - Questions about R programming.
- `@help-ml` - Questions about machine learning.
- `@help-git` - Questions about git.
- `@help-tutorials` - For help with tutorial logistics, like cloning the notebooks.
- `@help-website` - If there are any issues with the website tag us to take a look.

## During tutorials

Tune in on Slack for continuous Q&A!

- Ask questions on Slack! Use the `#ohw25_tutorials` channel to ask questions or check out answers to questions others have posed. We will use this same channel every day. Several of us will be monitoring this channel and addressing your questions throughout the tutorials
- Ask questions on Slack! Use the `#ohw26_general` channel to ask questions or check out answers to questions others have posed. We will use this same channel every day. Several of us will be monitoring this channel and addressing your questions throughout the tutorials
- **Vote up** questions from others to help the moderators prioritize which questions to ask the speaker during tutorials.
- Tutorial moderators will mark questions that are best answered by the instructor and ask helpers (and anyone else!) to answer the rest in real time. Then when the instructor ask if there are questions the moderators will read those reserved for the instructor.
- Zoom Chat will **not** be available. Ask on Slack!
- You will be muted at the start of the tutorial presentation. The moderator will review questions on Slack and ask the questions to the instructor during Q&A time.

## Projects

See the [Hacking at OHW25 page](../projects/index.md) for more information. Feel free to post a question on the `#ohw25_project` channel, too.
See the [Hacking at OHW26 page](../projects/index.md) for more information. Feel free to post a question on the `#ohw26_project` channel, too.

## Reporting a Code of Conduct violation

Expand Down
18 changes: 9 additions & 9 deletions ohw26/logistics/index.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
# Logistics Overview

OHW25 will be in person in Seattle, Washington at the University of Washington. We are committed to providing an engaging and full experience for everyone and will strive to facilitate cross communication and collaboration across all participants.
OHW26 will be in person at the [Bamfield Marine Sciences Centre](https://bamfieldmsc.com) on the West Coast of Vancouver Island, British Columbia, Canada. We are committed to providing an engaging and full experience for everyone and will strive to facilitate cross communication and collaboration across all participants.

## Time

OceanHackWeek 2025 will take place August 18-22. The in-person participants will be engaged in OceanHackWeek throughout the day.
OceanHackWeek 2026 will take place August 24-28. The participants will be engaged in OceanHackWeek throughout the day.

**Detailed schedule is available on the [Schedule page](../schedule.md).**

Expand All @@ -15,18 +15,18 @@ We will use the [OceanHackWeek Slack workspace](http://oceanhackweek.slack.com/)

[Go directly from a channel or direct message chat into a voice or video chat](https://slack.com/help/articles/216771908-Make-calls-in-Slack), with screen-sharing capability. This will be particularly useful during hack project time.

## OHW JupyterHub ("The Hub") and GitHub
## JupyterHub ("The Hub") and GitHub

- OHW JupyterHub ("The Hub"): [https://workshop.nmfs-openscapes.2i2c.cloud](https://workshop.nmfs-openscapes.2i2c.cloud)
- OHW GitHub organization: [https://github.com/oceanhackweek](https://github.com/oceanhackweek)
For tutorials and project work we use [CryoCloud](https://book.cryointhecloud.com/), a community JupyterHub where we set up pre-configured compute environments.

## Tutorials broadcasting
- The Hub: [https://hub.cryointhecloud.com](https://hub.cryointhecloud.com)
- OHW GitHub organization: [https://github.com/oceanhackweek](https://github.com/oceanhackweek)

We will use Zoom to broadcast all tutorials. The Zoom link will be distributed via Slack.
You need to be in the [`ohw26-participants`](https://github.com/orgs/oceanhackweek/teams/ohw26-participants) team **with your organization membership set to public** before you can log in. See the [FAQ](faq.md) for the short version, or the [JupyterHub preparation page](../../resources/prep/jupyterhub.md) for the full walkthrough with screenshots.

## Hack projects

See the [Hacking at OHW25 page](../projects/index.md) for more information.
See the [Hacking at OHW26 page](../projects/index.md) for more information.

## Getting Help

Expand All @@ -35,7 +35,7 @@ See the [Getting Help page](getting_help.md) for guidance and links to have your
```{toctree}
:hidden:

Overview <./overview>
FAQ <faq>
Getting Help <getting_help>
```

6 changes: 3 additions & 3 deletions ohw26/projects/index.md
Original file line number Diff line number Diff line change
@@ -1,16 +1,16 @@
# Hacking at OHW25
# Hacking at OHW26

## How will the projects be conducted?

We encourage project ideas from participants! Feel free to discuss existing or new project ideas **#ohw25_project** Slack channel prior to the event. Once ideas begin to gel and collaborative groups begin to form, the group can start getting into the weeds using a Jamboard or a combination of sticky notes and whiteboards. Later, each group needs to create a project Slack channel that starts with `ohw25_proj_` (say, `ohw25_proj_upwelling`), and create a Github repository (follow [these instructions](https://oceanhackweek.org/resources/prep/git.html#create-a-project-repository)). For the repository, please create a `README.md` file following [this README template](https://github.com/oceanhackweek/ohwyy_proj_template).
We encourage project ideas from participants! Feel free to discuss existing or new project ideas **#ohw26_project** Slack channel prior to the event. Once ideas begin to gel and collaborative groups begin to form, the group can start getting into the weeds using a Jamboard or a combination of sticky notes and whiteboards. Later, each group needs to create a project Slack channel that starts with `ohw26_proj_` (say, `ohw26_proj_upwelling`), and create a Github repository (follow [these instructions](https://oceanhackweek.org/resources/prep/git.html#create-a-project-repository)). For the repository, please create a `README.md` file following [this README template](https://github.com/oceanhackweek/ohwyy_proj_template).

<!-- and present a visual [elevator speech](https://en.wikipedia.org/wiki/Elevator_pitch) using one [Google Slide](https://docs.google.com/presentation/d/1eQKSdFHNGMDqGJMY4d-yGnNm4UrUj5kIS2mLQGPMZC8/edit#slide=id.p), -->

We've scheduled part of Day 1 for project ideation and the morning of Day 2 for setting up Slack channels and GitHub repositories. After that, time not allocated to shared tutorials and discussions may be devoted to working on the projects - hacking!

Please look over the information below for guidance about projects, how to get started and the motivations for working on projects.

## OHW25 projects list
## OHW26 projects list

Check out the [projects that formed this year!](projects_thisyear.md)

Expand Down
55 changes: 4 additions & 51 deletions ohw26/projects/projects_thisyear.md
Original file line number Diff line number Diff line change
@@ -1,54 +1,7 @@
# OHW25 Projects List

Projects from OceanHackWeek 2025.

### 1. BluRaspberry: Optimal Unmanned underwater vehicles (UUVs) Path Planning

- Project members: Erin Linebarger, Joyce Cai, Kayla Mitchell, Christian Sarason (mentor)
- GitHub repository: [https://github.com/oceanhackweek/ohw25_proj_BluRaspberry](https://github.com/oceanhackweek/ohw25_proj_BluRaspberry)
- [Presentation recording](https://www.youtube.com/watch?v=a0UlJTmM2-U)


### 2. FisHy PACE: Predicting fish distributions from phytoplankton using hyperspectral satellite data

- Project members: Max Titcomb, Isidora Rojas, Alberto Rivera, Israt Jahan Mili, Sam Alaimo, Jon Peake (mentor)
- GitHub repository: [https://github.com/oceanhackweek/ohw25_proj_fishpace](https://github.com/oceanhackweek/ohw25_proj_fishpace)
- [Presentation recording](https://youtu.be/a0UlJTmM2-U?feature=shared&t=3573)
- [Final Presentation slides](https://docs.google.com/presentation/d/1oRBbjYOHBqAwBdsVWctXN-ScwihK1mItiyZXgEEFPC4/edit?slide=id.p#slide=id.p)

### 3. RiptideRemix: Audio classificaiton and audio-synthesis of acoustic soundsources

- Project members: Kasey Castello, Mattie Toll, Oluwatofunmi Adeboye, Isabelle Brandicourt, Derya Gumustel, Dwight Owens (mentor)
- GitHub repository: [https://github.com/oceanhackweek/ohw25_proj_RiptideRemix](https://github.com/oceanhackweek/ohw25_proj_RiptideRemix)
- [Presentation recording](https://youtu.be/a0UlJTmM2-U?feature=shared&t=1690)

### 4. Data Dashboard powered by LLM

- Project members: Liangtong Wei, Finn Wimberly, Ava Wessel, Aidan Lewis, Dinal Meecle, Boris Shapkin (mentor)
- GitHub repository: [https://github.com/oceanhackweek/ohw25_proj_datadashboard_llm](https://github.com/oceanhackweek/ohw25_proj_datadashboard_llm)
- [Presentation recording](https://youtu.be/a0UlJTmM2-U?feature=shared&t=4314)

### 5. Mind the CHL Gap

- Project members: Bruna Cândido, Trina Xavier, Lilac Hong, Eli Holmes (mentor)
- GitHub repository: [https://github.com/oceanhackweek/ohw25_proj_gap](https://github.com/oceanhackweek/ohw25_proj_gap)
- [Presentation recording](https://youtu.be/a0UlJTmM2-U?feature=shared&t=5480)
- [Presentation](https://gamma.app/docs/Daily-Gap-Filled-Chlorophyll-a-Datasets-Using-Deep-Neural-Network-ozsc5xmxri96od1)

### 5. ArBu: Argo float and buoy data to visualize biogeochemical signals during hurricanes

- Project members:
- GitHub repository: [https://github.com/oceanhackweek/ohw25_proj_ArBu](https://github.com/oceanhackweek/ohw25_proj_ArBu)
- [Presentation recording](https://youtu.be/a0UlJTmM2-U?feature=shared&t=2602)
- [Presentation]()

### 6. AI Assisted Next Day Predictive Modeling for Zooplankton

- Project members: Syed Usama Imtiaz, Dafrosa Kataraihya, Ismat Jahan; Fellows: Dwight Owens, Dr. Rui Jin
- GitHub repository: [https://github.com/oceanhackweek/ohw25_proj_zooplankton](https://github.com/oceanhackweek/ohw25_proj_zooplankton)
- [Presentation recording](https://youtu.be/a0UlJTmM2-U?feature=shared&t=832)
- [Presentation]()

# OHW26 Projects List

Projects from OceanHackWeek 2026.

Project teams form during the first days of the hackweek, so this page fills in as the week goes on. Each project will be listed here with its members, its repository under the [`oceanhackweek` GitHub organization](https://github.com/oceanhackweek), and a link to its final presentation.

For a sense of what hack projects look like in practice, see the [OHW25 projects list](../../ohw25/projects/projects_thisyear.md).
Loading
Loading