Created land SPINUP compsets with E3SMv3 and GSWP3 forcing

[acme-y9s]

Adding E3SMv3 forcing and generating the associated land spinup composts

[github-actions[bot]]

PR Preview Action v1.4.7 :---: :rocket: Deployed preview to https://E3SM-Project.github.io/E3SM/pr-preview/pr-6393/ on branch gh-pages at 2024-05-03 21:04 UTC

[bishtgautam]

One more follow up question: is the new DATM data already available on our public inputdata server?

[acme-y9s]

@bishtgautam Not yet! How should I deal with it? Thanks!

[bishtgautam]

On blues, the public inputdata dir is at /lcrc/group/acme/public_html/inputdata. Do you know how big is the new dataset?

[acme-y9s]

@bishtgautam It is 20-year coupler output forcing from E3SMv3 forcing which we used for land BGC SPINUP for v3 coupled simulation, which is 109G located on Chrysalis. Do you think we should upload it to the public input repository? Thanks.

[acme-y9s]

@bishtgautam @rljacob Yes, You both are right. It is what CPLHIST is for. What is the smart way to use one option CPLHIST fro different coupler output forcings? We should not specify the pathes and file names of the coupler forcings in namelist file, and will give these information in runscript file when we try to generate a case and submit a job?

[rljacob]

Still needed after #6416 ?

[rljacob]

@acme-y9s yes it should be enough to just archive the runscript that used the CPLHIST option with the specific v3 input files you used for the spinup.

[rljacob]

I'm going to propose we close this PR. The right way to preserve the ability to do the spinup is to save the runscript.

[thorntonpe]

@rljacob I agree that this can be closed.