diff --git a/_ext/team.yaml b/_ext/team.yaml index ddf27897..4a2ae720 100644 --- a/_ext/team.yaml +++ b/_ext/team.yaml @@ -93,6 +93,7 @@ team: - OHW22 Organizer - Maine - OHW23 Organizer - OHW24 Organizer - USA + - OHW25 Organizer - name: Jane Koh title: Program Specialist @@ -123,6 +124,7 @@ team: - OHW22 Organizer - Seattle - OHW23 Organizer - OHW24 Organizer - USA + - OHW25 Organizer - name: Paige Martin title: User Training Team Leader @@ -174,6 +176,7 @@ team: - OHW22 Organizer - Maine - OHW23 Organizer - OHW24 Organizer - USA + - OHW25 Organizer - name: Thomas Moore title: Ocean Data Analyst @@ -378,6 +381,7 @@ team: roles: - OHW23 Organizer - Seattle - OHW24 Organizer - USA + - OHW25 Organizer - name: Valentina Staneva title: Senior Research Scientist diff --git a/assets/images/ohw_hacking/ohw23-group-pic.jpeg b/assets/images/ohw_hacking/ohw23-group-pic.jpeg new file mode 100644 index 00000000..6f87dabe Binary files /dev/null and b/assets/images/ohw_hacking/ohw23-group-pic.jpeg differ diff --git a/index.md b/index.md index 13602560..c803838f 100644 --- a/index.md +++ b/index.md @@ -9,8 +9,7 @@ description: OceanHackWeek home :::{admonition} Stay tuned for OceanHackWeek 2025 :class: important -We are planning an in-person event at the University of Washington in Seattle later this year. Check back soon for updates! -In the meantime, [check out our past events,](about/pasthackweeks) including [OHW24](ohw24/index). Please [contact us](about/contact) if you're interested in contributing to OceanHackWeek 2025 as Organizing Committee member, [tutorial instructor or project mentor](resources/organizing/index). +We are planning an in-person event at the University of Washington Aug 18-22 in Seattle, WA USA. [Applications are open](https://docs.google.com/forms/d/1Mb72g93TySkyG_ls1Ql_wGEgynbUTI1YF_QJm4Mivv0/viewform?edit_requested=true) through July 14th. In the meantime, [check out our past events,](about/pasthackweeks) including [OHW24](ohw24/index). Please [contact us](about/contact) if you're interested in contributing to OceanHackWeek 2025 as Organizing Committee member, [tutorial instructor or project mentor](resources/organizing/index). +Yes, we welcome applications from the private sector. +Make sure to explain your motivation for participation in the application form! +We may hold a career panel discussion, +so please mention if you are interested in participating. + +### Q: I work in a non-US institution / organization / company. Can I apply? + +Yes, we welcome applications from abroad for both the in-person and virtual events. + +### Q: I was a participant in previous OceanHackWeek. Can I apply again? + +Yes, we welcome applications from previous participants, +but priority will be given to new applicants. +If you are interested in assisting as a project or tutorial helper during the hackweek, +please mention that in the application. + +### Q: Am I supposed to participate in all tutorials and presentations? + +Yes. While we understand that not all topics may be 100% relevant to you we want to maximize engagement. Note that we post the lessons and videos online later, so if you are interested in only a portion of the OceanHackWeek consider that an option rather than taking someone's spot. + +### Q: My application was not accepted, what now? + +Sadly resources are limited and we cannot accommodate all the applicants we would like. + +It is important to note that a rejected application does not mean a bad one! The reasons are: + +- The organizer tries to accommodate a good balance from novices to experts. That means a candidate may be rejected one year and accepted in another due to the different pool of applicants. Rule of thumb? Always apply again next year if possible! Also, if you believe you can contribute to the OHW as a helper instead of a student, please get in touch! We are always in need of helpers. +- Another important factor that goes into the selection of candidates is the motivation paragraph in your application. Boilerplate answers or short answers like: "I want to participate" or "It is important to me" may get lower ranking than those who read the past year materials and wrote a paragraph on how the OHW can really make a difference to them. In short: be informed, be honest, be you! +- Also, please refer to the FAQ question: "I am proficient in Matlab / other languages but have not used Python or R. It has been on my list to learn. How can I make my application be stronger?" diff --git a/ohw25/index.md b/ohw25/index.md new file mode 100644 index 00000000..62f6a1df --- /dev/null +++ b/ohw25/index.md @@ -0,0 +1,109 @@ +# OceanHackWeek 2025 (OHW25) + +OceanHackWeek 2025 (OHW25) will be held on **August 18-22, 2025** in Seattle, WA USA. The US event will take place at the [UW School of Fisheries and Aquatic Sciences](https://fish.uw.edu/). + +[Applications are open](https://docs.google.com/forms/d/1Mb72g93TySkyG_ls1Ql_wGEgynbUTI1YF_QJm4Mivv0/viewform?edit_requested=true) through July 14th. + +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)! +``` + +```{image} ../assets/images/ohw_hacking/ohw23-group-pic.jpeg +:alt: OHW23 group picture +:width: 230px +:align: left +``` + +The events will be all-day workshops (approximately 9am - 5pm). Join us for five days of hands-on tutorials, data exploration, software development, presentations, collaborative hack projects and community networking! See the [schedule here](schedule.md) -- also check out the past hackweeks for an idea of what a hackweek is like! + + + + + +## OHW25 Sponsors + +
+
+ + ```{image} ../assets/images/BigelowLabs.png + :alt: Bigelow Lab + :width: 180px + ``` + +
+
+ + ```{image} ../assets/images/apl_logo_blue.jpg + :alt: UW APL + :width: 180px + ``` + +
+
+ + ```{image} ../assets/images/logos/GMRI.png + :alt: Gulf of Maine Research Institute + :width: 180px + ``` + +
+
+ +
+
+ + ```{image} ../assets/images/logos/UW-SAFS.png + :alt: UW SAFS + :width: 130px + ``` + +
+ +
+ + ```{image} ../assets/images/ioos_logo.jpg + :alt: IOOS + :width: 180px + ``` + +
+
+ + ```{image} ../assets/images/logos/GOMO_Horizontal_Lockup_Logo_in_Blue.png + :alt: GOMO + :width: 180px + ``` + +
+
+ + ```{image} ../assets/images/logos/SOI-Logo-fullcolor-brand-V3.jpg + :alt: Schmidt Ocean Institute + :width: 180px + ``` + +
+
+ + + +```{toctree} +:maxdepth: 3 +:caption: OceanHackWeek 2025 (OHW25) +:hidden: + +schedule +Organizers +Logistics +tutorials-index/index +Projects +Information for Applicants +``` diff --git a/ohw25/logistics/getting_help.md b/ohw25/logistics/getting_help.md new file mode 100644 index 00000000..e10194af --- /dev/null +++ b/ohw25/logistics/getting_help.md @@ -0,0 +1,48 @@ +# 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. + +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. + +## Online Resources + +We provide a number of resources to help get you started on our [Resources page](https://oceanhackweek.org/resources/index.html). Please be sure to checks this page out, especially the section on preparation. + + +## Helpdesk + +We've set up the `#ohw25_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. + +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 +- **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. + +## Reporting a Code of Conduct violation + +Harassment and other [Code of Conduct violations](../../about/code-of-conduct.md) reduce the value of OceanHackWeek for everyone. If someone makes you or anyone else feel unsafe or unwelcome, please report it as soon as possible to one of the instructors. You can make a report either personally or anonymously. **Anonymous reports can be made [here](https://ohwcoc.wufoo.com/forms/z71akf608vqrgd/).** + diff --git a/ohw25/logistics/index.md b/ohw25/logistics/index.md new file mode 100644 index 00000000..e1c5b766 --- /dev/null +++ b/ohw25/logistics/index.md @@ -0,0 +1,41 @@ +# 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. + +## Time + +OceanHackWeek 2025 will take place August 18-22. The in-person participants will be engaged in OceanHackWeek throughout the day. + +**Detailed schedule is available on the [Schedule page](../schedule.md).** + + +## Channel of communication: Slack + +We will use the [OceanHackWeek Slack workspace](http://oceanhackweek.slack.com/) as the main channel of communication before, during, and after the hackweek. You should have received an invitation to join this workspace. If you haven't seen it in your inbox, check your spam folder, or email us at *info@oceanhackweek.org*. + +[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 + +- OHW JupyterHub ("The Hub"): [https://oceanhackweek.2i2c.cloud](https://oceanhackweek.2i2c.cloud) +- OHW GitHub organization: [https://github.com/oceanhackweek](https://github.com/oceanhackweek) + +## Tutorials broadcasting + +We will use Zoom to broadcast all tutorials. The Zoom link will be distributed via Slack. + +## Hack projects + +See the [Hacking at OHW25 page](../projects/index.md) for more information. + +## Getting Help + +See the [Getting Help page](getting_help.md) for guidance and links to have your questions answered or connect with organizers with concerns. + +```{toctree} +:hidden: + +Overview <./overview> +Getting Help +``` + diff --git a/ohw25/organizers.md b/ohw25/organizers.md new file mode 100644 index 00000000..7e9d8c7f --- /dev/null +++ b/ohw25/organizers.md @@ -0,0 +1,12 @@ +--- +layout: page +description: Team of OceanHackWeek 2025 organizers +--- + +# OceanHackWeek 2025 Organizers + +```{ohw-team} +:roles: "OHW25 Organizer*" +:badges: +:hide_role_badges: "OHW18 O*,OHW19 O*,OHW20 O*,OHW21 O*,OHW22 O*,OHW23 O*,OHW24 O*,*Participant*,Steering *,Tutorials,Infrastructure,Applicant Selection,Projects,Financial Planning,Website" +``` diff --git a/ohw25/projects/index.md b/ohw25/projects/index.md new file mode 100644 index 00000000..1c127110 --- /dev/null +++ b/ohw25/projects/index.md @@ -0,0 +1,29 @@ +# Hacking at OHW25 + +## 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'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 + +Check out the [projects that formed this year!](projects_thisyear.md) + +## Project overview + +```{include} ../../resources/projects.md +:start-after: "# Project Overview" +``` + + +```{toctree} +:maxdepth: 1 +:hidden: + +./projects_thisyear +``` diff --git a/ohw25/projects/projects_thisyear.md b/ohw25/projects/projects_thisyear.md new file mode 100644 index 00000000..063024f1 --- /dev/null +++ b/ohw25/projects/projects_thisyear.md @@ -0,0 +1,30 @@ +# OHW25 Projects List + +Projects from OceanHackWeek 2025. + +## Projects led by OHW25 participants + +### 1. Project Title + +- Project members: +- GitHub repository: +- [Presentation recording]() +- [Project pitch slide]() + +### 2. Project Title + +- Project members: +- GitHub repository: +- [Presentation recording]() +- [Project pitch slide]() + +### 3. Project Title + +- Project members: +- GitHub repository: +- [Presentation recording]() +- [Project pitch slide]() + + + + diff --git a/ohw25/schedule.md b/ohw25/schedule.md new file mode 100644 index 00000000..78c789d3 --- /dev/null +++ b/ohw25/schedule.md @@ -0,0 +1,18 @@ +# Schedule + + +**OceanHackWeek 2025 will take place on:** + +- August 18-22 in Seattle, Washington, USA. + + + + +## US in-person schedule + + \ No newline at end of file diff --git a/ohw25/tutorials-index/index.md b/ohw25/tutorials-index/index.md new file mode 100644 index 00000000..743af47f --- /dev/null +++ b/ohw25/tutorials-index/index.md @@ -0,0 +1,48 @@ +# Tutorials + +We are pleased to present a number of tutorials during the week. These tutorials provide a look into the work that your colleagues pursue using coding tools. The software for most tutorials can be downloaded using the tools described in our [Tutorials Getting Started page](../tutorials_getting_started.md). Please check the [schedule](../schedule.md) for the times of these presentations. + +```{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)! +``` + +## Main tutorials + + + +The following tutorials will be presented live during the **US sessions**, and will be recorded for later review. + +### Monday, August 18th + + +### Tuesday, August 19th + + +### Wednesday, August 28th + + +### Thursday, August 29th + + +## Lectures and Discussions + +Finally, each year we offer brief sessions on non-coding aspects of computational oceanography; this year we are pleased to offer the following. + + + +```{toctree} +:maxdepth: 1 +:hidden: + +../tutorials_getting_started +../tutorials/01-Tue/Data_access_methods_Python.ipynb +machine-learning.md +../tutorials/02-Wed/ai_assisted_programming_ohw.ipynb +../tutorials/02-Wed/xarray-in-45-min.ipynb +../tutorials/03-Thu/OHW_omics_lesson.ipynb +``` diff --git a/ohw25/tutorials_getting_started.md b/ohw25/tutorials_getting_started.md new file mode 100644 index 00000000..86a8dbb3 --- /dev/null +++ b/ohw25/tutorials_getting_started.md @@ -0,0 +1,37 @@ +# Getting started on tutorials + +## Introduction + +Tutorials will be run live on the [OceanHackWeek JupyterHub ("The Hub"), https://oceanhackweek.2i2c.cloud](https://oceanhackweek.2i2c.cloud) in your browser either as Jupyter notebooks or as scripts and notebooks in RStudio. The instructor and all participants can be running their own copies of the tutorial in their Hub account, with files cloned from the OHW source in GitHub. + +Below are instructions for getting the tutorials started on the the Hub in your browser, and updating the tutorials files with the latest version from the GitHub tutorials repository, [https://github.com/oceanhackweek/ohw-tutorials](https://github.com/oceanhackweek/ohw-tutorials). + +The schedule of tutorials is available [here](../../ohw24/schedule.md), and links to tutorial materials and some background resources will be available there as well. + +## How do I get the tutorial repository into the Hub? + +For the tutorials, we recommend the use of [nbgitpuller](https://jupyterhub.github.io/nbgitpuller/) to clone and pull the tutorials repository, or update the clone you already have. Use the magical nbgitpuller link below to accomplish this clone or update. + +```{admonition} Pull tutorial repo via the magic of nbgitpuller + +The nbgitpuller link is magical, but it can't detect which profile you are currently running. Either should update the (same) tutorial repo, but it may error if you use the Python link if you are actively using the R profile, or the other way around. + +::::{tab-set} + +:::{tab-item} Python + +[Pull tutorial repo for the Python profile](https://oceanhackweek.2i2c.cloud/hub/user-redirect/git-pull?repo=https%3A%2F%2Fgithub.com%2Foceanhackweek%2Fohw-tutorials&urlpath=lab%2Ftree%2Fohw-tutorials%2F&branch=OHW24) + +::: + +:::{tab-item} R + +[Pull tutorial repo for the R profile](https://oceanhackweek.2i2c.cloud/hub/user-redirect/git-pull?repo=https%3A%2F%2Fgithub.com%2Foceanhackweek%2Fohw-tutorials&urlpath=rstudio%2F&branch=OHW24) + +::: + +:::: + +``` + +See this [extended discussion](../resources/prep/jupyterhub.md#how-do-i-get-the-tutorial-repository) for more details about `nbgitpuller` and the alternative approach relying on `git` commands and `GitHub` workflows.