You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bootstrap all the new pages for OHW24 based on OHW23 pages.
I made some simple content updates (eg, replace 23 with 24) and cleanups, added some strikethrough formatting for text that probably should be deleted, and added admonitions to highlight other changes likely needed
Copy file name to clipboardExpand all lines: ohw24/index.md
+24-3Lines changed: 24 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,13 @@
1
1
# OceanHackWeek 2024 (OHW24)
2
2
3
-
OceanHackWeek 2024 (OHW24) will be held on **August 26-30, 2024** as two in-person events, in East Boothbay, Maine, US and in Sydney, Australia. The US in-person event will take place at the [Bigelow Laboratory for Ocean Sciences](https://www.bigelow.org).
3
+
OceanHackWeek 2024 (OHW24) will be held on **August 26-30, 2024** as two in-person events, in East Boothbay, Maine, US and in Sydney, Australia. The US event will take place at the [Bigelow Laboratory for Ocean Sciences](https://www.bigelow.org).
4
+
5
+
The OceanHackWeek program consists of hands-on tutorials, visual presentations, and collaborative hack projects throughout a 5-day period.
6
+
7
+
```{admonition} Technical preparations and background for OceanHackWeek!
8
+
- Please review the ["Preparation" materials](../resources/prep/index.md) covering basic topics like `Git`, `GitHub`, `conda` package management and the OHW `JupyterHub`
9
+
- 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)!
@@ -10,7 +17,17 @@ OceanHackWeek 2024 (OHW24) will be held on **August 26-30, 2024** as two in-pers
10
17
11
18
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!
12
19
13
-
See the [OHW23 program](https://oceanhackweek.org/ohw23/) (a hybrid event) to get a better sense of the usual activities and how they're organized.
20
+
21
+
## In-person event in Maine
22
+
23
+
See the [schedules here](schedule.md).
24
+
25
+
```{admonition} UPDATE THIS INFORMATION TO OHW24 CONTEXT!!
26
+
:class: important
27
+
- See the [ohw23 index page](../ohw23) as a template to content for this page, though the parts about the hybrid nature don't apply
28
+
- Will you list the Australia event here, too?
29
+
- Remove the admonition box below if applications for volunteers have closed
30
+
```
14
31
15
32
16
33
@@ -42,7 +59,7 @@ We are still looking for volunteers to help with OceanHackWeek 2024! Please [app
We know how overwhelming all of this information can be. Here is some for asking questions and figuring out where to turn for help.
4
+
5
+
You can ask anything on the Slack `#ohw24_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.
6
+
7
+
## Online Resources
8
+
9
+
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.
10
+
11
+
12
+
## Helpdesk
13
+
14
+
We've set up the `#ohw24_helpdesk` Slack channel to ask technical questions (or other types of questions, if you'd like).
15
+
16
+
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.
17
+
18
+
You are also welcome to direct message the helpers if you don't feel comfortable asking questions publicly.
19
+
20
+
### Slack help groups
21
+
22
+
-`@help-infrastructure` - For issues regarding the JupyterHub, Slack, Github, and Zoom.
23
+
-`@help-projects` - For help with managing projects, for instance asking how to set up a new repo, or organize meetings.
24
+
-`@help-python` - Questions about Python programming.
25
+
-`@help-r` - Questions about R programming.
26
+
-`@help-ml` - Questions about machine learning.
27
+
-`@help-git` - Questions about git.
28
+
-`@help-tutorials` - For help with tutorial logistics, like cloning the notebooks.
29
+
-`@help-website` - If there are any issues with the website tag us to take a look.
30
+
31
+
## During tutorials
32
+
33
+
Tune in on Slack for continuous Q&A!
34
+
35
+
- Ask questions on Slack! Use the `#ohw24-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
36
+
-**Vote up** questions from others to help the moderators prioritize which questions to ask the speaker during tutorials.
37
+
- 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.
38
+
- Zoom Chat will **not** be available. Ask on Slack!
39
+
- 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.
40
+
41
+
## Projects
42
+
43
+
See the [Hacking at OHW24 page](../projects/index.md) for more information. Feel free to post a question on the `#ohw24_project` channel, too.
44
+
45
+
## Reporting a Code of Conduct violation
46
+
47
+
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/).**
Some of you will participate in person in East Boothbay and others in Sydney. ~~and others will participate virtually from time zones all over the world. Each of these gathering styles has strengths and weaknesses.~~ We are committed to providing an engaging and full experience for everyone and will strive to facilitate cross communication and collaboration across all participants.
4
+
5
+
## Time
6
+
7
+
OceanHackWeek 2024 will take place:
8
+
9
+
- August 26-30 for ~~the virtual event and~~ the in-person event in East Boothbay, Maine,, US
10
+
- August 8-12 for the in-person event in Western Australia (**DO YOU INTEND TO LIST THE TWO EVENTS HERE?**)
11
+
12
+
In-person participants will be engaged in OceanHackWeek throughout the day. ~~The virtual event will take place in a 3-hour daily block of formal, live activities, 09:00am - 12:00pm PDT / 16:00 - 19:00 UTC.~~
13
+
14
+
**Detailed schedules are available on the [Schedule page](../schedule.md).**
15
+
16
+
17
+
## Channel of communication: Slack
18
+
19
+
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*.
20
+
21
+
[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.
22
+
23
+
## OHW JupyterHub ("The Hub") and GitHub
24
+
25
+
- OHW JupyterHub ("The Hub"): [https://oceanhackweek.2i2c.cloud](https://oceanhackweek.2i2c.cloud)
We encourage project ideas from participants! Feel free to discuss existing or new project ideas **#ohw24_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 [Google Jamboard](https://jamboard.google.com/d/1lOgVwnqQLvNRPAOEVEGnWXm8FSTuPYQWbteptKrslTM/viewer?f=0). Later the group needs to create 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), create a project Slack channel that starts with `ohw24_proj_` (say, `ohw24_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).
6
+
7
+
We've scheduled part of Day 1 and the early part of Day 2 for project ideation. After that, time not allocated to shared tutorials and discussions may be devoted to working on the projects - hacking!
8
+
9
+
Please look over the information below for guidance about projects, how to get started and the motivations for working on projects.
10
+
11
+
## OHW24 projects list
12
+
13
+
Check out the [projects that formed this year!](projects_thisyear.md)
The list of projects will be fleshed out here as they it comes together. Here is an example of ideal (if not always fully possible) project information, from OHW23:
6
+
7
+
### 1. Marine species distribution modeling tutorial: sea turtles
8
+
9
+
- Project members: Catherine Courtier, Mackenzie Fiss, Denisse Fierro Arcos, Paulo Freire, Jade Hong, Caitlin O’Brien, Mary Solokas, Laura Tsang, Eli Holmes, Tylar Murray, Ben Tupper
```{admonition} UPDATE THIS INFORMATION TO OHW24 CONTEXT!!
4
+
- Will you try to include the Australian schedule here?
5
+
- A link to convert timezones may not be useful if you're not supporting virtual participation
6
+
- Update the link to the OHW24 US schedule Google Sheet, after "publishing" it (Alex or Emilio can help with that)
7
+
```
8
+
9
+
**OceanHackWeek 2024 will take place on:**
10
+
11
+
- August 26-30 for the the in-person event in East Boothbay, Maine, US
12
+
-~~August 8-12 for the in-person event in Western Australia~~
13
+
14
+
**All times below are shown in "EDT", Pacific Daylight savings Time (UTC-5).** You can [use this link to convert](https://www.timeanddate.com/worldclock/converter.html?iso=20230807T160000&p1=1440&p2=234&p3=196&p4=16&p5=179) to your own local times.
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.
4
+
5
+
```{admonition} Technical preparations and background for OceanHackWeek!
6
+
- Please review the ["Preparation" materials](../../resources/prep/index.md) covering basic topics like `Git`, `GitHub`, `conda` package management and the OHW `JupyterHub`
7
+
- 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)!
8
+
```
9
+
10
+
## Main tutorials
11
+
12
+
```{admonition} UPDATE THIS INFORMATION TO OHW24 CONTEXT!!
13
+
:class: important
14
+
- See the [ohw23 tutorials index page](../../ohw23/tutorials-index) as a template to content for this page.
15
+
- Make sure to update the links to tutorials in `ohw-tutorials` repo in `toctree`, and see [https://github.com/oceanhackweek/oceanhackweek.github.io/issues/263](https://github.com/oceanhackweek/oceanhackweek.github.io/issues/263) to understand the somewhat complex, git submodules set up that links to tutorials in that repo
16
+
```
17
+
18
+
## Lectures and Discussions
19
+
20
+
Finally, each year we offer brief sessions on non-coding aspects of computational oceanography; this year we are pleased to offer two.
-[Alex Kerney](https://github.com/abkfenris) - [**Stresses in the geosciences**](https://github.com/oceanhackweek/ohw-tutorials/tree/OHW23/02-Wed/README.md)
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.
6
+
7
+
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).
8
+
9
+
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.
10
+
11
+
## How do I get the tutorial repository into the Hub?
12
+
13
+
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.
14
+
15
+
```{admonition} Pull tutorial repo via the magic of nbgitpuller
16
+
17
+
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.
18
+
19
+
::::{tab-set}
20
+
21
+
:::{tab-item} Python
22
+
23
+
[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)
24
+
25
+
:::
26
+
27
+
:::{tab-item} R
28
+
29
+
[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)
30
+
31
+
:::
32
+
33
+
::::
34
+
35
+
```
36
+
37
+
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.
0 commit comments