Context
Following the AM3 atmosphere evaluation discussion, we need to check whether ACCESS-MOPPy can CMORise AM3 outputs for downstream evaluation workflows.
The initial use case is running existing atmosphere/coupled-model evaluation analyses on AM3 outputs, including ENSO Recipes / notebooks 1, 2, 3, 5, 6, and 8. Some of these analyses require CMORised data, and AM3 CMORisation work is expected to be needed for CMIP-related workflows anyway.
Proposed checks
- Identify the AM3 output structure and available variables for the candidate simulations.
- Check whether ACCESS-MOPPy can ingest AM3 outputs directly.
- Check whether required atmosphere variables can be mapped/derived for the evaluation scripts and ENSO recipes.
- Identify any missing vocabularies, grid/time handling, metadata, or variable derivation support.
- Document the minimum changes needed for AM3 CMORisation support.
- If feasible, add a small test/example configuration using representative AM3 sample data.
Related evaluation workflow
This links to the broader goal of having a reusable atmosphere evaluation workflow/script that can be run for each new AM3 simulation. It also connects to the need for an AM3 builder in the ACCESS-NRI Intake Catalogue so AM3 outputs are easier to discover and use.
Context
Following the AM3 atmosphere evaluation discussion, we need to check whether ACCESS-MOPPy can CMORise AM3 outputs for downstream evaluation workflows.
The initial use case is running existing atmosphere/coupled-model evaluation analyses on AM3 outputs, including ENSO Recipes / notebooks 1, 2, 3, 5, 6, and 8. Some of these analyses require CMORised data, and AM3 CMORisation work is expected to be needed for CMIP-related workflows anyway.
Proposed checks
Related evaluation workflow
This links to the broader goal of having a reusable atmosphere evaluation workflow/script that can be run for each new AM3 simulation. It also connects to the need for an AM3 builder in the ACCESS-NRI Intake Catalogue so AM3 outputs are easier to discover and use.