# ACCESS-OM3 25km 1.0-beta Feedback **URL:** \ **Category:** COSIMA\ **Tags:** access-om3, feedback, beta\ **Created:** [17 July 2025 23:31 UTC](https://forum.access-hive.org.au/t/access-om3-25km-1-0-beta-feedback/4719 "2025-07-17T23:31:33Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![anton](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/anton/32/1836_2.png) [@anton](https://forum.access-hive.org.au/u/anton)\ **Post date:** [17 July 2025 23:31 UTC](https://forum.access-hive.org.au/t/access-om3-25km-1-0-beta-feedback/4719/1 "2025-07-17T23:31:33Z")
# About This topic is a catch-all location for feedback for the [ACCESS-OM3 25km RYF 1.0-beta Release](https://forum.access-hive.org.au/t/access-om3-release-information/4494). Please reply to this topic if you have feedback on the ACCESS-OM3 release. Feedback can be to point out problems encountered, or positive to highlight what worked well. If your feedback is involved and will require specific #help feel free to [make a topic on the ACCESS-Hive Forum](https://forum.access-hive.org.au/new-topic?category=cosima&tags=help,beta,feedback,access-om3). If you’re not sure, reply here and your query can be moved to a separate topic if required. ---
**Author:** ![wghuneke](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/wghuneke/32/102_2.png) [@wghuneke](https://forum.access-hive.org.au/u/wghuneke)\ **Post date:** [4 August 2025 04:09 UTC](https://forum.access-hive.org.au/t/access-om3-25km-1-0-beta-feedback/4719/2 "2025-08-04T04:09:56Z")
Thanks to everyone involved in setting up OM3-25km, it’s great to have the beta version available now! I had a look at the instructions [how to run the model](https://docs.access-hive.org.au/models/run-a-model/run-access-om3/) and did a 1 year test run - it worked well. Below is minor feedback I have on the instructions, having new users in mind. Overall, it’s really clear and with a good balance regarding the information load. - Under “Download and run ACCESS-OM3 configuration” → laboratory directory: could add information that it will be created when the model is run/payu setup. I.e. not when downloading the code. - worth noting that the experiment name will look slightly different in /archive, something like \*-expt-9fs89ef8, I believe this comes from payu/version control? - “Change run length” link does not work (redirects to top of page). - Green box under “Run configuration“: Maybe worth re-iterating that the model won’t run if there is a work directory? (for people who only read the boxes…) - typo: “Edit ACCESS-OM3 configuration“: first sentence needs an “a” - typo: The run length is controlled by “stop\_option” (empty space missing) - Regarding the restart options: I think the text could be clearer here, in particular on the difference between “restart period” and “restart\_frq” (mentioned further down). I don’t have a good suggestion right now on how to change it though. - typo - full stop missing in paragraph “However, …” under “Pruning model restarts” - “Other configuration options“: I think the phrasing here could be more positive/supportive. It sounds a little like this is only something for more experienced people and is rarely done. However, I cannot think of many use cases where someone will want to learn how to run the model to only run the standard control case - that model output is available already. I understand that each perturbation is unique, and detailed info on manipulating the code is out of scope for this tutorial. But I think it would be nice to acknowledge that most (all?) people will want to change something, e.g. by listing common perturbations (changing the input files, parameterisations, vertical grid, …?) + giving a link to the OM3 configuration where more detailed info is given. ---
**Author:** ![cbull](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/cbull/32/2203_2.png) [@cbull](https://forum.access-hive.org.au/u/cbull)\ **Post date:** [25 August 2025 06:52 UTC](https://forum.access-hive.org.au/t/access-om3-25km-1-0-beta-feedback/4719/3 "2025-08-25T06:52:46Z")
Hi @wghuneke, thanks very much for your feedback! These kinds of comments really lead to a better full release down the road. [We’ve set up an issue](https://github.com/ACCESS-NRI/access-hive.org.au/issues/983) to action this feedback but do get in touch if you’d like to provide further feedback or discussion on how your suggestions are implemented. ---
**Author:** ![dougiesquire](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/dougiesquire/32/16_2.png) [@dougiesquire](https://forum.access-hive.org.au/u/dougiesquire)\ **Post date:** [25 August 2025 06:54 UTC](https://forum.access-hive.org.au/t/access-om3-25km-1-0-beta-feedback/4719/4 "2025-08-25T06:54:41Z")
Note that there is a bug in the version of MOM6 used in the `release-MC_25km_jra_ryf-1.0-beta` configuration that means that the scalar diagnostics of global/area mean temperature and salinity are the model prognostic temperature and salinity, but are always reported as potential temperature and practical salinity. The following diagnostics included by default in the `release-MC_25km_jra_ryf-1.0-beta` configuration are affected: - `thetaoga` (long\_name: “Global Mean Ocean Potential Temperature”) is actually conservative temperature - `tosga` (long\_name: “Global Area Average Sea Surface Temperature”) is actually conservative temperature - `soga` (long\_name: “Global Mean Ocean Salinity”) is actually absolute salinity - `sosga` (long\_name: “Global Area Average Sea Surface Salinity”) is actually absolute salinity A [fix for this bug](https://github.com/NOAA-GFDL/MOM6/pull/860) has already been implemented in MOM6 and will be included in the next ACCESS-OM3 release