choose a F compset to compare with B1850

[zhaos]

Hello,

I am a new user to CESM. I have a naive question: Is there a defined F compset to compare with B1850? My study purpose is to examine the role of ocean dynamics in tropical rainfall.

I found two defined F1850 compset:
F1850, 1850_CAM60_CLM50%SP_CICE%PRES_DOCN%DOM_MOSART_CISM2%NOEVOLVE_SWAV
F1850_BDRD, 1850_CAM60_CLM50%BGC_CICE%PRES_DOCN%DOM_MOSART_CISM2%NOEVOLVE_SWAV_BGC%BDRD
And the long name for B1850 is:
1850_CAM60_CLM50%BGC-CROP_CICE_POP2%ECO%ABIO-DIC_MOSART_CISM2%NOEVOLVE_WW3_BGC%BDRD

The land model component is not exactly the same among the compsets (CLM50%SP in F1850, CLM50%BGC in F1850_BDRD, CLM50%BGC-CROP in B1850). Would this land model difference interfere with the comparison between F1850(_BDRD) and B1850 simulations to differentiate oceanic effects?

Any help would be really appreciated.

 

[slevis]

I will answer about the land model:
Yes, comparing SP versus BGC versus CROP will not give you a clean comparison. For a clean comparison, you should pick one.

I have not used the following capability in a while to tell you exactly how it's done:
If you do not find what you want in the "short-hand" compsets, you can make your own compsets by modifying the long names.

 

[zhaos]

Thank you for your answer!

I added a F compset <alias> and <lname> to a script that is originally located in $SRCROOT/components/cam/cime_config/config_compsets.xml. The model was able to run. Does this seem right?

 

[sacks]

@zhaos - yes, that approach is a good one. Another way to do it is to use the long name directly as the --compset argument to create_newcase. That method is easier so you don't need to modify an xml file, but if you have things working by modifying the xml file, then your approach is a good one.