Installing spack repositories

[saanvi (Saanvi Deobhankar)]

Hello,

I am working on building ACCESS-ESM1.5 from source using these instructions, but I am getting an issue at the spack install step.

Spack is unable to install the GCOM and UM packages. During the build, it prompts me for my Git username/password, but although my git account is linked to ACCESS, the installation still fails. I believe it may be because these repositories are private:

• https://github.com/ACCESS-NRI/GCOM4.git
• https://github.com/ACCESS-NRI/UM_v7.git

Could I please request access to these repositories, or if there are any alternative ways to work around this issue.

Thank you in advance for any help

Kind regards,
Saanvi

[harshula]

Hi Saanvi,

I maintain ACCESS-NRI’s Spack configuration. Can you please clarify if your ultimate objective is to modify GCOM and/or UMv7 source and rebuild those components? We can then provide instructions that specifically address your requirements.

Thanks,
Harshula

[saanvi (Saanvi Deobhankar)]

Hi Harshula,

Thank you for your reply. My aim is to modify the UMv7 and CICE4.1 components.

Kind regards,
Saanvi

[anton (Anton Steketee, ACCESS-NRI Oceans Team)]

Hi Saanvi

Have you seen this post about sea ice diagnostics in esm1.5:

Issue with CICE diagnostic `dvidtt` in ACCESS-ESM / the CMIP6 pre-industrial archive

This is a limitation in the ESM1.5 coupling which means all the variables measuring a rate are incorrect in the first output after a restart. These variables which are configured to output from CICE have this issue in ESM1.5: #cmip_variable definable_in_access access_variable(s) #sfdsi no fsalt_ai aice #sidconcdyn no daidtd #sidconcth no daidtt #sidmassdyn no dvidtd #sidmassgrowthbot no congel #sidmassgrowthwat no frazil #sidmasslat no meltl #sidmassmeltbot no meltb #si…

Several of the the thermodynamics related diagnostics we ended up turning off in the ACCESS-NRI configurations. They are available in ESM1.6 now. which uses CICE5 instead. Although ESM1.6 isn’t formally released yet, it is mostly complete. We could point you to configurations and control runs to get this project started.

Either way - the build process for esm1.5 and esm1.6 is very similar.

Anton