Engelca/1135 1178 1179 improve access ram3 documentation#1181
Conversation
…emove quick guide from run-a-model run_access-ram3.md
…-ram3-configs docs.
…ause there is not much text in those sections anymore to point back to.
|
paigem
left a comment
There was a problem hiding this comment.
Thanks so much @engelca for this PR! It looks great - I think this update increases understandability noticeably - so thank you! I just suggest a couple minor wording updates, but otherwise I think this is ready to merge.
With the addition of revision in the rose/cylc page, we will want to ensure we make it clear what users should do for the revision in the docs for other models that use rose/cylc. Not in scope for this PR, but something I have noted and will action when we revamp the rose/cylc page. 😊
Co-authored-by: Paige Martin <paige.martin@anu.edu.au>
Co-authored-by: Paige Martin <paige.martin@anu.edu.au>
|
Thanks @paigem. I have accepted your two suggestions. Good point about "two" not multiple. I will update the suite to be have USE_OSTIA = False later this morning. |
|
Just a quick update to say that we will add a couple more edits to this PR before merging. |
ACCESS-Hive Docs
Description
Changes were required to the ACCESS-Hive ACCESS-rAM3 (affecting the run-a-model, model landing page and the generic rose/cylc page) to cope with removing OSTIA from the standard example AND for including the revision number in the rose/cylc checkout. The website was simplified by moving sections of text around (within pages and between pages to improve readability as well).
Fixes #1135
Fixes #1178
Please note that it introduces a inconsistency in the rose_cylc.md file that I would like to discuss because:
Still to do:
Type of change
Checklist:
- There are some broken links and I am not sure if they are new.