how to run ACCESS-OM3 and ACCESS-OM3 specification documentation #893
Conversation
chrisb13
requested review from
atteggiani,
anton-seaice,
heidinett and
helenmacdonald
|
… just removed the offending text
chrisb13
force-pushed
the
cbull/run-ACCESS-OM3
branch
from
b354647 to
15c4f70
Compare
There was a problem hiding this comment.
@chrisb13 I haven't yet fixed the section on changing the runtime. I will tonight, but in the meantime here are some other things to fix.
Applying @dougiesquire's code review suggestions for how to run om3, further changes to follow that require tailored edits. Co-authored-by: Dougie Squire <[email protected]>
Co-authored-by: Anton Steketee <[email protected]>
Adding suggestions made by @dougiesquire and @anton-seaice. Co-authored-by: Dougie Squire <[email protected]> Co-authored-by: Anton Steketee <[email protected]>
|
@dougiesquire / @atteggiani now ready for review. |
|
Thank you @chrisb13! I marked it as "ready for review", and I'll get to it sometimes around tomorrow or on Wednesday. |
| [Run ACCESS-OM](/models/run-a-model/run-access-om){: class="text-card"} |
There was a problem hiding this comment.
Should this be changed to Run ACCESS-OM2? And should a Run ACCESS-OM3 button be added further up?
| !!! warning | ||
| BGC experiments are slower and generally consume more resources (compute time and disk space). | ||
|
|
||
| ### Model Components | ||
| <div class="tabLabels" label="ACCESS-OM2-versions"> | ||
| <button id="1deg">ACCESS-OM2</button> | ||
| <button id="1deg">ACCESS-OM2-1</button> |
There was a problem hiding this comment.
There are issues with the spatial resolutions being rendered in this table. I also don't really understand what these tables add...
| CICE6 is used in ACCESS-OM3 which is under active development. |
There was a problem hiding this comment.
| CICE6 is used in ACCESS-OM3 which is under active development. | |
| CICE6 is used in [ACCESS-OM3](/models/configurations/access-cm#access-om3) which is under active development. |
| - **Join the _vk83_, _xp65_ and _qv56_ projects at NCI**<br> | ||
| To join these projects, request membership on the respective [vk83](https://my.nci.org.au/mancini/project/vk83/join), [xp65](https://my.nci.org.au/mancini/project/xp65/join) and [qv56](https://my.nci.org.au/mancini/project/qv56/join) NCI project pages.<br> |
There was a problem hiding this comment.
As mentioned previously, this isn't strictly needed for ACCESS-OM2 at the moment. But I guess no harm in having people join this project.
| More information about the available experiments and the naming scheme of the branches can also be found in the [{{ model }} configs]({{ github_configs }}) GitHub repository. | ||
|
|
||
| The first step is to choose a configuration from those available.<br> | ||
| For example, if the required configuration is the 1° horizontal resolution with repeat-year _JRA55_ forcing (without BGC), then the branch to select is [`dev-1deg_jra55do_ryf`](https://github.com/ACCESS-NRI/access-om3-configs/tree/dev-1deg_jra55do_ryf). |
There was a problem hiding this comment.
This whole page needs to be updated for the new branch naming, e.g.dev-MC_1deg_jra_ryf
For the upcoming ACCESS-OM3 025 alpha release this is for the related documentation
This is the related issue.
NB: not looking for a review just yet!