From e6141e12880fb5c33d31358d94f2bf09cc9b1d03 Mon Sep 17 00:00:00 2001 From: Emilio Mayorga Date: Tue, 25 Jul 2023 10:12:23 -0700 Subject: [PATCH 01/12] Reorganize top bar menu --- conf.py | 2 +- index.md | 9 ++------- 2 files changed, 3 insertions(+), 8 deletions(-) diff --git a/conf.py b/conf.py index 62c14f74..643f89d6 100644 --- a/conf.py +++ b/conf.py @@ -50,7 +50,7 @@ # If true, "(C) Copyright ..." is shown in the HTML footer. Default is True. html_show_copyright = True -copyright = "2022, OceanHackWeek" +copyright = "2023, OceanHackWeek" # -- HTML Config ------------------------------------------------- diff --git a/index.md b/index.md index 32a41a1a..14697456 100644 --- a/index.md +++ b/index.md @@ -146,19 +146,14 @@ Thanks to our sponsors that have made OceanHackWeek possible over the last sever - ```{toctree} :maxdepth: 2 :hidden: about/index.md -about/pasthackweeks.md OceanHackWeek 2023 -OceanHackWeek 2022 +resources/index.md +about/pasthackweeks.md % posts ``` From 64932fc18079b60a4ff1aa108847c6c5b63c0123 Mon Sep 17 00:00:00 2001 From: Emilio Mayorga Date: Tue, 25 Jul 2023 10:44:15 -0700 Subject: [PATCH 02/12] Start updating references and intro to Resources materials --- ohw22/index.md | 19 +------------------ resources/index.md | 24 ++++++++++++++++++------ resources/logistics/coffeebreaks.md | 7 ------- resources/prep/index.md | 3 ++- 4 files changed, 21 insertions(+), 32 deletions(-) delete mode 100644 resources/logistics/coffeebreaks.md diff --git a/ohw22/index.md b/ohw22/index.md index 1df733ef..c9db8baa 100644 --- a/ohw22/index.md +++ b/ohw22/index.md @@ -12,7 +12,7 @@ OceanHackWeek 2022 will happen from **August 15-19, 2022**. The workshop will ta The OceanHackWeek program consists of hands-on tutorials, visual presentations, and collaborative hack projects throughout a 5-day period. Participants can apply for being in one of the regional satellites or the virtual global event. Regional satellite events are connected closely with the virtual global event, while providing additional collaboration and networking opportunities on a regional basis. -See the [OHW21 program](https://oceanhackweek.github.io/ohw-resources) (a hybrid event) to get a better sense of the usual activities and how they're organized. +See the [OHW21 program](https://oceanhackweek.org/ohw-resources) (a hybrid event) to get a better sense of the usual activities and how they're organized. :::{admonition} Join OHW22 global virtual tutorials! :class: note @@ -132,22 +132,5 @@ Global Virtual Event Regional Satellite Events Organizers tutorials-index/index -``` - -```{toctree} -:maxdepth: 2 -:caption: OHW22 Resources -:hidden: - -Logistics <../resources/logistics/index> -Preparation <../resources/prep/index> -Projects <../resources/projects/index> -``` - -```{toctree} -:caption: OHW22 Other information -:hidden: - Information for Applicants -../resources/organizing/index ``` diff --git a/resources/index.md b/resources/index.md index 9a057189..a15723ba 100644 --- a/resources/index.md +++ b/resources/index.md @@ -1,15 +1,27 @@ # Resources -To make sure that OHW22 will be a welcoming environment for everyone, please read our [Code of Conduct](/about/code-of-conduct.md) carefully as part of your preparation. We expect all participants to adhere to the Code of Conduct in all interactions throughout the hackweek. - -## Schedules +```{attention} +**This page should be rewritten entirely!** +``` -There are a few different schedules and participants may need to pay attention to multiple based on if they are part of the global event, or at a satellite. -Go to [the Schedule page for details](schedule.md). +To make sure that OHW22 will be a welcoming environment for everyone, please read our [Code of Conduct](/about/code-of-conduct.md) carefully as part of your preparation. We expect all participants to adhere to the Code of Conduct in all interactions throughout the hackweek. ## Preparation We will use a [JupyterHub](https://jupyter.org/hub)-based online environment for all OceanHackWeek computational activities, including tutorials; this environment supports both Python and R. You will need a robust internet connection and a capable laptop or desktop computer. - We will use Slack, Zoom and GitHub as our primary communication and content delivery platforms. The week before OceanHackWeek you will receive via email an invitation to join the OceanHackWeek GitHub organization, [https://github.com/oceanhackweek/](https://github.com/oceanhackweek/) if you have not received it already, along with Slack invites and Zoom connection info. + +## Organizing OceanHackWeek + +PLACEHOLDER. SEE THE Organizing OHW section + + +```{toctree} +:maxdepth: 2 +:caption: OHW Resources +:hidden: + +Preparation +organizing/index.md +``` diff --git a/resources/logistics/coffeebreaks.md b/resources/logistics/coffeebreaks.md deleted file mode 100644 index 97108adc..00000000 --- a/resources/logistics/coffeebreaks.md +++ /dev/null @@ -1,7 +0,0 @@ -# OHW21 Global Rolling Social/Coffee Breaks - -After we get this hackweek kicked-off and project teams formed we will start inviting you to come hangout and meet others across the globe in [our virtual break space](https://www.wonder.me/r?id=b9a45324-db39-4434-b84f-f6e1ee3aeb76). Breaks will be announced every 3-hours and will last for 15-minutes, but of course you can stay longer. In fact, the space is yours to use for the entire hackweek for any purposes including meeting with your project team. The space is open starting now, July 30 until soon after OHW21 ends. We will be using the web-based platform from [Wonder.me](https://www.wonder.me). The supported browsers are Google Chrome & Microsoft Edge, & Firefox works equally as well. Sometimes Linux has issues, but we have seen it work. You may need to fiddle to get the microphone or camera to work if you have multiple ones connected. It will not work on devices like ipads/smart phone/etc. Alas, not perfect, but kinda fun. - -When you [click on the Wonder Room link](https://www.wonder.me/r?id=b9a45324-db39-4434-b84f-f6e1ee3aeb76) you will be asked for permission to use your camera and microphone and to take a selfie with your computer to use for your avatar. Don’t over think the picture, it’s less scary walking up to someone with a picture vs initials. You will be dropped in the space where you can roam about freely between people/pods. As soon as your avatar is near another avatar, your audio/visuals will activate, and you will be able to see and hear only the people close by. It will deactivate when you move apart. Point and click your mouse to navigate and bump into others. More information about our global breaks will come when we get them started but for now feel free to test and checkout the space. Right now, the space is a coffee shop in Brooklyn NY. - -We will try to have at least one OHW21 organizer or helper serving in the good host role for each coffee break, making sure anyone coming into the Wonder Room can move around, feels welcome, and perhaps introduce them to others already there. This is also a good place for participants to come to get questions answered about the hackweek. diff --git a/resources/prep/index.md b/resources/prep/index.md index 5379fd8f..e4011861 100644 --- a/resources/prep/index.md +++ b/resources/prep/index.md @@ -1,9 +1,10 @@ # Preparations +Technical materials as preparation for the OceanHackWeek event. ```{toctree} :maxdepth: 2 -:caption: OceanHackWeek 2022 (OHW22) +:caption: Table of Content Git github From acf0b196d25fc17992a29b925ac4f5823f4475fc Mon Sep 17 00:00:00 2001 From: Emilio Mayorga Date: Tue, 25 Jul 2023 11:06:21 -0700 Subject: [PATCH 03/12] Move/copy logistics and projects to both ohw23 and ohw22 --- ohw22/index.md | 2 + ohw22/logistics/getting_help.md | 41 ++++++++++++ ohw22/logistics/index.md | 42 ++++++++++++ ohw22/projects/guidelines.md | 65 +++++++++++++++++++ ohw22/projects/index.md | 35 ++++++++++ ohw22/projects/steps.md | 47 ++++++++++++++ ohw23/index.md | 4 ++ ohw23/logistics/getting_help.md | 41 ++++++++++++ ohw23/logistics/index.md | 42 ++++++++++++ ohw23/projects/guidelines.md | 65 +++++++++++++++++++ ohw23/projects/index.md | 31 +++++++++ ohw23/projects/steps.md | 47 ++++++++++++++ ohw23/schedule.md | 26 ++++++++ .../tutorials-index/data-access-in-python.md | 10 +++ ohw23/tutorials-index/data-access-in-r.md | 7 ++ ohw23/tutorials-index/data-vis-in-python.md | 13 ++++ ohw23/tutorials-index/espanol/index.md | 6 ++ .../espanol/python-cientifico.md | 8 +++ ohw23/tutorials-index/index.md | 14 ++++ .../machine-learning-applications.md | 7 ++ 20 files changed, 553 insertions(+) create mode 100644 ohw22/logistics/getting_help.md create mode 100644 ohw22/logistics/index.md create mode 100644 ohw22/projects/guidelines.md create mode 100644 ohw22/projects/index.md create mode 100644 ohw22/projects/steps.md create mode 100644 ohw23/logistics/getting_help.md create mode 100644 ohw23/logistics/index.md create mode 100644 ohw23/projects/guidelines.md create mode 100644 ohw23/projects/index.md create mode 100644 ohw23/projects/steps.md create mode 100644 ohw23/schedule.md create mode 100644 ohw23/tutorials-index/data-access-in-python.md create mode 100644 ohw23/tutorials-index/data-access-in-r.md create mode 100644 ohw23/tutorials-index/data-vis-in-python.md create mode 100644 ohw23/tutorials-index/espanol/index.md create mode 100644 ohw23/tutorials-index/espanol/python-cientifico.md create mode 100644 ohw23/tutorials-index/index.md create mode 100644 ohw23/tutorials-index/machine-learning-applications.md diff --git a/ohw22/index.md b/ohw22/index.md index c9db8baa..0dcbd499 100644 --- a/ohw22/index.md +++ b/ohw22/index.md @@ -131,6 +131,8 @@ schedule Global Virtual Event Regional Satellite Events Organizers +Logistics tutorials-index/index +Projects Information for Applicants ``` diff --git a/ohw22/logistics/getting_help.md b/ohw22/logistics/getting_help.md new file mode 100644 index 00000000..c03bb79d --- /dev/null +++ b/ohw22/logistics/getting_help.md @@ -0,0 +1,41 @@ +# 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 `#ohw22-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. + +## Helpdesk + +We've set up the `#ohw22-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 + +- Ask questions on Slack! Use the `#ohw22-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 [Projects Getting Started page](../projects/steps.md). Feel free to post a question on the `#ohw22_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://oceanhackweek.wufoo.com/forms/zep2ybt1swlulc/).** + diff --git a/ohw22/logistics/index.md b/ohw22/logistics/index.md new file mode 100644 index 00000000..53bcc7a0 --- /dev/null +++ b/ohw22/logistics/index.md @@ -0,0 +1,42 @@ +# Logistics Overview + +Some of you will participate in person at various satellite events, and others will participate virtually from time zones all over the world. As we have learned throughout the pandemic, 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. + +## Time + +OceanHackWeek 2022 will take place August 15-19. + +**In-person participants** will gather as for times as directed by the satellite organizers. While **virtual participants** may choose to engage primarily with this group and schedule via Zoom and Slack, we strongly encourage you to join the program designed specifically as a virtual event. The virtual event will be split into two schedules and groups based on the distribution of participant time zones, in a 3-hour daily block of formal, live activities. The **larger virtual event** will take place 11:00am - 2:00pm PDT / 18:00 - 21:00 UTC. + +Detailed schedules are available [Schedule page](../../ohw22/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 *oceanhkw@uw.edu*. + +[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 [Project overview](../projects/index.md) and [Hacking at OHW22](../projects/steps.md) for more info. + +## 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/ohw22/projects/guidelines.md b/ohw22/projects/guidelines.md new file mode 100644 index 00000000..81a8c436 --- /dev/null +++ b/ohw22/projects/guidelines.md @@ -0,0 +1,65 @@ + + + + +# Project Guidelines + +## Project Template +Each project requires a brief project summary in the README.md of each GitHub project folder. Below is a template for the project summary. + +### Project title + +Brief title describing the proposed work. + +### Collaborators on this project + +List all participants on the project. + +### The problem + +What oceanographic data science problem are you going to explore? Try to focus on the data science/methodology problem first, followed by the location-specific oceanographic example afterwards. The project is likely more engaging for fellow hackers if it is centered around common data science problems. For example, the project could be to develop a workflow in Python to analyze CTD time series from multiple data sources, instead of emphasizing and focusing only on temperature variations in one very specific part of the ocean. + +### Application example + +Here is where you follow up with a location-specific example of where the data science methodology applies and list example datasets (size, format, how to access) that could be used for this exploration. + +### Specific tasks + +List the specific tasks you want to accomplish. + +### Existing methods + +How would you or others traditionally try to address this problem? + +### Proposed methods/tools + +Building from what you learn at Oceanhackweek, what new approaches would you like to try to implement? + +### Background reading + +Optional: links to manuscripts or technical documents for more in-depth analysis. + + + +## Project Ideas +* Developing tutorials for using NASA data on the cloud. +* Working on an efficient open source matchup tutorial for satellite orbital data and in situ point or trajectory data. +* Developing an OSS algorithm development toolbox in Python to deal with a 400GB AMSR brightness temperature - in situ matchup database. + + + +## Project Data Storage + +If your group needs to store data for project use during Oceanhackweek, depending on the volume, below is what we recommend: +- Whenever possible, public datasets like OOI, ARGO, satellite, etc. should be accessed remotely in the Jupyter notebook through standard protocols like OPeNDAP or other programmatic approaches. +- **Data that are <1 MB**: can be included directly in the project Github repository. +- **Data that are <10 GB**: can be stored in your home space on ocean.pangeo.io. When you are accessing data from the internet, it is often useful to have a cell in the notebook that downloads such data into your home space if those data are not there, otherwise do nothing if they are already there. You can also upload a local dataset through the pangeo interface. You can upload only one file as of now, so if you have multiple files you will need to zip them and unzip them later from the terminal. These are two ways to fetch and store larger datasets locally if they are not enormous. +- **Data that are >10 GB**: are best stored in a cloud-optimized format. If you don't already have the data on the cloud, please talk to the instructors about your needs and how you anticipate using the data. We can help you prepare and upload the data to [cloud object storage](https://en.wikipedia.org/wiki/Cloud_storage) with Oceanhackweek support. +- Questions? Feel free post on Slack #project channel or email [oceanhkw@uw.edu](mailto:oceanhkw@uw.edu). diff --git a/ohw22/projects/index.md b/ohw22/projects/index.md new file mode 100644 index 00000000..ff2187f3 --- /dev/null +++ b/ohw22/projects/index.md @@ -0,0 +1,35 @@ +# Project Overview + +Collaborative projects are a key component of OceanHackWeek, in which you get to interact with others closely and apply new skills to make something exciting happen: it can be creating tools to streamline access of a particular data source, visualizing some high density data interactively, testing existing models with new data sources, or anything else you may want to do at the intersection of oceanography and data science. + +## What is a Hack? + +A "hack" is a small project that aims to solve a specific problem using computational tools. + +Examples of hacks include: + +* Build a working demo of a new or modified algorithm +* Outline of a larger project, with some key features scoped +* Visualization of an old dataset in a new manner +* Modify an algorithm and apply it to a new dataset +* Combine two pre-existing pieces of code to perform some new function +* Create a tool to apply to work with existing code, datasets +* Transform code from one language to another to use with other tools +* Update old code to run faster, on new machines, and/or more efficiently +* Extend an existing project with an additional feature +* Simplify code to be more maintainable, aka "paying technical debt" + + + +## Why hack at OceanHackWeek? + +Increasingly, research and software development are conducted by groups of people with diverse skills and backgrounds. We believe this collaborative work leads to more innovative solutions to complex problems. At OceanHackWeek, our goal is to explore with you some of the skills needed to navigate technical and social challenges of working in these kinds of collaborative settings. We believe the best way to do so is to provide opportunities for you to gain hands-on experience in working together with others on a well-defined problem related to ocean sciences. + + +```{toctree} +:maxdepth: 2 +:caption: OceanHackWeek 2022 (OHW22) +:hidden: + +steps.md +``` diff --git a/ohw22/projects/steps.md b/ohw22/projects/steps.md new file mode 100644 index 00000000..c519b12d --- /dev/null +++ b/ohw22/projects/steps.md @@ -0,0 +1,47 @@ +# Hacking at OHW22 + +## How will the projects be conducted? + +We have put together a [few questions](https://github.com/oceanhackweek/discussions/discussions/categories/ohw22-project-planning) that can help you propose a project in [GitHub discussions](https://github.com/oceanhackweek/discussions/discussions/categories/ohw22-project-planning). + +On Monday August 15th we will have a brief “project setup” session for an overview of all projects already proposed up to that point, and give another opportunity to pitch new ideas that may be formed throughout the day. Project proposals must be submitted by the end of this day (Day 1). Each satellite may have its own, specific deadline time, so please connect with your satellite or the global event for details. + +## Tips for getting started + +* Potentially choose something that you've been interested but haven't had the time or skills to do before, or something you can continue to work on post OceanHackWeek! +* Hacking is a community activity! It's okay to choose projects that you can't accomplish alone as other people will be there to help you, both at OceanHackWeek and outside of it! +* Help your group member: you might be the person they need to solve their problem, and vice versa. +* When discussing, pitch your explanation to the least experienced hacker in the group, and you'll end up better understanding what you're trying to do, or need to revise your idea. +* You can mix programming languages as needed in order to get started, but do check in with your project mentors and group members to make sure your efforts are straightforward to be absorbed into the project. + + + + + + + + + diff --git a/ohw23/index.md b/ohw23/index.md index 3b6b16e4..9e663a51 100644 --- a/ohw23/index.md +++ b/ohw23/index.md @@ -136,6 +136,10 @@ The event will be all day (approximately 8am - 5pm AWST / UTC+8) for the 5-day p :caption: OceanHackWeek 2023 (OHW23) :hidden: +schedule Organizers +Logistics +tutorials-index/index +Projects Information for Applicants ``` diff --git a/ohw23/logistics/getting_help.md b/ohw23/logistics/getting_help.md new file mode 100644 index 00000000..c03bb79d --- /dev/null +++ b/ohw23/logistics/getting_help.md @@ -0,0 +1,41 @@ +# 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 `#ohw22-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. + +## Helpdesk + +We've set up the `#ohw22-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 + +- Ask questions on Slack! Use the `#ohw22-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 [Projects Getting Started page](../projects/steps.md). Feel free to post a question on the `#ohw22_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://oceanhackweek.wufoo.com/forms/zep2ybt1swlulc/).** + diff --git a/ohw23/logistics/index.md b/ohw23/logistics/index.md new file mode 100644 index 00000000..53bcc7a0 --- /dev/null +++ b/ohw23/logistics/index.md @@ -0,0 +1,42 @@ +# Logistics Overview + +Some of you will participate in person at various satellite events, and others will participate virtually from time zones all over the world. As we have learned throughout the pandemic, 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. + +## Time + +OceanHackWeek 2022 will take place August 15-19. + +**In-person participants** will gather as for times as directed by the satellite organizers. While **virtual participants** may choose to engage primarily with this group and schedule via Zoom and Slack, we strongly encourage you to join the program designed specifically as a virtual event. The virtual event will be split into two schedules and groups based on the distribution of participant time zones, in a 3-hour daily block of formal, live activities. The **larger virtual event** will take place 11:00am - 2:00pm PDT / 18:00 - 21:00 UTC. + +Detailed schedules are available [Schedule page](../../ohw22/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 *oceanhkw@uw.edu*. + +[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 [Project overview](../projects/index.md) and [Hacking at OHW22](../projects/steps.md) for more info. + +## 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/ohw23/projects/guidelines.md b/ohw23/projects/guidelines.md new file mode 100644 index 00000000..81a8c436 --- /dev/null +++ b/ohw23/projects/guidelines.md @@ -0,0 +1,65 @@ + + + + +# Project Guidelines + +## Project Template +Each project requires a brief project summary in the README.md of each GitHub project folder. Below is a template for the project summary. + +### Project title + +Brief title describing the proposed work. + +### Collaborators on this project + +List all participants on the project. + +### The problem + +What oceanographic data science problem are you going to explore? Try to focus on the data science/methodology problem first, followed by the location-specific oceanographic example afterwards. The project is likely more engaging for fellow hackers if it is centered around common data science problems. For example, the project could be to develop a workflow in Python to analyze CTD time series from multiple data sources, instead of emphasizing and focusing only on temperature variations in one very specific part of the ocean. + +### Application example + +Here is where you follow up with a location-specific example of where the data science methodology applies and list example datasets (size, format, how to access) that could be used for this exploration. + +### Specific tasks + +List the specific tasks you want to accomplish. + +### Existing methods + +How would you or others traditionally try to address this problem? + +### Proposed methods/tools + +Building from what you learn at Oceanhackweek, what new approaches would you like to try to implement? + +### Background reading + +Optional: links to manuscripts or technical documents for more in-depth analysis. + + + +## Project Ideas +* Developing tutorials for using NASA data on the cloud. +* Working on an efficient open source matchup tutorial for satellite orbital data and in situ point or trajectory data. +* Developing an OSS algorithm development toolbox in Python to deal with a 400GB AMSR brightness temperature - in situ matchup database. + + + +## Project Data Storage + +If your group needs to store data for project use during Oceanhackweek, depending on the volume, below is what we recommend: +- Whenever possible, public datasets like OOI, ARGO, satellite, etc. should be accessed remotely in the Jupyter notebook through standard protocols like OPeNDAP or other programmatic approaches. +- **Data that are <1 MB**: can be included directly in the project Github repository. +- **Data that are <10 GB**: can be stored in your home space on ocean.pangeo.io. When you are accessing data from the internet, it is often useful to have a cell in the notebook that downloads such data into your home space if those data are not there, otherwise do nothing if they are already there. You can also upload a local dataset through the pangeo interface. You can upload only one file as of now, so if you have multiple files you will need to zip them and unzip them later from the terminal. These are two ways to fetch and store larger datasets locally if they are not enormous. +- **Data that are >10 GB**: are best stored in a cloud-optimized format. If you don't already have the data on the cloud, please talk to the instructors about your needs and how you anticipate using the data. We can help you prepare and upload the data to [cloud object storage](https://en.wikipedia.org/wiki/Cloud_storage) with Oceanhackweek support. +- Questions? Feel free post on Slack #project channel or email [oceanhkw@uw.edu](mailto:oceanhkw@uw.edu). diff --git a/ohw23/projects/index.md b/ohw23/projects/index.md new file mode 100644 index 00000000..5d8a3e95 --- /dev/null +++ b/ohw23/projects/index.md @@ -0,0 +1,31 @@ +# Project Overview + +Collaborative projects are a key component of OceanHackWeek, in which you get to interact with others closely and apply new skills to make something exciting happen: it can be creating tools to streamline access of a particular data source, visualizing some high density data interactively, testing existing models with new data sources, or anything else you may want to do at the intersection of oceanography and data science. + +## What is a Hack? + +A "hack" is a small project that aims to solve a specific problem using computational tools. + +Examples of hacks include: + +* Build a working demo of a new or modified algorithm +* Outline of a larger project, with some key features scoped +* Visualization of an old dataset in a new manner +* Modify an algorithm and apply it to a new dataset +* Combine two pre-existing pieces of code to perform some new function +* Create a tool to apply to work with existing code, datasets +* Transform code from one language to another to use with other tools +* Update old code to run faster, on new machines, and/or more efficiently +* Extend an existing project with an additional feature +* Simplify code to be more maintainable, aka "paying technical debt" + +## Why hack at OceanHackWeek? + +Increasingly, research and software development are conducted by groups of people with diverse skills and backgrounds. We believe this collaborative work leads to more innovative solutions to complex problems. At OceanHackWeek, our goal is to explore with you some of the skills needed to navigate technical and social challenges of working in these kinds of collaborative settings. We believe the best way to do so is to provide opportunities for you to gain hands-on experience in working together with others on a well-defined problem related to ocean sciences. + + +```{toctree} +:hidden: + +steps.md +``` diff --git a/ohw23/projects/steps.md b/ohw23/projects/steps.md new file mode 100644 index 00000000..7284f811 --- /dev/null +++ b/ohw23/projects/steps.md @@ -0,0 +1,47 @@ +# Hacking at OHW23 + +## How will the projects be conducted? + +We have put together a [few questions](https://github.com/oceanhackweek/discussions/discussions/categories/ohw22-project-planning) that can help you propose a project in [GitHub discussions](https://github.com/oceanhackweek/discussions/discussions/categories/ohw22-project-planning). + +On Monday August 15th we will have a brief “project setup” session for an overview of all projects already proposed up to that point, and give another opportunity to pitch new ideas that may be formed throughout the day. Project proposals must be submitted by the end of this day (Day 1). Each satellite may have its own, specific deadline time, so please connect with your satellite or the global event for details. + +## Tips for getting started + +* Potentially choose something that you've been interested but haven't had the time or skills to do before, or something you can continue to work on post OceanHackWeek! +* Hacking is a community activity! It's okay to choose projects that you can't accomplish alone as other people will be there to help you, both at OceanHackWeek and outside of it! +* Help your group member: you might be the person they need to solve their problem, and vice versa. +* When discussing, pitch your explanation to the least experienced hacker in the group, and you'll end up better understanding what you're trying to do, or need to revise your idea. +* You can mix programming languages as needed in order to get started, but do check in with your project mentors and group members to make sure your efforts are straightforward to be absorbed into the project. + + + + + + + + + diff --git a/ohw23/schedule.md b/ohw23/schedule.md new file mode 100644 index 00000000..fcadefa9 --- /dev/null +++ b/ohw23/schedule.md @@ -0,0 +1,26 @@ +# Schedule + +OceanHackWeek 2022 will take place August 15-19. + +With a global virtual event and many satellites, this schedule is still very much under development. The global virtual event will be meeting from 11-2 Pacific, and most satellites are planning at least part of their day around that time block to encourage cross-satellite interaction. + +## Overview of the global event + + + +## Satellite events + +For satellite event schedules, please check out their individual pages to see how each satellite will work with the global event. Some satellite schedules may not be ready yet; contact the satellite organizers via Slack for more information. + +- [US Northeast](./maine/index.md) +- [US Northwest](./seattle/index.md) +- [US Southwest](./san-diego/index.md) +- [Australia](./australia/index.md) +- [Brazil](./brazil/index.md) +- [Español](./espanol/index.es.md) + +```{toctree} +:hidden: + +monday +``` \ No newline at end of file diff --git a/ohw23/tutorials-index/data-access-in-python.md b/ohw23/tutorials-index/data-access-in-python.md new file mode 100644 index 00000000..3a052621 --- /dev/null +++ b/ohw23/tutorials-index/data-access-in-python.md @@ -0,0 +1,10 @@ +# Data access in Python + +```{toctree} + +../tutorials/01-Tue/00-data-access-in-python/00-data-access.ipynb +../tutorials/01-Tue/00-data-access-in-python/01-extras-https.ipynb +../tutorials/01-Tue/00-data-access-in-python/02-extras-data-clean-up.ipynb +../tutorials/01-Tue/00-data-access-in-python/03-extras-argopy-erddap.ipynb +../tutorials/01-Tue/00-data-access-in-python/04-extras-erddapy_saildrone.ipynb +``` diff --git a/ohw23/tutorials-index/data-access-in-r.md b/ohw23/tutorials-index/data-access-in-r.md new file mode 100644 index 00000000..77f819c8 --- /dev/null +++ b/ohw23/tutorials-index/data-access-in-r.md @@ -0,0 +1,7 @@ +# Data access in R + +```{toctree} +../tutorials/01-Tue/00-data-access-in-R/01_data_access.Rmd +../tutorials/01-Tue/00-data-access-in-R/02_get_nbdc.Rmd +../tutorials/01-Tue/00-data-access-in-R/03_get_nao.Rmd +``` diff --git a/ohw23/tutorials-index/data-vis-in-python.md b/ohw23/tutorials-index/data-vis-in-python.md new file mode 100644 index 00000000..092255f0 --- /dev/null +++ b/ohw23/tutorials-index/data-vis-in-python.md @@ -0,0 +1,13 @@ +# Data visualization in Python + +```{toctree} + +../tutorials/02-Wed/01-data-visualization-in-python/tutorial/index.ipynb +../tutorials/02-Wed/01-data-visualization-in-python/tutorial/00_Setup.ipynb +../tutorials/02-Wed/01-data-visualization-in-python/tutorial/01_Overview.ipynb +../tutorials/02-Wed/01-data-visualization-in-python/tutorial/02_Building_Panels.ipynb +../tutorials/02-Wed/01-data-visualization-in-python/tutorial/03_Interlinked_Panels.ipynb +../tutorials/02-Wed/01-data-visualization-in-python/tutorial/04_Basic_Plotting.ipynb +../tutorials/02-Wed/01-data-visualization-in-python/tutorial/05_Composing_Plots.ipynb + +``` diff --git a/ohw23/tutorials-index/espanol/index.md b/ohw23/tutorials-index/espanol/index.md new file mode 100644 index 00000000..00af5373 --- /dev/null +++ b/ohw23/tutorials-index/espanol/index.md @@ -0,0 +1,6 @@ +# Espanol Tutorials + +```{toctree} +python-cientifico +../../tutorials/optional/espanol/datos-espaciales-tidy/Notas.Rmd +``` diff --git a/ohw23/tutorials-index/espanol/python-cientifico.md b/ohw23/tutorials-index/espanol/python-cientifico.md new file mode 100644 index 00000000..a1ddbc68 --- /dev/null +++ b/ohw23/tutorials-index/espanol/python-cientifico.md @@ -0,0 +1,8 @@ +# Python Cientifico + +```{toctree} +Intro to Python <../../tutorials/optional/espanol/python-cientifico/intro_to_python_ohw2022.ipynb> +Read tabular data<../../tutorials/optional/espanol/python-cientifico/read_tabulardata.ipynb> +Intro to Plotting <../../tutorials/optional/espanol/python-cientifico/Intro_to_plot.ipynb> +Intro to NetCDF <../../tutorials/optional/espanol/python-cientifico/intro_to_netcdf.ipynb> +``` diff --git a/ohw23/tutorials-index/index.md b/ohw23/tutorials-index/index.md new file mode 100644 index 00000000..de96dd57 --- /dev/null +++ b/ohw23/tutorials-index/index.md @@ -0,0 +1,14 @@ +# Tutorials + +```{toctree} +:maxdepth: 1 + +../../resources/tutorials/getting_started +../tutorials/00-Mon/xarray-in-45-min.ipynb +data-access-in-python +data-access-in-r +data-vis-in-python +machine-learning-applications +espanol/index +../tutorials/optional/managing-conda-envs/README.md +``` diff --git a/ohw23/tutorials-index/machine-learning-applications.md b/ohw23/tutorials-index/machine-learning-applications.md new file mode 100644 index 00000000..555b9c46 --- /dev/null +++ b/ohw23/tutorials-index/machine-learning-applications.md @@ -0,0 +1,7 @@ +# Machine learning applications + +```{toctree} +../tutorials/03-Thu/00-machine-learning/00-unsupervised-PCA.ipynb +../tutorials/03-Thu/00-machine-learning/01-unsupervised-kmeans.ipynb +../tutorials/03-Thu/00-machine-learning/02-supervised-knn.ipynb +``` From 23eaf8747a83e57aa8329d195bec33cf5c3275aa Mon Sep 17 00:00:00 2001 From: Emilio Mayorga Date: Tue, 25 Jul 2023 14:48:59 -0700 Subject: [PATCH 04/12] Remove from resources content that was moved to specific events, or was unused --- resources/logistics/getting_help.md | 41 ------------------ resources/logistics/index.md | 42 ------------------- resources/projects/guidelines.md | 65 ----------------------------- resources/projects/index.md | 35 ---------------- resources/projects/steps.md | 47 --------------------- resources/website/updates.md | 2 - 6 files changed, 232 deletions(-) delete mode 100644 resources/logistics/getting_help.md delete mode 100644 resources/logistics/index.md delete mode 100644 resources/projects/guidelines.md delete mode 100644 resources/projects/index.md delete mode 100644 resources/projects/steps.md delete mode 100644 resources/website/updates.md diff --git a/resources/logistics/getting_help.md b/resources/logistics/getting_help.md deleted file mode 100644 index c03bb79d..00000000 --- a/resources/logistics/getting_help.md +++ /dev/null @@ -1,41 +0,0 @@ -# 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 `#ohw22-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. - -## Helpdesk - -We've set up the `#ohw22-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 - -- Ask questions on Slack! Use the `#ohw22-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 [Projects Getting Started page](../projects/steps.md). Feel free to post a question on the `#ohw22_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://oceanhackweek.wufoo.com/forms/zep2ybt1swlulc/).** - diff --git a/resources/logistics/index.md b/resources/logistics/index.md deleted file mode 100644 index 53bcc7a0..00000000 --- a/resources/logistics/index.md +++ /dev/null @@ -1,42 +0,0 @@ -# Logistics Overview - -Some of you will participate in person at various satellite events, and others will participate virtually from time zones all over the world. As we have learned throughout the pandemic, 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. - -## Time - -OceanHackWeek 2022 will take place August 15-19. - -**In-person participants** will gather as for times as directed by the satellite organizers. While **virtual participants** may choose to engage primarily with this group and schedule via Zoom and Slack, we strongly encourage you to join the program designed specifically as a virtual event. The virtual event will be split into two schedules and groups based on the distribution of participant time zones, in a 3-hour daily block of formal, live activities. The **larger virtual event** will take place 11:00am - 2:00pm PDT / 18:00 - 21:00 UTC. - -Detailed schedules are available [Schedule page](../../ohw22/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 *oceanhkw@uw.edu*. - -[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 [Project overview](../projects/index.md) and [Hacking at OHW22](../projects/steps.md) for more info. - -## 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/resources/projects/guidelines.md b/resources/projects/guidelines.md deleted file mode 100644 index 81a8c436..00000000 --- a/resources/projects/guidelines.md +++ /dev/null @@ -1,65 +0,0 @@ - - - - -# Project Guidelines - -## Project Template -Each project requires a brief project summary in the README.md of each GitHub project folder. Below is a template for the project summary. - -### Project title - -Brief title describing the proposed work. - -### Collaborators on this project - -List all participants on the project. - -### The problem - -What oceanographic data science problem are you going to explore? Try to focus on the data science/methodology problem first, followed by the location-specific oceanographic example afterwards. The project is likely more engaging for fellow hackers if it is centered around common data science problems. For example, the project could be to develop a workflow in Python to analyze CTD time series from multiple data sources, instead of emphasizing and focusing only on temperature variations in one very specific part of the ocean. - -### Application example - -Here is where you follow up with a location-specific example of where the data science methodology applies and list example datasets (size, format, how to access) that could be used for this exploration. - -### Specific tasks - -List the specific tasks you want to accomplish. - -### Existing methods - -How would you or others traditionally try to address this problem? - -### Proposed methods/tools - -Building from what you learn at Oceanhackweek, what new approaches would you like to try to implement? - -### Background reading - -Optional: links to manuscripts or technical documents for more in-depth analysis. - - - -## Project Ideas -* Developing tutorials for using NASA data on the cloud. -* Working on an efficient open source matchup tutorial for satellite orbital data and in situ point or trajectory data. -* Developing an OSS algorithm development toolbox in Python to deal with a 400GB AMSR brightness temperature - in situ matchup database. - - - -## Project Data Storage - -If your group needs to store data for project use during Oceanhackweek, depending on the volume, below is what we recommend: -- Whenever possible, public datasets like OOI, ARGO, satellite, etc. should be accessed remotely in the Jupyter notebook through standard protocols like OPeNDAP or other programmatic approaches. -- **Data that are <1 MB**: can be included directly in the project Github repository. -- **Data that are <10 GB**: can be stored in your home space on ocean.pangeo.io. When you are accessing data from the internet, it is often useful to have a cell in the notebook that downloads such data into your home space if those data are not there, otherwise do nothing if they are already there. You can also upload a local dataset through the pangeo interface. You can upload only one file as of now, so if you have multiple files you will need to zip them and unzip them later from the terminal. These are two ways to fetch and store larger datasets locally if they are not enormous. -- **Data that are >10 GB**: are best stored in a cloud-optimized format. If you don't already have the data on the cloud, please talk to the instructors about your needs and how you anticipate using the data. We can help you prepare and upload the data to [cloud object storage](https://en.wikipedia.org/wiki/Cloud_storage) with Oceanhackweek support. -- Questions? Feel free post on Slack #project channel or email [oceanhkw@uw.edu](mailto:oceanhkw@uw.edu). diff --git a/resources/projects/index.md b/resources/projects/index.md deleted file mode 100644 index ff2187f3..00000000 --- a/resources/projects/index.md +++ /dev/null @@ -1,35 +0,0 @@ -# Project Overview - -Collaborative projects are a key component of OceanHackWeek, in which you get to interact with others closely and apply new skills to make something exciting happen: it can be creating tools to streamline access of a particular data source, visualizing some high density data interactively, testing existing models with new data sources, or anything else you may want to do at the intersection of oceanography and data science. - -## What is a Hack? - -A "hack" is a small project that aims to solve a specific problem using computational tools. - -Examples of hacks include: - -* Build a working demo of a new or modified algorithm -* Outline of a larger project, with some key features scoped -* Visualization of an old dataset in a new manner -* Modify an algorithm and apply it to a new dataset -* Combine two pre-existing pieces of code to perform some new function -* Create a tool to apply to work with existing code, datasets -* Transform code from one language to another to use with other tools -* Update old code to run faster, on new machines, and/or more efficiently -* Extend an existing project with an additional feature -* Simplify code to be more maintainable, aka "paying technical debt" - - - -## Why hack at OceanHackWeek? - -Increasingly, research and software development are conducted by groups of people with diverse skills and backgrounds. We believe this collaborative work leads to more innovative solutions to complex problems. At OceanHackWeek, our goal is to explore with you some of the skills needed to navigate technical and social challenges of working in these kinds of collaborative settings. We believe the best way to do so is to provide opportunities for you to gain hands-on experience in working together with others on a well-defined problem related to ocean sciences. - - -```{toctree} -:maxdepth: 2 -:caption: OceanHackWeek 2022 (OHW22) -:hidden: - -steps.md -``` diff --git a/resources/projects/steps.md b/resources/projects/steps.md deleted file mode 100644 index c519b12d..00000000 --- a/resources/projects/steps.md +++ /dev/null @@ -1,47 +0,0 @@ -# Hacking at OHW22 - -## How will the projects be conducted? - -We have put together a [few questions](https://github.com/oceanhackweek/discussions/discussions/categories/ohw22-project-planning) that can help you propose a project in [GitHub discussions](https://github.com/oceanhackweek/discussions/discussions/categories/ohw22-project-planning). - -On Monday August 15th we will have a brief “project setup” session for an overview of all projects already proposed up to that point, and give another opportunity to pitch new ideas that may be formed throughout the day. Project proposals must be submitted by the end of this day (Day 1). Each satellite may have its own, specific deadline time, so please connect with your satellite or the global event for details. - -## Tips for getting started - -* Potentially choose something that you've been interested but haven't had the time or skills to do before, or something you can continue to work on post OceanHackWeek! -* Hacking is a community activity! It's okay to choose projects that you can't accomplish alone as other people will be there to help you, both at OceanHackWeek and outside of it! -* Help your group member: you might be the person they need to solve their problem, and vice versa. -* When discussing, pitch your explanation to the least experienced hacker in the group, and you'll end up better understanding what you're trying to do, or need to revise your idea. -* You can mix programming languages as needed in order to get started, but do check in with your project mentors and group members to make sure your efforts are straightforward to be absorbed into the project. - - - - - - - - - diff --git a/resources/website/updates.md b/resources/website/updates.md deleted file mode 100644 index f5dbb8c4..00000000 --- a/resources/website/updates.md +++ /dev/null @@ -1,2 +0,0 @@ -```{include} ../../_InstructionSiteUpdates.md -``` From 09ae9406e311f97ec155a44fb6545a6d60a9787d Mon Sep 17 00:00:00 2001 From: Emilio Mayorga Date: Tue, 25 Jul 2023 14:50:19 -0700 Subject: [PATCH 05/12] Add ohw22/index.md to another toctree, to expose ohw22 section toctree --- about/pasthackweeks.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/about/pasthackweeks.md b/about/pasthackweeks.md index 6b36b4e7..4bca9360 100644 --- a/about/pasthackweeks.md +++ b/about/pasthackweeks.md @@ -61,3 +61,11 @@ OceanHackWeek started out as an in-person event in Seattle with limited virtual - [Participant testimonials](testimonials.md#ohw18-in-person) - [Schedule](https://oceanhackweek.github.io/ohw2018/schedule.html). Links to tutorials are found here. - [Web site](https://oceanhackweek.github.io/ohw2018/) + + +```{toctree} +:maxdepth: 1 +:hidden: + +../ohw22/index.md +``` \ No newline at end of file From 39de20d5e92592d7ebe897257ace82f172b8babe Mon Sep 17 00:00:00 2001 From: Emilio Mayorga Date: Tue, 25 Jul 2023 14:52:05 -0700 Subject: [PATCH 06/12] Fix ohw22 tutorials page navigation, including getting started page. Plus other ohw22 cleanup --- ohw22/projects/guidelines.md | 65 ------------------------------ ohw22/tutorials-index/index.md | 2 +- ohw22/tutorials_getting_started.md | 37 +++++++++++++++++ 3 files changed, 38 insertions(+), 66 deletions(-) delete mode 100644 ohw22/projects/guidelines.md create mode 100644 ohw22/tutorials_getting_started.md diff --git a/ohw22/projects/guidelines.md b/ohw22/projects/guidelines.md deleted file mode 100644 index 81a8c436..00000000 --- a/ohw22/projects/guidelines.md +++ /dev/null @@ -1,65 +0,0 @@ - - - - -# Project Guidelines - -## Project Template -Each project requires a brief project summary in the README.md of each GitHub project folder. Below is a template for the project summary. - -### Project title - -Brief title describing the proposed work. - -### Collaborators on this project - -List all participants on the project. - -### The problem - -What oceanographic data science problem are you going to explore? Try to focus on the data science/methodology problem first, followed by the location-specific oceanographic example afterwards. The project is likely more engaging for fellow hackers if it is centered around common data science problems. For example, the project could be to develop a workflow in Python to analyze CTD time series from multiple data sources, instead of emphasizing and focusing only on temperature variations in one very specific part of the ocean. - -### Application example - -Here is where you follow up with a location-specific example of where the data science methodology applies and list example datasets (size, format, how to access) that could be used for this exploration. - -### Specific tasks - -List the specific tasks you want to accomplish. - -### Existing methods - -How would you or others traditionally try to address this problem? - -### Proposed methods/tools - -Building from what you learn at Oceanhackweek, what new approaches would you like to try to implement? - -### Background reading - -Optional: links to manuscripts or technical documents for more in-depth analysis. - - - -## Project Ideas -* Developing tutorials for using NASA data on the cloud. -* Working on an efficient open source matchup tutorial for satellite orbital data and in situ point or trajectory data. -* Developing an OSS algorithm development toolbox in Python to deal with a 400GB AMSR brightness temperature - in situ matchup database. - - - -## Project Data Storage - -If your group needs to store data for project use during Oceanhackweek, depending on the volume, below is what we recommend: -- Whenever possible, public datasets like OOI, ARGO, satellite, etc. should be accessed remotely in the Jupyter notebook through standard protocols like OPeNDAP or other programmatic approaches. -- **Data that are <1 MB**: can be included directly in the project Github repository. -- **Data that are <10 GB**: can be stored in your home space on ocean.pangeo.io. When you are accessing data from the internet, it is often useful to have a cell in the notebook that downloads such data into your home space if those data are not there, otherwise do nothing if they are already there. You can also upload a local dataset through the pangeo interface. You can upload only one file as of now, so if you have multiple files you will need to zip them and unzip them later from the terminal. These are two ways to fetch and store larger datasets locally if they are not enormous. -- **Data that are >10 GB**: are best stored in a cloud-optimized format. If you don't already have the data on the cloud, please talk to the instructors about your needs and how you anticipate using the data. We can help you prepare and upload the data to [cloud object storage](https://en.wikipedia.org/wiki/Cloud_storage) with Oceanhackweek support. -- Questions? Feel free post on Slack #project channel or email [oceanhkw@uw.edu](mailto:oceanhkw@uw.edu). diff --git a/ohw22/tutorials-index/index.md b/ohw22/tutorials-index/index.md index de96dd57..111000c2 100644 --- a/ohw22/tutorials-index/index.md +++ b/ohw22/tutorials-index/index.md @@ -3,7 +3,7 @@ ```{toctree} :maxdepth: 1 -../../resources/tutorials/getting_started +../tutorials_getting_started ../tutorials/00-Mon/xarray-in-45-min.ipynb data-access-in-python data-access-in-r diff --git a/ohw22/tutorials_getting_started.md b/ohw22/tutorials_getting_started.md new file mode 100644 index 00000000..a7839bce --- /dev/null +++ b/ohw22/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](../../ohw22/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=OHW22) + +::: + +:::{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=OHW22) + +::: + +:::: + +``` + +See this [extended discussion](../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. From a806700ad2f9689b28fcfdde2d9e01d3551482b0 Mon Sep 17 00:00:00 2001 From: Emilio Mayorga Date: Tue, 25 Jul 2023 14:52:49 -0700 Subject: [PATCH 07/12] Fix ohw23 tutorials page navigation, including getting started page. Plus schedule page fixes --- ohw23/schedule.md | 7 +++--- ohw23/tutorials-index/index.md | 2 +- ohw23/tutorials_getting_started.md | 37 ++++++++++++++++++++++++++++++ 3 files changed, 42 insertions(+), 4 deletions(-) create mode 100644 ohw23/tutorials_getting_started.md diff --git a/ohw23/schedule.md b/ohw23/schedule.md index fcadefa9..66a32487 100644 --- a/ohw23/schedule.md +++ b/ohw23/schedule.md @@ -1,6 +1,6 @@ # Schedule -OceanHackWeek 2022 will take place August 15-19. +**OceanHackWeek 2022 will take place August 15-19.** With a global virtual event and many satellites, this schedule is still very much under development. The global virtual event will be meeting from 11-2 Pacific, and most satellites are planning at least part of their day around that time block to encourage cross-satellite interaction. @@ -8,7 +8,8 @@ With a global virtual event and many satellites, this schedule is still very muc -## Satellite events + + \ No newline at end of file diff --git a/ohw23/tutorials-index/index.md b/ohw23/tutorials-index/index.md index de96dd57..111000c2 100644 --- a/ohw23/tutorials-index/index.md +++ b/ohw23/tutorials-index/index.md @@ -3,7 +3,7 @@ ```{toctree} :maxdepth: 1 -../../resources/tutorials/getting_started +../tutorials_getting_started ../tutorials/00-Mon/xarray-in-45-min.ipynb data-access-in-python data-access-in-r diff --git a/ohw23/tutorials_getting_started.md b/ohw23/tutorials_getting_started.md new file mode 100644 index 00000000..a7839bce --- /dev/null +++ b/ohw23/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](../../ohw22/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=OHW22) + +::: + +:::{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=OHW22) + +::: + +:::: + +``` + +See this [extended discussion](../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. From 9b56dce88a3da9b55f8feb1ed278e40c63170cba Mon Sep 17 00:00:00 2001 From: Emilio Mayorga Date: Wed, 26 Jul 2023 20:45:49 -0700 Subject: [PATCH 08/12] Move general project content to resources and use myst include from event project pages --- index.md | 2 +- ohw22/projects/index.md | 36 +++----------- ohw23/projects/index.md | 32 +++---------- ohw23/projects/steps.md | 47 ------------------- resources/index.md | 1 + .../steps.md => resources/projects.md | 29 +++++++++--- 6 files changed, 39 insertions(+), 108 deletions(-) delete mode 100644 ohw23/projects/steps.md rename ohw22/projects/steps.md => resources/projects.md (61%) diff --git a/index.md b/index.md index 14697456..4d2be09a 100644 --- a/index.md +++ b/index.md @@ -155,5 +155,5 @@ about/index.md OceanHackWeek 2023 resources/index.md about/pasthackweeks.md -% posts + ``` diff --git a/ohw22/projects/index.md b/ohw22/projects/index.md index ff2187f3..e75db96e 100644 --- a/ohw22/projects/index.md +++ b/ohw22/projects/index.md @@ -1,35 +1,13 @@ -# Project Overview +# Hacking at OHW22 -Collaborative projects are a key component of OceanHackWeek, in which you get to interact with others closely and apply new skills to make something exciting happen: it can be creating tools to streamline access of a particular data source, visualizing some high density data interactively, testing existing models with new data sources, or anything else you may want to do at the intersection of oceanography and data science. +## How will the projects be conducted? -## What is a Hack? +We have put together a [few questions](https://github.com/oceanhackweek/discussions/discussions/categories/ohw22-project-planning) that can help you propose a project in [GitHub discussions](https://github.com/oceanhackweek/discussions/discussions/categories/ohw22-project-planning). -A "hack" is a small project that aims to solve a specific problem using computational tools. +On Monday August 15th we will have a brief “project setup” session for an overview of all projects already proposed up to that point, and give another opportunity to pitch new ideas that may be formed throughout the day. Project proposals must be submitted by the end of this day (Day 1). Each satellite may have its own, specific deadline time, so please connect with your satellite or the global event for details. -Examples of hacks include: +## Project overview -* Build a working demo of a new or modified algorithm -* Outline of a larger project, with some key features scoped -* Visualization of an old dataset in a new manner -* Modify an algorithm and apply it to a new dataset -* Combine two pre-existing pieces of code to perform some new function -* Create a tool to apply to work with existing code, datasets -* Transform code from one language to another to use with other tools -* Update old code to run faster, on new machines, and/or more efficiently -* Extend an existing project with an additional feature -* Simplify code to be more maintainable, aka "paying technical debt" - - - -## Why hack at OceanHackWeek? - -Increasingly, research and software development are conducted by groups of people with diverse skills and backgrounds. We believe this collaborative work leads to more innovative solutions to complex problems. At OceanHackWeek, our goal is to explore with you some of the skills needed to navigate technical and social challenges of working in these kinds of collaborative settings. We believe the best way to do so is to provide opportunities for you to gain hands-on experience in working together with others on a well-defined problem related to ocean sciences. - - -```{toctree} -:maxdepth: 2 -:caption: OceanHackWeek 2022 (OHW22) -:hidden: - -steps.md +```{include} ../../resources/projects.md +:start-after: "# Project Overview" ``` diff --git a/ohw23/projects/index.md b/ohw23/projects/index.md index 5d8a3e95..9d4d1fb1 100644 --- a/ohw23/projects/index.md +++ b/ohw23/projects/index.md @@ -1,31 +1,13 @@ -# Project Overview +# Hacking at OHW23 -Collaborative projects are a key component of OceanHackWeek, in which you get to interact with others closely and apply new skills to make something exciting happen: it can be creating tools to streamline access of a particular data source, visualizing some high density data interactively, testing existing models with new data sources, or anything else you may want to do at the intersection of oceanography and data science. +## How will the projects be conducted? -## What is a Hack? +We have put together a [few questions](https://github.com/oceanhackweek/discussions/discussions/categories/ohw22-project-planning) that can help you propose a project in [GitHub discussions](https://github.com/oceanhackweek/discussions/discussions/categories/ohw22-project-planning). -A "hack" is a small project that aims to solve a specific problem using computational tools. +On Monday August 15th we will have a brief “project setup” session for an overview of all projects already proposed up to that point, and give another opportunity to pitch new ideas that may be formed throughout the day. Project proposals must be submitted by the end of this day (Day 1). Each satellite may have its own, specific deadline time, so please connect with your satellite or the global event for details. -Examples of hacks include: +## Project overview -* Build a working demo of a new or modified algorithm -* Outline of a larger project, with some key features scoped -* Visualization of an old dataset in a new manner -* Modify an algorithm and apply it to a new dataset -* Combine two pre-existing pieces of code to perform some new function -* Create a tool to apply to work with existing code, datasets -* Transform code from one language to another to use with other tools -* Update old code to run faster, on new machines, and/or more efficiently -* Extend an existing project with an additional feature -* Simplify code to be more maintainable, aka "paying technical debt" - -## Why hack at OceanHackWeek? - -Increasingly, research and software development are conducted by groups of people with diverse skills and backgrounds. We believe this collaborative work leads to more innovative solutions to complex problems. At OceanHackWeek, our goal is to explore with you some of the skills needed to navigate technical and social challenges of working in these kinds of collaborative settings. We believe the best way to do so is to provide opportunities for you to gain hands-on experience in working together with others on a well-defined problem related to ocean sciences. - - -```{toctree} -:hidden: - -steps.md +```{include} ../../resources/projects.md +:start-after: "# Project Overview" ``` diff --git a/ohw23/projects/steps.md b/ohw23/projects/steps.md deleted file mode 100644 index 7284f811..00000000 --- a/ohw23/projects/steps.md +++ /dev/null @@ -1,47 +0,0 @@ -# Hacking at OHW23 - -## How will the projects be conducted? - -We have put together a [few questions](https://github.com/oceanhackweek/discussions/discussions/categories/ohw22-project-planning) that can help you propose a project in [GitHub discussions](https://github.com/oceanhackweek/discussions/discussions/categories/ohw22-project-planning). - -On Monday August 15th we will have a brief “project setup” session for an overview of all projects already proposed up to that point, and give another opportunity to pitch new ideas that may be formed throughout the day. Project proposals must be submitted by the end of this day (Day 1). Each satellite may have its own, specific deadline time, so please connect with your satellite or the global event for details. - -## Tips for getting started - -* Potentially choose something that you've been interested but haven't had the time or skills to do before, or something you can continue to work on post OceanHackWeek! -* Hacking is a community activity! It's okay to choose projects that you can't accomplish alone as other people will be there to help you, both at OceanHackWeek and outside of it! -* Help your group member: you might be the person they need to solve their problem, and vice versa. -* When discussing, pitch your explanation to the least experienced hacker in the group, and you'll end up better understanding what you're trying to do, or need to revise your idea. -* You can mix programming languages as needed in order to get started, but do check in with your project mentors and group members to make sure your efforts are straightforward to be absorbed into the project. - - - - - - - - - diff --git a/resources/index.md b/resources/index.md index a15723ba..a615deeb 100644 --- a/resources/index.md +++ b/resources/index.md @@ -23,5 +23,6 @@ PLACEHOLDER. SEE THE Organizing OHW section :hidden: Preparation +Projects organizing/index.md ``` diff --git a/ohw22/projects/steps.md b/resources/projects.md similarity index 61% rename from ohw22/projects/steps.md rename to resources/projects.md index c519b12d..96b8e5c7 100644 --- a/ohw22/projects/steps.md +++ b/resources/projects.md @@ -1,10 +1,6 @@ -# Hacking at OHW22 +# Project Overview -## How will the projects be conducted? - -We have put together a [few questions](https://github.com/oceanhackweek/discussions/discussions/categories/ohw22-project-planning) that can help you propose a project in [GitHub discussions](https://github.com/oceanhackweek/discussions/discussions/categories/ohw22-project-planning). - -On Monday August 15th we will have a brief “project setup” session for an overview of all projects already proposed up to that point, and give another opportunity to pitch new ideas that may be formed throughout the day. Project proposals must be submitted by the end of this day (Day 1). Each satellite may have its own, specific deadline time, so please connect with your satellite or the global event for details. +Collaborative projects are a key component of OceanHackWeek, in which you get to interact with others closely and apply new skills to make something exciting happen: it can be creating tools to streamline access of a particular data source, visualizing some high density data interactively, testing existing models with new data sources, or anything else you may want to do at the intersection of oceanography and data science. ## Tips for getting started @@ -14,6 +10,27 @@ On Monday August 15th we will have a brief “project setup” session for an ov * When discussing, pitch your explanation to the least experienced hacker in the group, and you'll end up better understanding what you're trying to do, or need to revise your idea. * You can mix programming languages as needed in order to get started, but do check in with your project mentors and group members to make sure your efforts are straightforward to be absorbed into the project. +## What is a Hack? + +A "hack" is a small project that aims to solve a specific problem using computational tools. + +Examples of hacks include: + +* Build a working demo of a new or modified algorithm +* Outline of a larger project, with some key features scoped +* Visualization of an old dataset in a new manner +* Modify an algorithm and apply it to a new dataset +* Combine two pre-existing pieces of code to perform some new function +* Create a tool to apply to work with existing code, datasets +* Transform code from one language to another to use with other tools +* Update old code to run faster, on new machines, and/or more efficiently +* Extend an existing project with an additional feature +* Simplify code to be more maintainable, aka "paying technical debt" + +## Why hack at OceanHackWeek? + +Increasingly, research and software development are conducted by groups of people with diverse skills and backgrounds. We believe this collaborative work leads to more innovative solutions to complex problems. At OceanHackWeek, our goal is to explore with you some of the skills needed to navigate technical and social challenges of working in these kinds of collaborative settings. We believe the best way to do so is to provide opportunities for you to gain hands-on experience in working together with others on a well-defined problem related to ocean sciences. + From 7eb785389d5025c9d8a14a0a5a0d63f98231e03c Mon Sep 17 00:00:00 2001 From: Emilio Mayorga Date: Wed, 26 Jul 2023 20:57:34 -0700 Subject: [PATCH 09/12] Remove bad posts entry from main toctree --- index.md | 1 - 1 file changed, 1 deletion(-) diff --git a/index.md b/index.md index 4d2be09a..ba5811b6 100644 --- a/index.md +++ b/index.md @@ -155,5 +155,4 @@ about/index.md OceanHackWeek 2023 resources/index.md about/pasthackweeks.md - ``` From 11f3790d751d6ba58ad9b5777b1524a6b74b286a Mon Sep 17 00:00:00 2001 From: Emilio Mayorga Date: Wed, 26 Jul 2023 21:15:42 -0700 Subject: [PATCH 10/12] Fix some broken links to event projects page. Update channel names in event projects page --- ohw22/logistics/getting_help.md | 2 +- ohw22/logistics/index.md | 2 +- ohw23/logistics/getting_help.md | 8 ++++---- ohw23/logistics/index.md | 2 +- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/ohw22/logistics/getting_help.md b/ohw22/logistics/getting_help.md index c03bb79d..a15cdfd3 100644 --- a/ohw22/logistics/getting_help.md +++ b/ohw22/logistics/getting_help.md @@ -33,7 +33,7 @@ You are also welcome to direct message the helpers if you don't feel comfortable ## Projects -See the [Projects Getting Started page](../projects/steps.md). Feel free to post a question on the `#ohw22_project` channel, too. +See the [Hacking at OHW22 page](../projects/index.md) for more information. Feel free to post a question on the `#ohw22_project` channel, too. ## Reporting a Code of Conduct violation diff --git a/ohw22/logistics/index.md b/ohw22/logistics/index.md index 53bcc7a0..67faccc1 100644 --- a/ohw22/logistics/index.md +++ b/ohw22/logistics/index.md @@ -27,7 +27,7 @@ We will use Zoom to broadcast all tutorials. The Zoom link will be distributed v ## Hack projects -See [Project overview](../projects/index.md) and [Hacking at OHW22](../projects/steps.md) for more info. +See the [Hacking at OHW22 page](../projects/index.md) for more information. ## Getting Help diff --git a/ohw23/logistics/getting_help.md b/ohw23/logistics/getting_help.md index c03bb79d..f1c648ac 100644 --- a/ohw23/logistics/getting_help.md +++ b/ohw23/logistics/getting_help.md @@ -2,11 +2,11 @@ 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 `#ohw22-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 `#ohw23-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. ## Helpdesk -We've set up the `#ohw22-helpdesk` Slack channel to ask technical questions (or other types of questions, if you'd like). +We've set up the `#ohw23-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. @@ -25,7 +25,7 @@ You are also welcome to direct message the helpers if you don't feel comfortable ## During tutorials -- Ask questions on Slack! Use the `#ohw22-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 `#ohw23-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! @@ -33,7 +33,7 @@ You are also welcome to direct message the helpers if you don't feel comfortable ## Projects -See the [Projects Getting Started page](../projects/steps.md). Feel free to post a question on the `#ohw22_project` channel, too. +See the [Hacking at OHW23 page](../projects/index.md) for more information. Feel free to post a question on the `#ohw23_project` channel, too. ## Reporting a Code of Conduct violation diff --git a/ohw23/logistics/index.md b/ohw23/logistics/index.md index 53bcc7a0..f9f545ac 100644 --- a/ohw23/logistics/index.md +++ b/ohw23/logistics/index.md @@ -27,7 +27,7 @@ We will use Zoom to broadcast all tutorials. The Zoom link will be distributed v ## Hack projects -See [Project overview](../projects/index.md) and [Hacking at OHW22](../projects/steps.md) for more info. +See the [Hacking at OHW23 page](../projects/index.md) for more information. ## Getting Help From ba7ed03cb976f4b5a0afee1915fb9aa3f5c8738b Mon Sep 17 00:00:00 2001 From: Emilio Mayorga Date: Thu, 27 Jul 2023 09:30:27 -0700 Subject: [PATCH 11/12] Add admonition to ohw23 front page about old content in ohw23 pages --- ohw23/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ohw23/index.md b/ohw23/index.md index 9e663a51..fc0f4aa9 100644 --- a/ohw23/index.md +++ b/ohw23/index.md @@ -1,9 +1,9 @@ # OceanHackWeek 2023 (OHW23) -```{admonition} OceanHackWeek 2023 +```{attention} :class: important -**Applicants have been notified and participants should expect further communications** +**We are rolling out the content for OHW23.** Some pages may initially have old information from OHW22, but will be updated very soon. **Watch out for old content and check back soon!** ``` OceanHackWeek 2023 (OHW23) will take a **hybrid** form consisting of a virtual event, an in-person event in Seattle, US, and an in-person event in Dunsbrough, Western Australia. It will take place on: From e8cb1543f4f2fee218f0f954961b37bb22adf9b8 Mon Sep 17 00:00:00 2001 From: Emilio Mayorga Date: Thu, 27 Jul 2023 09:41:45 -0700 Subject: [PATCH 12/12] Update tutorials-index to only show the getting started page --- ohw23/tutorials-index/index.md | 7 ------- 1 file changed, 7 deletions(-) diff --git a/ohw23/tutorials-index/index.md b/ohw23/tutorials-index/index.md index 111000c2..b3c8394a 100644 --- a/ohw23/tutorials-index/index.md +++ b/ohw23/tutorials-index/index.md @@ -4,11 +4,4 @@ :maxdepth: 1 ../tutorials_getting_started -../tutorials/00-Mon/xarray-in-45-min.ipynb -data-access-in-python -data-access-in-r -data-vis-in-python -machine-learning-applications -espanol/index -../tutorials/optional/managing-conda-envs/README.md ```