Skip to content

Commit c99332c

Browse files
committed
updating outline
1 parent e380027 commit c99332c

File tree

1 file changed

+17
-15
lines changed

1 file changed

+17
-15
lines changed

docs/intro.md

Lines changed: 17 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -9,38 +9,40 @@ Authors: Valentina Staneva, Quinn Brencher, Scott Henderson
99

1010
In this tutorial we will introduce GitHub Actions to scientists as a tool for lightweight automation of scientific data workflows. We will
1111
demonstrate that GitHub Actions are not just a tool for software testing, but can be used in various ways to improve the reproducibility
12-
and impact of scientific analysis. Through a sequence of examples, we will demonstrate some of Github Actions' applications to scientific
12+
and impact of scientific analysis. Through a sequence of examples, we will demonstrate some of GitHub Actions' applications to scientific
1313
workflows, such as scheduled deployment of algorithms to sensor streams, updating visualizations based on new data, processing large
1414
datasets, model versioning and performance benchmarking. GitHub Actions can particularly empower Python scientific programmers who are not
1515
willing to build fully-fledged applications or set up complex computational infrastructure, but would like to increase the impact of their
1616
work. The goal is that participants will leave with their own ideas of how to integrate Github Actions in their own work.
1717

18-
## Description:
18+
## Description
1919

2020
GitHub Actions are quite popular within the software engineering community, but a scientific Python programmer may not have seen their use
2121
beyond a continuous integration framework for unit testing. We would like to increase their visibility through a scientific workflow lens.
2222
We will use examples that are relevant to the community: wrangling a messy realtime hydrophone data stream to display noise sounds from the
2323
Puget Sound (not far from the conference venue!) or processing hundreds of satellite radar images over glacial lakes in High-Mountain Asia
24-
to study flood hazards. We assume no knowledge on Github Actions and will start slowly with a “Hello World” step, but build quickly to
24+
to study flood hazards. We assume no knowledge on GitHub Actions and will start slowly with a “Hello World” step, but build quickly to
2525
create complex and exciting workflows. We will also showcase their value for scientific collaborations across institutions as a means to
2626
share reproducible workflows and computing infrastructure.
2727

28-
## Prerequisites:
29-
GitHub account, familiarity with git, GitHub, and Python (conda, scipy, matplotlib), some maturity in manipulating scientific data and
28+
## Prerequisites
29+
GitHub account, familiarity with git (commits, versioning), GitHub (push, pull requests), and Python (conda, scipy, matplotlib), some maturity in manipulating scientific data and
3030
exposure to the challenges associated with it, ability to read code (our examples may use libraries not familiar to the audience, but the
3131
focus will be on the steps these libraries accomplish rather than the details)
3232

33-
## Installation Instructions:
33+
## Installation Instructions
3434
Participants can make edits from the GitHub interface, but if they are willing to make updates locally, they need to have a functioning git
3535
([set up instructions](https://swcarpentry.github.io/git-novice/#installing-git))
3636

3737
## Outline
3838

39+
## Short Version
3940
```{tableofcontents}
4041
```
4142

43+
## Long Version (with approximate schedule)
4244
* Overview of GitHub Actions and Workflows and their popular uses in Python software development (examples of testing, listing,
43-
packaging)(30 min)
45+
packaging)(20 min)
4446
* We will explain the main components of GitHub Actions and associated terminology
4547
* We will summarize their typical uses in software development
4648
* We will point to popular GitHub Actions used in Python software development and packaging (the focus of this tutorial will not be
@@ -54,36 +56,36 @@ on them but rather on scientific pipelines)
5456
* we will deploy a typical scientific workflow: reading data, converting to a new format, and making a visualization
5557
* participants will update the deployment schedule to trigger a new workflow and will monitor the progress in the GitHub interface
5658

57-
* Break (10 min)
59+
* Break (15 min)
5860

5961
* Exporting results (30 min)
6062
* participants will learn about various ways to store the results:
6163
* caching
62-
* creating GitHub artifacts
6364
* committing to GitHub
64-
* storing to own storage
65-
* they will modify the code to make their own plot which will be automatically updated
65+
* creating GitHub artifacts
66+
* storing to personal storage
67+
* they will modify the code to make a new plot which will be automatically updated
6668
* they will use either matplotlib or an interactive library such as plotly
6769

6870
* Update results on a webpage (30 min)
6971
* we will overview different ways to display scientific results on a webpage
7072
* we will demonstrate the workflow to deploy the webpage
7173
* participants will rerender the webpage based on the updates in GitHub
7274

73-
* Large-scale data processing (30 min)
74-
* we will demonstrate a use-case of processing large data sets with Github Actions
75+
* Large-scale data processing (45 min)
76+
* we will demonstrate a use-case of processing large data sets with GitHub Actions
7577
* participants will fiddle with problem size to understand the power and limits of the computational infrastructure
7678
* we will discuss connections to cluster/cloud computing
7779

7880
* Break (10 min)
7981

80-
* Model Versioning and Comparison (30 min)
82+
* Model Versioning and Benchmarking (20 min)
8183
* we will introduce how to leverage GitHub’s version control to version different models and performance
8284
* participants can contribute a new model and check its performance
8385
* we will discuss how this can be used as a community network to share methods and results
8486

8587
* Recap and Discussion (or buffer time) (20 min)
86-
* we will have a discussion on potential uses of Github Actions within the work of the participants
88+
* we will have a discussion on potential uses of GitHub Actions within the work of the participants
8789

8890

8991
# References

0 commit comments

Comments
 (0)