Merge branch 'main' into pack_intro

.github/workflows/ensure_clean_notebooks.py

@@ -30,13 +30,13 @@
 
 results = []
 for notebook in ipynbs:
- #if not notebook in exclude_notebooks:
- print(f'Checking {notebook}...')
- nb = nbformat.read(notebook, as_version=nbformat.NO_CONVERT)
- result = nbc.check_notebook(nb,
- remove_empty_cells=False,
- preserve_cell_metadata=True)
- results.append(result)
+ if not notebook in exclude_notebooks:
+  print(f'Checking {notebook}...')
+  nb = nbformat.read(notebook, as_version=nbformat.NO_CONVERT)
+  result = nbc.check_notebook(nb,
+  remove_empty_cells=False,
+  preserve_cell_metadata=True)
+  results.append(result)
 
 if False in results:
  sys.exit(1)

.github/workflows/qaqc.yaml

@@ -31,7 +31,7 @@ jobs:
  uses: codespell-project/actions-codespell@master
  with:
  check_filenames: true
- skip: '*.js,*.css,qaqc.yml,*.geojson'
+ skip: '*.js,*.css,qaqc.yml,*.geojson,conda/*'
  ignore_words_file: .codespellignore
  only_warn: 1
 

.templatesyncignore

@@ -13,5 +13,11 @@ team/*-*
 ###
 # book files (configuration, usage-specific)
 book/_config.yml
+book/logo.png
 ###
 # event-specific tutorials
+###
+# files you may want to exclude once you start using your template
+.gitignore
+README.md
+book/_toc.yml

CONTRIBUTING.md

@@ -59,7 +59,7 @@ To build our website, we need specific Python packages which are managed with th
 
 ## Contributing tutorials
 
-If you're adding a new Jupyter Notebook Tutorial, please first take a look at [our guide on creating tutorials](https://uwhackweek.github.io/hackweeks-as-a-service/resources/tutorial-resources.html).
+If you're adding a new Jupyter Notebook Tutorial, please first take a look at [our guide on creating tutorials](https://guidebook.hackweek.io/training/tutorials/index.html).
 
 When adding a new `.ipynb` file under `book/tutorials` be sure to:
 

book/CoC.md

@@ -1,30 +1,14 @@
-# Event Code of Conduct
+# Participant Conduct
 
-Guidelines to ensure we offer a hospitable and inclusive event and a list of resources for reporting violations. Although the content is similar, this event Code of Conduct should not be confused with the {{ '[Contributor Covenant Code of Conduct]({url}/{repo}/blob/main/CODE_OF_CONDUCT.md)'.format(url=github_org_url, repo=book_repo) }} governing contributions to this JupyterBook.
+We require all participants in the University of Washington (UW) eScience Hackweek program to comply with the [eScience Code of Conduct](https://escience.washington.edu/about/code-of-conduct/) copied below.
 
+Hackweek participants are intentionally diverse across many categories including academic standing, domain field, technical experience, etc., and we expect everyone to respect all perspectives represented. Please also read the [eScience Equity Statement](https://escience.washington.edu/about/equity-statement/).
 
----
-## Participant Conduct
+## Code of Conduct
 
-We require all participants in the University of Washington (UW) eScience Hackweek program to comply with the 
-[eScience Code of Conduct](https://escience.washington.edu/about/code-of-conduct/) copied below.
+The University of Washington eScience Institute (“eScience”) is dedicated to providing a welcoming, supportive and inclusive environment for all people, regardless of background and identity. We do not tolerate discrimination or harassment based on characteristics that include, but are not limited to gender, gender identity and expression, sexual orientation, marital status, disability, physical appearance, body size, race, age, national origin or religion. Any form of behavior to exclude, intimidate, or cause discomfort is a violation of the Code of Conduct. By participating in this community, participants accept to abide by the eScience Code of Conduct and accept the procedures by which any Code of Conduct incidents are resolved.
 
-Hackweek participants are intentionally diverse across many categories including academic standing, domain field, 
-technical experience, etc., and we expect everyone to respect all perspectives represented. Please also read the
-[eScience Equity Statement](https://escience.washington.edu/about/equity-statement/).
-
-### Code of Conduct
-
-The University of Washington eScience Institute (“eScience”) is dedicated to providing a welcoming, supportive and
-inclusive environment for all people, regardless of background and identity. We do not tolerate discrimination or 
-harassment based on characteristics that include, but are not limited to gender, gender identity and expression, 
-sexual orientation, marital status, disability, physical appearance, body size, race, age, national origin or 
-religion. Any form of behavior to exclude, intimidate, or cause discomfort is a violation of the Code of Conduct. 
-By participating in this community, participants accept to abide by the eScience Code of Conduct and accept the 
-procedures by which any Code of Conduct incidents are resolved.
-
-In order to foster a positive and professional learning environment we encourage the following kinds of behaviors 
-on all platforms and during all events, both in-person and online:
+In order to foster a positive and professional learning environment we encourage the following kinds of behaviors on all platforms and during all events, both in-person and online:
 
 * Use welcoming and inclusive language
 * Be respectful of different viewpoints and experiences
@@ -33,9 +17,7 @@ on all platforms and during all events, both in-person and online:
 
 Harassment includes, but is not limited to:
 
-* Written or verbal comments that reinforce social structures of domination related to gender, gender identity 
-and expression, sexual orientation, marital status, disability, physical appearance, body size, race, age, 
-national origin or religion
+* Written or verbal comments that reinforce social structures of domination related to gender, gender identity and expression, sexual orientation, marital status, disability, physical appearance, body size, race, age, national origin or religion
 * Violent threats or language directed against another person
 * Sexual language or images in public spaces
 * Deliberate intimidation, stalking, or following
@@ -46,24 +28,12 @@ national origin or religion
 * Nonconsensual or unwelcome physical contact
 * Advocating for, or encouraging, any of the above behavior
 
-Participants asked to stop any harassing behavior are expected to comply immediately. This applies to any 
-eScience events or activities, either online or in-person. Participants violating these rules may be 
-sanctioned or expelled from participation at the discretion of eScience staff. The organizers may take 
-action to redress anything designed to, or with the clear impact of, disrupting the event or making the 
-environment hostile for any participants. 
+Participants asked to stop any harassing behavior are expected to comply immediately. This applies to any eScience events or activities, either online or in-person. Participants violating these rules may be sanctioned or expelled from participation at the discretion of eScience staff. The organizers may take action to redress anything designed to, or with the clear impact of, disrupting the event or making the environment hostile for any participants. 
+
+Harassment and other code of conduct violations reduce the value of our programming for everyone. If someone makes you or anyone else feel unsafe or unwelcome, please report it as soon as possible. You can make a report either personally or anonymously. To personally report, contact the eScience executive director, Sarah Stone, at sstone3@uw.edu or another trusted staff member. Anonymous reports can be made [here](https://bit.ly/uwhackweekfeedback). If you are experiencing a problem or issue that needs to be addressed by someone outside the program, you may contact the UW Office of the Ombud at ombuds@uw.edu or 206-543-6028.
+
+[SafeCampus](https://www.washington.edu/safecampus/) (206-685-7233) is also available at any time to anonymously discuss safety and well-being concerns for yourself and others. SafeCampus is the University of Washington’s violence-prevention and response program, providing resources to UW students, staff, faculty and community members. For more information, visit their [What to Expect](https://www.washington.edu/safecampus/what-to-expect) page.
 
-Harassment and other code of conduct violations reduce the value of our programming for everyone. 
-If someone makes you or anyone else feel unsafe or unwelcome, please report it as soon as possible. 
-You can make a report either personally or anonymously. To personally report, contact the eScience 
-executive director, Sarah Stone, at sstone3@uw.edu or another trusted staff member. Anonymous 
-reports can be made {{ '[here]({url})'.format(url=anon_reporting_url) }}. If you are experiencing a problem 
-or issue that needs to be addressed by someone outside the program, you may contact the UW Office 
-of the Ombud at ombuds@uw.edu or 206-543-6028.
+Thank you for helping to make our institute inclusive, welcoming and safe.
 
-[SafeCampus](https://www.washington.edu/safecampus/) (206-685-7233) is also available at any time to 
-anonymously discuss safety and well-being concerns for yourself and others. SafeCampus is the University 
-of Washington’s violence-prevention and response program, providing resources to UW students, staff, 
-faculty and community members. For more information, 
-visit their [What to Expect](https://www.washington.edu/safecampus/what-to-expect) page.
 
-Thank you for helping to make our institute inclusive, welcoming and safe.

book/_config.yml

@@ -37,6 +37,8 @@ execute:
  execute_notebooks: 'force'
  exclude_patterns:
  - "**/geospatial-advanced.ipynb"
