# Scope of ACCESS-NRI ACCESS-OM2 release **URL:** \ **Category:** COSIMA\ **Tags:** release, access-nri\ **Created:** [23 November 2022 03:41 UTC](https://forum.access-hive.org.au/t/scope-of-access-nri-access-om2-release/172 "2022-11-23T03:41:13Z")\ **Posts on this page:** 8\ **Page:** 2
**Author:** ![rmholmes](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/rmholmes/32/117_2.png) [@rmholmes](https://forum.access-hive.org.au/u/rmholmes)\ **Post date:** [9 December 2022 03:34 UTC](https://forum.access-hive.org.au/t/scope-of-access-nri-access-om2-release/172/21 "2022-12-09T03:34:38Z")
I’ve added details for the 1/4-degree and 1-degree runs that I think should be tracked in this way (i.e. major IAF runs that people will be interested in analysing, and major RYF runs that they may be interested in branching perturbations off). Nearly everything else I don’t think is worth tracking in this way (except perhaps one of Hakase’s 1-degree IAMIP runs??). I don’t think we need to add the full `metadata.yaml` description here. I feel that this is a place to give a short overview of the runs available and have links to where the data is _and where to find the configs if you want to rerun/run a perturbation_. Some details, which i don’t know, from the 1/10th are still missing. ---
**Author:** ![aekiss](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/aekiss/32/46_2.png) [@aekiss](https://forum.access-hive.org.au/u/aekiss)\ **Post date:** [30 January 2023 21:41 UTC](https://forum.access-hive.org.au/t/scope-of-access-nri-access-om2-release/172/22 "2023-01-30T21:41:31Z")
> [@Aidan](#): > > IAF restarts are every 5 years, 98 and 2003, makes planning runs more difficult. Restarts for 0.1° IAF have been saved every year (set `restart_freq: 1` in `config.yaml` and used `tidy_restarts.py` instead). ---
**Author:** ![aekiss](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/aekiss/32/46_2.png) [@aekiss](https://forum.access-hive.org.au/u/aekiss)\ **Post date:** [30 January 2023 21:45 UTC](https://forum.access-hive.org.au/t/scope-of-access-nri-access-om2-release/172/23 "2023-01-30T21:45:37Z")
> [@rmholmes](#): > > We already have these systems in the git history (manifests, hashes etc.), it’s just a matter of making this transparent for a new user (currently, they would email the person who ran the control run who would then send them links to the appropriate configuration commits and restart files). There’s already some instructions [here](https://github.com/COSIMA/access-om2/wiki/Tutorials#starting-a-new-experiment-using-restarts-from-a-previous-experiment) but I agree this could be done in a more automated way. ---
**Author:** ![aekiss](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/aekiss/32/46_2.png) [@aekiss](https://forum.access-hive.org.au/u/aekiss)\ **Post date:** [30 January 2023 21:55 UTC](https://forum.access-hive.org.au/t/scope-of-access-nri-access-om2-release/172/24 "2023-01-30T21:55:30Z")
I’m not sure how many experiments used [`sync_data.sh`](https://github.com/COSIMA/01deg_jra55_iaf/blob/master/sync_data.sh) to copy the outputs from `/scratch`, but those that did will have a [run summary](https://github.com/aekiss/run_summary) .csv and a clone of the git history (git-runlog) in the same location as the output file. This should provide everything that’s needed to re-do or branch a run from any point. ---
**Author:** ![rmholmes](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/rmholmes/32/117_2.png) [@rmholmes](https://forum.access-hive.org.au/u/rmholmes)\ **Post date:** [30 January 2023 22:43 UTC](https://forum.access-hive.org.au/t/scope-of-access-nri-access-om2-release/172/25 "2023-01-30T22:43:09Z")
@aekiss in other words, we should all just read the instructions! That automatic `git-runlog` sync is great. I’ve added a short paragraph at the beginning of the tutorial indicating different ways in which the configuration files for the previous experiment can be found. See the start of [Tutorials · COSIMA/access-om2 Wiki · GitHub](https://github.com/COSIMA/access-om2/wiki/Tutorials#starting-a-new-experiment-using-restarts-from-a-previous-experiment) @aekiss can you check it please? Of course, the `git-runlog` won’t help if people aren’t using `sync_data.sh`. A quick check with find suggests that there are quite a few experiments where this is the case, including important runs such as `01deg_jra55v13_ryf9091` and all the 1-degree OMIP runs. These should be fixed if possible. ---
**Author:** ![aekiss](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/aekiss/32/46_2.png) [@aekiss](https://forum.access-hive.org.au/u/aekiss)\ **Post date:** [31 January 2023 03:26 UTC](https://forum.access-hive.org.au/t/scope-of-access-nri-access-om2-release/172/26 "2023-01-31T03:26:32Z")
Thanks @rmholmes, I’ve added some extra detail, and also at steps 1 and 4 - does that make sense? ---
**Author:** ![aekiss](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/aekiss/32/46_2.png) [@aekiss](https://forum.access-hive.org.au/u/aekiss)\ **Post date:** [31 January 2023 03:38 UTC](https://forum.access-hive.org.au/t/scope-of-access-nri-access-om2-release/172/27 "2023-01-31T03:38:53Z")
I’m also updating `/g/data/hh5/tmp/cosima/access-om2-run-summaries` for the first time in years. The list of runs summarised is in `do-run-summaries`. This is far from comprehensive and I’m not sure it’s the best approach. ---
**Author:** ![rmholmes](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/rmholmes/32/117_2.png) [@rmholmes](https://forum.access-hive.org.au/u/rmholmes)\ **Post date:** [31 January 2023 05:25 UTC](https://forum.access-hive.org.au/t/scope-of-access-nri-access-om2-release/172/28 "2023-01-31T05:25:36Z")
> [@aekiss](#): > > Thanks @rmholmes, I’ve added some extra detail, and also at steps 1 and 4 - does that make sense? Looks good to me, thanks! [Previous page](https://forum.access-hive.org.au/t/scope-of-access-nri-access-om2-release/172.md?page=1)