access-enso-recipes
Recipes and metrics for evaluating ENSO in ACCESS
Science Score: 49.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
✓DOI references
Found 8 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 (14.1%) to scientific vocabulary
Keywords
Repository
Recipes and metrics for evaluating ENSO in ACCESS
Basic Info
Statistics
- Stars: 4
- Watchers: 4
- Forks: 1
- Open Issues: 8
- Releases: 3
Topics
Metadata Files
README.md
ACCESS-ENSO-Recipes (El Nio-Southern Oscillation)
Overview
The ACCESS-ENSO-Recipes package is a collection of Jupyter notebooks designed to reproduce the metrics described in the CLIVAR 2020 ENSO Metrics Package. These metrics are based on the methodology outlined by Planton et al. (2021) (DOI:10.1175/BAMS-D-19-0337.1) and implemented following the instructions provided by Yann Planton.
This package integrates with ESMValTool, utilising its preprocessors to streamline analysis. Users can explore the ENSO metrics interactively in Jupyter notebooks or execute them as an ESMValTool recipe for batch processing.
Key Features:
- Reproduction of ENSO metrics from the CLIVAR 2020 ENSO Metrics Package.
- Simplified diagnostics for integration into ESMValTool.
- Support for interactive exploration in Jupyter notebooks or execution via ESMValTool recipes.
- Configured for use on NCI Gadi with the ACCESS-NRI conda environment.
What is ESMValTool?
The Earth System Model Evaluation Tool (ESMValTool) is a community-developed software package for the evaluation of Earth System Models (ESMs).
For more information, visit the official ESMValTool website.
Requirements
To use the ACCESS-ENSO-Recipes, ensure the following:
Environment:
- Access to NCI Gadi.
- The ACCESS-NRI conda environment pre-configured with the esmvaltool-workflow.
How to Use on ARE (Australian Research Environment)
1. Open ARE on Gadi
Go to the Australian Research Environment website and login with your NCI username and password. If you don't have an NCI account, you can sign up for one at the MyNCI website.

2. Start JupyterLab App
Click on JupyterLab under Featured Apps to configure a new JupyterLab instance. This option is also available under the All Apps section at the bottom of the page and the Interactive Apps dropdown located in the top menu.

3. Configure JupyterLab session
You will now be presented with the main JupyterLab instance configuration form. Please complete only the fields below - leave all other fields blank or to their default values.
- 3.1 Walltime: The number of hours the JupyterLab instance will run. For the hackathon, please insert a walltime of
4hours.

- 3.2 Compute Size: Select
Medium (4 cpus, 18G mem)from the dropdown menu.

- 3.3 Project: Please enter
nf33. This will allocate SU usage to the workshop project.

- 3.4 Storage: In ARE, storage locations need to be explicitly defined to access these data from within a JupyterLab instance.
Please copy and paste the following string in its entirety into the storage input field:
gdata/xp65+gdata/fs38+gdata/oi10+gdata/al33+gdata/rr3+gdata/rt52+gdata/zz93+gdata/ct11+gdata/zv30

3.5 Click
Advanced options ...- Optional: You can check the box here to receive an email notification when your JupyterLab instance starts, but as we are running a relatively small instance, it will likely spin up quickly so this probably isn't necessary.
3.6 Module directories: To load the required environment modules, please copy and paste the following. This is equivalent to using
module useon the command line./g/data/xp65/public/modules

- 3.7 Modules To load the ESMValTool-workflow environment, please copy and paste the following. This is equivalent to using
module loadon the command line.conda/analysis3

- 3.7 Click
Launchto start your JupyterLab instance.

4. Launch JupyterLab session
Once you have clicked Launch the browser will redirect to the 'interactive sessions' page where you will see your JupyterLab instance details and current status which will look something like this:

Once the JupyterLab instance has started (this usually takes around 30 seconds), this status window should update and look something like the following, reporting that the instance has started and the time remaining. More detailed information on the instance can be accessed by clicking the Session ID link.

Click Open JupyterLab. This opens the instance in a new browser window where you can navigate to the location of the files.
Feedback and Support
This package is maintained by the ACCESS-NRI Model Evaluation and Diagnostics Team. For issues, suggestions, or assistance, please contact ACCESS-NRI support.
We welcome contributions! Please follow the contribution guidelines to submit enhancements or bug fixes.
References
- CLIVAR 2020 ENSO Metrics Package: CLIVAR Website
- Planton et al. (2021): DOI:10.1175/BAMS-D-19-0337.1
- ESMValTool: ESMValTool Official Website
Owner
- Name: ACCESS-NRI
- Login: ACCESS-NRI
- Kind: organization
- Email: access.nri@anu.edu.au
- Website: https://www.access-nri.org.au/
- Repositories: 17
- Profile: https://github.com/ACCESS-NRI
Australian Earth System Simulator - National Research Infrastructure
GitHub Events
Total
- Create event: 85
- Release event: 3
- Issues event: 19
- Watch event: 4
- Delete event: 59
- Member event: 2
- Issue comment event: 78
- Push event: 165
- Pull request review comment event: 4
- Pull request review event: 7
- Pull request event: 114
- Fork event: 1
Last Year
- Create event: 85
- Release event: 3
- Issues event: 19
- Watch event: 4
- Delete event: 59
- Member event: 2
- Issue comment event: 78
- Push event: 165
- Pull request review comment event: 4
- Pull request review event: 7
- Pull request event: 114
- Fork event: 1
Issues and Pull Requests
Last synced: 6 months ago
All Time
- Total issues: 9
- Total pull requests: 60
- Average time to close issues: 3 months
- Average time to close pull requests: 27 days
- Total issue authors: 3
- Total pull request authors: 3
- Average comments per issue: 0.11
- Average comments per pull request: 0.77
- Merged pull requests: 40
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 9
- Pull requests: 60
- Average time to close issues: 3 months
- Average time to close pull requests: 27 days
- Issue authors: 3
- Pull request authors: 3
- Average comments per issue: 0.11
- Average comments per pull request: 0.77
- Merged pull requests: 40
- Bot issues: 0
- Bot pull requests: 0
Top Authors
Issue Authors
- rbeucher (7)
- flicj191 (1)
- rhaegar325 (1)
Pull Request Authors
- rbeucher (38)
- flicj191 (21)
- rhaegar325 (1)