+ - "cloud-computing/04-cloud-optimized-icesat2.ipynb"
+ - "cloud-computing/atl08_parquet_files/atl08_parquet.ipynb"
  allow_errors: false
  # Per-cell notebook execution limit (seconds)
  timeout: 300

book/_toc.yml

@@ -5,7 +5,6 @@ format: jb-book
 parts:
 - caption: Details
  chapters:
- - file: logistics
  - title: Schedule
  url: https://2024.hackweek.io/index.html?jump_to=schedule
  - title: Team
@@ -17,6 +16,7 @@ parts:
  - file: preliminary/checklist
  - file: preliminary/git
 - caption: Tutorials
+ maxdepth: 1
  chapters:
  - file: tutorials/index
  sections:
@@ -28,13 +28,19 @@ parts:
  - file: tutorials/nb-to-package/sample.ipynb
  - file: tutorials/nb-to-package/package
  - file: tutorials/nb-to-package/community
+ - file: tutorials/mission-overview/icesat-2-mission-overview
+ - file: tutorials/cloud-computing/00-goals-and-outline
+ sections:
+ - file: tutorials/cloud-computing/01-cloud-computing
+ - file: tutorials/cloud-computing/02-cloud-data-access
+ - file: tutorials/cloud-computing/03-cloud-optimized-data-access
+ - file: tutorials/cloud-computing/04-cloud-optimized-icesat2
+ - file: tutorials/cloud-computing/atl08_parquet_files/atl08_parquet
+ options:
+ - titlesonly: true
 - caption: Projects
  chapters:
