Open ccarouge opened 3 days ago
Looking into this, it seems the spack package for esm1.6 could do with a refresh as well. See issue for the UM repo and issue for CICE5. I don't think we need to wait on the update to the spack package before getting a default deployment.
Before we can test a deployment with the generic tracers, we need a config for these (https://github.com/ACCESS-NRI/access-esm1.6-configs/issues/4) because it requires different inputs.
Maybe it is worth updating what is in main now so that it doesn't point to feature branches once the merge happens in the UM7 repo and then look at the generic tracers later.
PR #10 shows a working version of UM7 + CABLE3 in an ESM build. Once this UM code is merged in UM7 repository, we should create a default deployment PR for ESM1.6. Ideally this should also include the generic tracers from the ocean side and updates to CICE.