Data

Tools

Indexes

Applications

Experiments

Open Source Science

cape-k-wildfires

Cookbook for the wildfires observed at CAPE-k from the CAPE-k student workshop

https://github.com/arm-synergy/cape-k-wildfires

Science Score: 67.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • ✓
    CITATION.cff file
    Found CITATION.cff file
  • ✓
    codemeta.json file
    Found codemeta.json file
  • ✓
    .zenodo.json file
    Found .zenodo.json file
  • ✓
    DOI references
    Found 2 DOI reference(s) in README
  • ✓
    Academic publication links
    Links to: zenodo.org
  • ○
    Academic email domains
  • ○
    Institutional organization owner
  • ○
    JOSS paper metadata
  • ○
    Scientific vocabulary similarity
    Low similarity (13.9%) to scientific vocabulary
Last synced: 6 months ago · JSON representation ·

Repository

Cookbook for the wildfires observed at CAPE-k from the CAPE-k student workshop

Basic Info
Statistics
  • Stars: 0
  • Watchers: 1
  • Forks: 6
  • Open Issues: 2
  • Releases: 2
Created about 1 year ago · Last pushed 8 months ago
Metadata Files
Readme License Citation

README.md

thumbnail

Cape-k Wildfire Cookbook

nightly-build Binder DOI

This Project Pythia Cookbook covers Analysis of a Wildfire event sampled at Kennaook Cape Grim during CAPE-k

Motivation

(Add a few sentences stating why this cookbook will be useful. What skills will you, "the chef", gain once you have reached the end of the cookbook?)

Authors

First Author, Second Author, etc. Acknowledge primary content authors here

Contributors

Structure

(State one or more sections that will comprise the notebook. E.g., This cookbook is broken up into two main sections - "Foundations" and "Example Workflows." Then, describe each section below.)

Section 1 ( Replace with the title of this section, e.g. "Foundations" )

(Add content for this section, e.g., "The foundational content includes ... ")

Section 2 ( Replace with the title of this section, e.g. "Example workflows" )

(Add content for this section, e.g., "Example workflows include ... ")

Running the Notebooks

You can either run the notebook using Binder or on your local machine.

Running on Binder

The simplest way to interact with a Jupyter Notebook is through Binder, which enables the execution of a Jupyter Book in the cloud. The details of how this works are not important for now. All you need to know is how to launch a Pythia Cookbooks chapter via Binder. Simply navigate your mouse to the top right corner of the book chapter you are viewing and click on the rocket ship icon, (see figure below), and be sure to select “launch Binder”. After a moment you should be presented with a notebook that you can interact with. I.e. you’ll be able to execute and even change the example programs. You’ll see that the code cells have no output at first, until you execute them by pressing {kbd}Shift+{kbd}Enter. Complete details on how to interact with a live Jupyter notebook are described in Getting Started with Jupyter.

Running on Your Own Machine

If you are interested in running this material locally on your computer, you will need to follow this workflow:

(Replace "cookbook-example" with the title of your cookbooks)

  1. Clone the https://github.com/ProjectPythia/cookbook-example repository:

bash git clone https://github.com/ProjectPythia/cookbook-example.git

  1. Move into the cookbook-example directory bash cd cookbook-example
  2. Create and activate your conda environment from the environment.yml file bash conda env create -f environment.yml conda activate cookbook-example
  3. Move into the notebooks directory and start up Jupyterlab bash cd notebooks/ jupyter lab

Owner

  • Name: Atmospheric Radiation Measurement user facility
  • Login: ARM-Synergy
  • Kind: organization

Citation (CITATION.cff) 

title: "CAPE-k Wildfire Analysis"
cff-version: 1.2.0
message: "If you use this cookbook, please cite it as below."
abstract: "Student analysis focused on wildfires observed at the CAPE-k site."
authors:
  # add additional entries for each author -- see https://github.com/citation-file-format/citation-file-format/blob/main/schema-guide.md
  - family-names: Paton Walsh
    given-names: Clare
    orcid: https://orcid.org/0000-0003-1156-4138
    website: https://github.com/clarepw
    affiliation: University of Wollongong
  - family-names: Shende
    given-names: Prashasti
    orcid: https://orcid.org/0009-0009-5577-0647
    website: https://github.com/shendeprashasti
    affiliation: University of Melbourne 
  - family-names: Jandl
    given-names: Ida
    orcid: https://orcid.org/0009-0000-3636-6651
    website: https://github.com/Ida-droid
    affiliation: University of Melbourne
  - family-names: Sodano
    given-names: Salvatore
    orcid: https://orcid.org/0009-0001-8641-7434
    website: https://github.com/SalvatoreSodano
    affiliation: University of Tasmania
  - family-names: Nawaz
    given-names: Hasan
    orcid: https://orcid.org/0000-0003-3009-6472
    website: https://github.com/hasan92nawaz
    affiliation: University of Wollongong
  - family-names: Roy
    given-names: Deepa
    website: https://github.com/deepa707
    affiliation: University of Wollongong
  - family-names: Burgess
    given-names: Luke
    orcid: https://orcid.org/0009-0004-2660-4870
    website: https://github.com/LukeBurgessClimate
    affiliation: University of Melbourne

GitHub Events

Total
  • Release event: 5
  • Member event: 5
  • Issue comment event: 9
  • Push event: 20
  • Pull request review event: 3
  • Pull request event: 20
  • Fork event: 6
  • Create event: 7
Last Year
  • Release event: 5
  • Member event: 5
  • Issue comment event: 9
  • Push event: 20
  • Pull request review event: 3
  • Pull request event: 20
  • Fork event: 6
  • Create event: 7

Issues and Pull Requests

Last synced: 6 months ago

All Time
  • Total issues: 0
  • Total pull requests: 10
  • Average time to close issues: N/A
  • Average time to close pull requests: about 9 hours
  • Total issue authors: 0
  • Total pull request authors: 7
  • Average comments per issue: 0
  • Average comments per pull request: 0.7
  • Merged pull requests: 5
  • Bot issues: 0
  • Bot pull requests: 1
Past Year
  • Issues: 0
  • Pull requests: 10
  • Average time to close issues: N/A
  • Average time to close pull requests: about 9 hours
  • Issue authors: 0
  • Pull request authors: 7
  • Average comments per issue: 0
  • Average comments per pull request: 0.7
  • Merged pull requests: 5
  • Bot issues: 0
  • Bot pull requests: 1
View more stats
Top Authors
Issue Authors
Pull Request Authors
  • hasan92nawaz (4)
  • LukeBurgessClimate (1)
  • Ida-droid (1)
  • shendeprashasti (1)
  • SalvatoreSodano (1)
  • clarepw (1)
  • dependabot[bot] (1)
Top Labels
Issue Labels
Pull Request Labels
dependencies (1) github_actions (1)

Dependencies

.github/workflows/nightly-build.yaml actions
.github/workflows/publish-book.yaml actions
.github/workflows/trigger-book-build.yaml actions
.github/workflows/trigger-delete-preview.yaml actions
.github/workflows/trigger-link-check.yaml actions
.github/workflows/trigger-preview.yaml actions
.github/workflows/trigger-replace-links.yaml actions
  • actions/checkout v4 composite
  • jacobtomlinson/gha-find-replace v3 composite
  • stefanzweifel/git-auto-commit-action v5 composite
environment.yml pypi