From 07ac13695dd1cab4c3bc33e8610ee1f38e6b0559 Mon Sep 17 00:00:00 2001 From: Valentina Staneva Date: Sun, 6 Oct 2024 23:50:51 -0700 Subject: [PATCH 1/6] switch repo name --- docs/exporting-results.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/exporting-results.md b/docs/exporting-results.md index 0d269e1..29ecc20 100644 --- a/docs/exporting-results.md +++ b/docs/exporting-results.md @@ -32,8 +32,7 @@ gh run download The workflow run also provides a publicly available link to the download artifact: -Artifact download URL: [`https://github.com/uwescience/SciPy2024-GitHubActionsTutorial/actions/runs/9591972369/artifacts/1619380017`](https://github.com/uwescience/SciPy2024- -GitHubActionsTutorial/actions/runs/9591972369/artifacts/1619380017) +Artifact download URL: [`https://github.com/uwescience/GitHubActionsTutorial-USRSE24/actions/runs/11204894444/artifacts/2021247787`](https://github.com/uwescience/GitHubActionsTutorial-USRSE24/actions/runs/11204894444/artifacts/2021247787) There is a `download-artifact` action to download the artifacts and share between jobs within a workflow run (note this is limited to the individual workflow run, for downloading across runs use the other options). From 23051350b107ecb564e2e1e900d4e898bc2ffaeb Mon Sep 17 00:00:00 2001 From: Valentina Staneva Date: Mon, 7 Oct 2024 01:05:55 -0700 Subject: [PATCH 2/6] Update getting-started.md repo name --- docs/getting-started.md | 25 ++++++++++++------------- 1 file changed, 12 insertions(+), 13 deletions(-) diff --git a/docs/getting-started.md b/docs/getting-started.md index 9db65fd..d0b0c2d 100644 --- a/docs/getting-started.md +++ b/docs/getting-started.md @@ -1,26 +1,25 @@ # Setup * We expect all participants to have a GitHub account (if not you can make one here [https://github.com/login](https://github.com/login)) -* Fork [https://github.com/uwescience/SciPy2024-GitHubActionsTutorial](https://github.com/uwescience/SciPy2024-GitHubActionsTutorial) +* Fork [https://github.com/uwescience/SciPy2024-GitHubActionsTutorial](https://github.com/uwescience/GitHubActionsTutorial-USRSE24) * Enable GitHub Actions: * Settings -> Actions -> Allow actions and reusable workflows * [Managing Permissions Documentation](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository) -All workflow configurations are stored in the [`.github/workflows`](https://github.com/uwescience/SciPy2024-GitHubActionsTutorial/tree/main/.github/workflows) folder and we will go through them in the following order: - -1. [`python_env.yml`](https://github.com/uwescience/SciPy2024-GitHubActionsTutorial/blob/main/.github/workflows/python_env.yml) -2. [`conda_env.yml`](https://github.com/uwescience/SciPy2024-GitHubActionsTutorial/blob/main/.github/workflows/conda_env.yml) -3. [`noise_processing.yml`](https://github.com/uwescience/SciPy2024-GitHubActionsTutorial/blob/main/.github/workflows/noise_processing.yml) -4. [`create_website_spectrogram.yml`](https://github.com/uwescience/SciPy2024-GitHubActionsTutorial/blob/main/.github/workflows/create_website_spectrogram.yml) -5. [`create_website.yml`](https://github.com/uwescience/SciPy2024-GitHubActionsTutorial/blob/main/.github/workflows/create_website.yml) -6. [`batch_image_correlation.yml`](https://github.com/uwescience/SciPy2024-GitHubActionsTutorial/blob/main/.github/workflows/batch_image_correlation.yml) -7. [`image_correlation_pair.yml`](https://github.com/uwescience/SciPy2024-GitHubActionsTutorial/blob/main/.github/workflows/image_correlation_pair.yml) -8. [`summary_statistics.yml`](https://github.com/uwescience/SciPy2024-GitHubActionsTutorial/blob/main/.github/workflows/summary_statistics.yml) -9. [`model_benchmarking.yml`](https://github.com/uwescience/SciPy2024-GitHubActionsTutorial/blob/main/.github/workflows/model_benchmarking.yml) -10. [`create_website_benchmarks`](https://github.com/uwescience/SciPy2024-GitHubActionsTutorial/blob/main/.github/workflows/create_website_benchmarks.yml) +All workflow configurations are stored in the [`.github/workflows`](https://github.com/uwescience/GitHubActionsTutorial-USRSE24/tree/main/.github/workflows) folder and we will go through them in the following order: +1. [`python_env.yml`](https://github.com/uwescience/GitHubActionsTutorial-USRSE24/blob/main/.github/workflows/python_env.yml) +2. [`conda_env.yml`](https://github.com/uwescience/GitHubActionsTutorial-USRSE24/blob/main/.github/workflows/conda_env.yml) +3. [`noise_processing.yml`](https://github.com/uwescience/GitHubActionsTutorial-USRSE24/blob/main/.github/workflows/noise_processing.yml) +4. [`create_website_spectrogram.yml`](https://github.com/uwescience/GitHubActionsTutorial-USRSE24/blob/main/.github/workflows/create_website_spectrogram.yml) +5. [`create_website.yml`](https://github.com/uwescience/GitHubActionsTutorial-USRSE24/blob/main/.github/workflows/create_website.yml) +6. [`batch_image_correlation.yml`](https://github.com/uwescience/GitHubActionsTutorial-USRSE24/blob/main/.github/workflows/batch_image_correlation.yml) +7. [`image_correlation_pair.yml`](https://github.com/uwescience/GitHubActionsTutorial-USRSE24/blob/main/.github/workflows/image_correlation_pair.yml) +8. [`summary_statistics.yml`](https://github.com/uwescience/GitHubActionsTutorial-USRSE24/blob/main/.github/workflows/summary_statistics.yml) +9. [`model_benchmarking.yml`](https://github.com/uwescience/GitHubActionsTutorial-USRSE24/blob/main/.github/workflows/model_benchmarking.yml) +10. [`create_website_benchmarks`](https://github.com/uwescience/GitHubActionsTutorial-USRSE24/blob/main/.github/workflows/create_website_benchmarks.yml) From d2588cf1546221cd2ae6da03d2f5baddb5d8aa4b Mon Sep 17 00:00:00 2001 From: Valentina Staneva Date: Mon, 7 Oct 2024 01:12:06 -0700 Subject: [PATCH 3/6] Update model_benchmarking.md repo name --- docs/model_benchmarking.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/model_benchmarking.md b/docs/model_benchmarking.md index b96eaea..39e85d1 100644 --- a/docs/model_benchmarking.md +++ b/docs/model_benchmarking.md @@ -2,11 +2,11 @@ Here we will describe a scenario in which users submit different models to be applied to common data and compare the results. For this we will leverage GitHub's core features to facilitate code versioning and collaborative development and will set up a GitHub Actions configuration which triggers the evaluation when a user creates a `pull request` with a new version of the model and updates a table with user's results and corresponding commit number. -We will use a simple approach to approximate the number of ships passing during a time window by counting the number of peaks that appear above a threshold in the broadband plot. The threshold is set in the [`model_benchmarking.py`](https://github.com/uwescience/SciPy2024-GitHubActionsTutorial/blob/main/ambient_sound_analysis/model_benchmarking.py) script. +We will use a simple approach to approximate the number of ships passing during a time window by counting the number of peaks that appear above a threshold in the broadband plot. The threshold is set in the [`model_benchmarking.py`](https://github.com/uwescience/GitHubActionsTutorial-USRSE24/blob/main/ambient_sound_analysis/model_benchmarking.py) script. ## Model Versioning Workflow -The workflow which triggers the model evaluation is in [`model_benchmarking.yml`](https://github.com/uwescience/SciPy2024-GitHubActionsTutorial/blob/main/.github/workflows/model_benchmarking.yml). It consists of the following steps: +The workflow which triggers the model evaluation is in [`model_benchmarking.yml`](https://github.com/uwescience/GitHubActionsTutorial-USRSE24/blob/main/.github/workflows/model_benchmarking.yml). It consists of the following steps: 1. it gets triggered on `pull_request` * `synchronize` type ensures it get triggered when somebody updates existing pull request @@ -18,7 +18,7 @@ The workflow which triggers the model evaluation is in [`model_benchmarking.yml` ## Model Benchmarking Workflow -The next workflow follows the steps `create_website_spectrogram` workflow, which converts a notebook [`display_benchmarks`](https://github.com/uwescience/SciPy2024-GitHubActionsTutorial/blob/main/ambient_sound_analysis/display_benchmarks.ipynb) to a website. In this case, we have a very simple notebook which reads all `score_[SHA].csv` and displays a "benchmark table" with the individual entries. This notebook is converted to a webpage ([https://uwescience.github.io/SciPy2024-GitHubActionsTutorial/display_benchmarks.html](https://uwescience.github.io/SciPy2024-GitHubActionsTutorial/display_benchmarks.html/)). +The next workflow follows the steps `create_website_spectrogram` workflow, which converts a notebook [`display_benchmarks`](https://github.com/uwescience/GitHubActionsTutorial-USRSE24/blob/main/ambient_sound_analysis/display_benchmarks.ipynb) to a website. In this case, we have a very simple notebook which reads all `score_[SHA].csv` and displays a "benchmark table" with the individual entries. This notebook is converted to a webpage ([https://uwescience.github.io/GitHubActionsTutorial-USRSE24/display_benchmarks.html](https://uwescience.github.io/GitHubActionsTutorial-USRSE24/display_benchmarks.html/)). ### Exercise @@ -29,7 +29,7 @@ Create a branch and update the `model_versioning.py` file with a different thres threshold = ?? ``` -Submit a pull request from this branch to main and monitor the execution of the workflows. Check out the generated website at [https://uwescience.github.io/SciPy2024-GitHubActionsTutorial/display_benchmarks.html](https://uwescience.github.io/SciPy2024-GitHubActionsTutorial/display_benchmarks.html/). +Submit a pull request from this branch to main and monitor the execution of the workflows. Check out the generated website at [https://uwescience.github.io/GitHubActionsTutorial-USRSE24/display_benchmarks.html](https://uwescience.github.io/GitHubActionsTutorial-USRSE24/display_benchmarks.html/). @@ -42,4 +42,4 @@ Submit a pull request from this branch to main and monitor the execution of the - \ No newline at end of file + From 7a9bd8e5139e8910a927e1e13bf29b671a4d4b68 Mon Sep 17 00:00:00 2001 From: Valentina Staneva Date: Mon, 7 Oct 2024 01:13:48 -0700 Subject: [PATCH 4/6] Update python-environment-workflow.md rename repo --- docs/python-environment-workflow.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/python-environment-workflow.md b/docs/python-environment-workflow.md index 4e606ba..b9c1788 100644 --- a/docs/python-environment-workflow.md +++ b/docs/python-environment-workflow.md @@ -4,7 +4,7 @@ First, we will run a basic workflow which creates a python environment with a few scientific packages and prints out their version. Python Environment Workflow Configuration: -[`.github/workflows/python_env.yml`](https://github.com/uwescience/SciPy2024-GitHubActionsTutorial/blob/main/.github/workflows/python_env.yml) +[`.github/workflows/python_env.yml`](https://github.com/uwescience/GitHubActionsTutorial-USRSE24/blob/main/.github/workflows/python_env.yml) * Go to **Actions** tab @@ -14,12 +14,12 @@ Python Environment Workflow Configuration: ### Exercise: -Edit [`.github/workflows/python_env.yml`](https://github.com/uwescience/SciPy2024-GitHubActionsTutorial/blob/main/.github/workflows/python_env.yml) to install packages popular in your research. Trigger the workflow to monitor their installation. +Edit [`.github/workflows/python_env.yml`](https://github.com/uwescience/GitHubActionsTutorial-USRSE24/blob/main/.github/workflows/python_env.yml) to install packages popular in your research. Trigger the workflow to monitor their installation. ## Installing Packages with Conda We can also install packages through conda (instead of `pip`). We will use a `miniconda-setup` action to achieve that easily. -Conda Environment Workflow Configuration [`.github/workflows/conda_env.yml`](https://github.com/uwescience/SciPy2024-GitHubActionsTutorial/blob/main/.github/workflows/conda_env.yml) +Conda Environment Workflow Configuration [`.github/workflows/conda_env.yml`](https://github.com/uwescience/GitHubActionsTutorial-USRSE24/blob/main/.github/workflows/conda_env.yml) From c65edacd051a48160f03510ea4dca2eacc7408c7 Mon Sep 17 00:00:00 2001 From: Valentina Staneva Date: Mon, 7 Oct 2024 01:14:28 -0700 Subject: [PATCH 5/6] Update scheduled-algorithm-deployment-workflow.md rename repo --- docs/scheduled-algorithm-deployment-workflow.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/scheduled-algorithm-deployment-workflow.md b/docs/scheduled-algorithm-deployment-workflow.md index ceace88..4743268 100644 --- a/docs/scheduled-algorithm-deployment-workflow.md +++ b/docs/scheduled-algorithm-deployment-workflow.md @@ -4,7 +4,7 @@ Next, we will demonstrate how GitHub Actions can be used to display a spectrogram for a segment from an underwater audio stream. -Spectrogram Visualization Workflow: [`.github/workflows/noise_processing.yml`](https://github.com/uwescience/SciPy2024-GitHubActionsTutorial/blob/main/.github/workflows/noise_processing.yml) +Spectrogram Visualization Workflow: [`.github/workflows/noise_processing.yml`](https://github.com/uwescience/GitHubActionsTutorial-USRSE24/blob/main/.github/workflows/noise_processing.yml) Workflow Steps: @@ -17,6 +17,6 @@ Workflow Steps: * Upload the `.png` files to GitHub After the workflow is executed `psd.png` and `broadband.png`files are updated in the repo and are visualized below. -![alt text](https://raw.githubusercontent.com/uwescience/SciPy2024-GitHubActionsTutorial/main/ambient_sound_analysis/img/psd.png) +![alt text](https://raw.githubusercontent.com/uwescience/GitHubActionsTutorial-USRSE24/main/ambient_sound_analysis/img/psd.png) -![alt text](https://raw.githubusercontent.com/uwescience/SciPy2024-GitHubActionsTutorial/main/ambient_sound_analysis/img/broadband.png) \ No newline at end of file +![alt text](https://raw.githubusercontent.com/uwescience/GitHubActionsTutorial-USRSE24/main/ambient_sound_analysis/img/broadband.png) From 8a30925532befa646ccf7aa8bffbddae017768af Mon Sep 17 00:00:00 2001 From: Valentina Staneva Date: Mon, 7 Oct 2024 01:15:14 -0700 Subject: [PATCH 6/6] Update visualizing-results-webpage.md rename repo --- docs/visualizing-results-webpage.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/visualizing-results-webpage.md b/docs/visualizing-results-webpage.md index 834bc23..5cdc291 100644 --- a/docs/visualizing-results-webpage.md +++ b/docs/visualizing-results-webpage.md @@ -7,9 +7,9 @@ We saw it is pretty easy to continuously update results on the Readme of the rep We will demonstrate the scenario of converting a Jupyter Notebook to a webpage. -Notebook: [`plot_noise_levels.ipynb`](https://github.com/uwescience/SciPy2024-GitHubActionsTutorial/blob/main/ambient_sound_analysis/plot_noise_levels.ipynb) +Notebook: [`plot_noise_levels.ipynb`](https://github.com/uwescience/GitHubActionsTutorial-USRSE24/blob/main/ambient_sound_analysis/plot_noise_levels.ipynb) -Create Website with Spectrogram Workflow: [`.github/workflows/create_website_spectrogram.yml`](https://github.com/uwescience/SciPy2024-GitHubActionsTutorial/blob/main/.github/workflows/create_website_spectrogram.yml) +Create Website with Spectrogram Workflow: [`.github/workflows/create_website_spectrogram.yml`](https://github.com/uwescience/GitHubActionsTutorial-USRSE24/blob/main/.github/workflows/create_website_spectrogram.yml) The process consists of the following stages: @@ -25,7 +25,7 @@ The process consists of the following stages: The website can be found here: -[https://uwescience.github.io/SciPy2024-GitHubActionsTutorial/plot\_noise\_levels.html](https://uwescience.github.io/SciPy2024-GitHubActionsTutorial/plot_noise_levels.html) +[https://uwescience.github.io/GitHubActionsTutorial-USRSE24/plot\_noise\_levels.html](https://uwescience.github.io/GitHubActionsTutorial-USRSE24/plot_noise_levels.html) The procedure is set up to run on `push` thus every time the notebook is updated the website is updated. @@ -43,4 +43,4 @@ Other ways: * [Jupyterbook](https://jupyterbook.org/en/stable/publish/gh-pages.html) * [Readthedocs](https://about.readthedocs.com/?ref=readthedocs.com) * Jekyll template -* Dashboard \ No newline at end of file +* Dashboard