Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why CICE in ACCESS-OM2 driven by Auscom while ACCESS driver exists? #73

Open
VanuatuN opened this issue May 27, 2024 · 2 comments
Open

Comments

@VanuatuN
Copy link

Dear all,

Makefile for CICE says e.g.

01deg:
bld/build.sh $(platform) auscom 3600x2700

While in the folder "drivers" we have an access driver.
I'm wondering why would be need an access driver then?

Thank you in advance for any clarifications!
Natalia

@VanuatuN VanuatuN changed the title Why CICE driven by Auscom while ACCESS driver exists? Why CICE in ACCESS-OM2 driven by Auscom while ACCESS driver exists? May 27, 2024
@aekiss
Copy link
Contributor

aekiss commented May 27, 2024

The model components in ACCESS-OM2 are also used in the ACCESS-CM2 climate model (with an active atmosphere and land surface). These applications require different drivers for CICE (confusingly named "auscom" for ACCESS-OM2, "access" for ACCESS-CM2, for historical reasons*) and so require different build options.

*this document describes a much earlier implementation than the current ACCESS-OM2 and ACCESS-CM2

@VanuatuN
Copy link
Author

Thank you! All clear now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants