update model version of NorESM-LSP

[evalieungh]

Hi! Can we try and coordinate testing and updating the LSP with newer model versions of CTSM and FATES?

I'm curious whether Jeanne R in Bergen (what is her github username?) has been tasked with doing something with the LSP. @lasseke, @mvdebolskiy should also be in the loop I think.

Sloooowly I'm going to try running FATES again, stubbornly through the LSP. I need to run new simulations for a manuscript, and want to try updating the model versions first.

But which versions to use?

Relevant issue for how to update: NorESMhub/noresm-land-sites-platform#161

[mvdebolskiy]

What ctsm and/or fates tag do you need run? There lots of changes have to be done with the input data and the way cime/ccs_config overwrites.

[lasseke]

Hey! If you want to update the CTSM version globally for the LSP and ctsm-api, this should be the line you need to update if I am not mistaken:

https://github.com/NorESMhub/ctsm-api/blob/651907a0cd8299d961a7f0d2f61b4aea13469b46/app/core/config.py#L26

It is also possible to overwrite this setting via .env files, if I understand it correctly after a quick overview:
https://github.com/NorESMhub/noresm-land-sites-platform/blob/ebc02d97148da2b4a388c2bbd1c0bfce8a2c5246/docker/api/.env#L8
or
https://github.com/NorESMhub/ctsm-api/blob/651907a0cd8299d961a7f0d2f61b4aea13469b46/env-example#L7 (this one is just an example and will not have any effect, so no need to change anything here)

You'd also need to update the docker containers afterward, so everything probably requires quite a bit of trial-and-error debugging.

If you want a specific FATES version different from the one specified in the updated CTSM release tag, you must additionally specify it as described in your link.

[mvdebolskiy]

Also, versions after 5.2 won't work due to the different way the components are checked out.