- - file: projects/list_of_projects
  - file: projects/index
- sections:
- - file: projects/project_roadmap
- - file: projects/project_initialization
 - caption: Reference
  chapters:
  - file: reference/glossary

book/intro.md

@@ -5,7 +5,7 @@
 
 📖 On this JupyterBook website you'll find [tutorials](tutorials/index). All tutorials are Jupyter Notebooks, designed to be run interactively, but also rendered on this website for convenience.
 
-👩‍💻 During a Hackweek teams work collaboratively on different projects. Read more about the projects and results on our [projects page](projects/list_of_projects)
+👩‍💻 During a Hackweek teams work collaboratively on different projects. Read more about the projects and results on our [projects page](projects/index)
 
 💡 Learn more about hackweeks hosted by the [University of Washington eScience Institute](https://uwhackweek.github.io/hackweeks-as-a-service/intro.html), or check out our publication describing the hackweek educational model {cite:p}`Huppenkothen2018`.
 
@@ -17,4 +17,4 @@
 * JupyterHub: {{ jupyterhub_url }}
 * GitHub organization: {{ github_org_url}}
 * Projects Spreadsheet: {{ project_spreadsheet_url }}
-```
+```

book/projects/index.md

@@ -1,17 +1,20 @@
-# Projects
-
-During hackweeks we invite participants to collaborate in small group project teams (usually 5-7 people). Projects provide unique opportunities for networking, advancing research and learning new things.
-
-We encourage you to be creative in how you design your project work! Here are some ways people have used project time in the past:
-
-* *focus on learning*: dive deeper into tutorial content and gain more hands on experience with new tools
-* *focus on community building*: hackweeks bring people together for the first time and projects are used to build social fabric and foster open science
-* *focus on research*: people often work to advance a research challenge using tools shared during the event. This often includes ongoing graduate and postgraduate investigations.
-* *focus on creating new tools*: hackweeks often expose general community software needs. Projects can be the catalyst for new community libraries.
-
-```{image} ../img/projects-montage.png
-:alt: picture of people interacting during hackweek project work
-:class: bg-primary mb-1
-:width: 700px
-:align: center
-```
+# Projects
+
+During hackweeks we invite participants to collaborate in small group project teams (usually 5-7 people). Projects provide unique opportunities for networking, advancing research and learning new things.
+
+```{image} ../img/projects-montage.png
+:alt: picture of people interacting during hackweek project work
+:class: bg-primary mb-1
+:width: 700px
+:align: center
+```
+
+You can find our comprehensive guide for organizing projects before, during, and after a hackweek in our [Hackweek Guidebook](https://guidebook.hackweek.io/training/projects/index.html). Below you'll find a table keeping track of all project work done during this event:
+
+## List of Projects
+
+Here is our current list of project for our {{dates}} {{ hackweek }} hackweek:
+
+| Project Name (with link to GitHub repo) | Short Description | Project Lead(s) |
+|:--------|:--------|:-----|
+| [Snow-Extrapolation](https://github.com/geo-smart/Snow-Extrapolation) | Goal: Improve National Snow Model (NSM) prediction performance in the Sierra Nevada mountains through domain constraints and the exploration of different ML algorithms. | Ryan Johnson |