Goal: Update the following figure to CMIP6 data (from this paper)
Teammates: you will want to "Fork" the project, and then "clone" your fork to your local computer (more on forking and cloning). Then later you can merge your changes back to your remote fork, and from there back to the main branch.
Once the initial setup is done, everyone will want to clone the repository onto the compute system they plan to use for the hackathon.
- Open a JupyterLab session on the system you plan to use.
- Open a terminal in the JupyterLab environment.
- Clone your project:
git clone https://github.com/apendergrass/cmip6hack-precip.git - Get to work!
The CMIP6 Hackathon template provides a starting point for CMIP6 Hackathon projects.
catalogs: data catalogs that can be used by Intake-ESM.environments: Conda environment files for the NCAR/Google Cloud deployments.notebooks: a place for storing Jupyter Notebooks.README.md: this document - consider modifying to make it a description of your project on GitHub.LICENSE: a default (MIT) license file for your project. You can change this if you feel the need.
Project leads should follow the next four steps. This only needs to be done once.
- Navigate to https://github.com/cmip6hack/project-template
- Click the "Use this template" button
- Name your project (consider prepending with "cmip6hack", so something like
cmip6hack-myproject) - Provide a brief description
- Tell your teammates where to find your repository and tell them to "Fork" the project.
Once the initial setup is done, everyone will want to clone the repository onto the compute system they plan to use for the hackathon.
- Open a JupyterLab session on the system you plan to use.
- Open a terminal in the JupyterLab environment.
- Clone your project:
git clone https://github.com/username/cmip6hack-myproject.git - Get to work!
Zenodo is a data archiving tool that can help make your project citable by assigning a DOI to the project's GitHub repository.
Follow the guidelines here https://guides.github.com/activities/citable-code