Skip to content

Conversation

@chrisb13
Copy link
Contributor

First hacky go at how to run access esm 1.6 doc

Given their similarity the plan is for this doc to cover both esm1.5/1.6.

@chrisb13 chrisb13 requested a review from a team June 27, 2025 01:22
@github-actions
Copy link

github-actions bot commented Jun 27, 2025

PR Preview
🚀 Preview of PR head commit 9faaba5 deployed to https://docs.access-hive.org.au/pr-previews/957
2025-10-29 11:21 AEDT
Preview generated through the Deploy to GitHub Pages workflow run 18893059543.

Comment on lines 1 to 4
{% set model = "ACCESS-ESM1.5" %}
{% set model2 = "ACCESS-ESM1.6" %}
{% set github_configs = "https://github.com/ACCESS-NRI/access-esm1.5-configs" %}
{% set release_notes = "https://forum.access-hive.org.au/t/access-esm1-5-release-information/2352" %}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would use the model version to distinguish the tags. It means more changes to update the tag for ESM1.5 in the whole page but it's less confusing to use (model2 for 1.6 type of confusion??) Don't accept the suggestion as is without doing the work to update throughout the page.

And we also need an URL for ESM1.6 config repo URL. We don't need the release notes yet, but may as well be consistent right now.

Suggested change
{% set model = "ACCESS-ESM1.5" %}
{% set model2 = "ACCESS-ESM1.6" %}
{% set github_configs = "https://github.com/ACCESS-NRI/access-esm1.5-configs" %}
{% set release_notes = "https://forum.access-hive.org.au/t/access-esm1-5-release-information/2352" %}
{% set model_1.5 = "ACCESS-ESM1.5" %}
{% set model_1.6 = "ACCESS-ESM1.6" %}
{% set github_configs_1.5 = "https://github.com/ACCESS-NRI/access-esm1.5-configs" %}
{% set github_configs_1.6 = "https://github.com/ACCESS-NRI/access-esm1.6-configs" %}
{% set release_notes_1.5 = "https://forum.access-hive.org.au/t/access-esm1-5-release-information/2352" %}

@@ -129,6 +132,26 @@ to a new experiment branch (`-b expt`) to a directory named `preindustrial+conce

----------------------------------------------------------------------------------------

## Get {{ model2 }} configuration
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would fold this section with the previous one and use a tab (example) to show the commands for ESM1.5 or ESM1.6.

I know we can't say we have tested etc. But as you said, this won't be published, it is only a WIP that we can share when we need to.


mkdir -p ~/access-esm1.6
cd ~/access-esm1.6
payu clone -b expt -B dev-preindustrial+concentrations [{{ github_configs }}](https://github.com/ACCESS-NRI/access-esm1.6-configs.git) preindustrial+concentrations
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No hyperlinks in code blocks!!

Suggested change
payu clone -b expt -B dev-preindustrial+concentrations [{{ github_configs }}](https://github.com/ACCESS-NRI/access-esm1.6-configs.git) preindustrial+concentrations
payu clone -b expt -B dev-preindustrial+concentrations https://github.com/ACCESS-NRI/access-esm1.6-configs.git preindustrial+concentrations

!!! tip
Downloading and running {{ model2 }} is very similar to {{ model }}, here we show the key difference for how to run {{ model2 }} as compared to running {{ model1 }} .

All released {{ model2 }} configurations are available from the [{{ model2 }} configs](https://github.com/aCCESS-NRI/accESS-esm1.6-configs) GitHub repository.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should use github_configs_1.6 for the link!

@ccarouge
Copy link
Member

@chrisb13 .
One more comment, the presence of the labels at the start of the page (model, github_configs...) makes me wonder if the intent is different. Should we go with 2 pages and simply change the labels at the top to have a working instruction page. It would be less work and probably less confusing to users?

Just a thought.

@github-actions
Copy link

github-actions bot commented Oct 24, 2025

PR Preview
🚀 Preview of PR head commit f441a8d deployed to https://docs.access-hive.org.au/pr-previews/957
2026-01-20 17:22 AEDT
Preview generated through the Deploy to GitHub Pages workflow run 21161603766.

@anton-seaice anton-seaice removed their assignment Oct 24, 2025
First hacky go at how to run access esm 1.6 doc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

6 participants