Example recipes using the cosima-cookbook
infrastructure.
To Get Started with the cosima-cookbook
, clone this repository locally, probably best in your local space on one of the NCI HPC machines so you can have access to model output. The repository includes a bunch of examples with which you can begin to construct your own analysis code.
If you made a notebook for analysing something that is not already included in the recipes, then please consider contributing back to the repository.
To make a contribution follow the steps laid out in the beginner's guide on how to contribute. If they sound intimidating then don't worry! Just raise an issue explaining briefly what the contribution you want to make is and we'll help out with the process!
The notebook COSIMA_CookBook_Tutorial.ipynb
outlines the basic philosophy of the cosima-cookbook
. This is the best place to start if you are not familiar with the cosima-cookbook
. Also included here are some other tutorials, either related to the cookbook (e.g., Make_Your_Own_Database.ipynb
) or more general (Making_Maps_with_Cartopy.ipynb
).
Don't miss out the tutorial about using cosima-cookbook
's explore
submodule to find out about available experiments and variables in a database. (The explorer
tutorial is better viewed either via nbviewer or by running the jupyter notebook yourself.)
Νotebooks for simple and not-so-simple diagnostics which are well-documented and explained. If you can find an example that suits your purpose, this is the best place to start.
Νotebooks to reproduce (as far as possible) the figures from the ACCESS-OM2 model announcement paper (GMD, 2020). These notebooks are mostly uncommented, but they should be functional. They are intended to demonstrate methods to undertake the calculations used in the paper.
Α number of examples which are valuable, but not commented sufficiently to make it into DocumentedExamples. An aspirational goal is to eliminate this class of example.
Α hotch-potch of old contributed files that may or not be useful or operational. Use at your own risk!