CAM_CONFIG_OPTS

[steve_ghan@pnl_gov]

I'm trying add a variation off a compset:
./create_newcase -case $CASEROOT -mach $MACH
-res f19_f19 -compset F_2000_CAM5 -compiler pgi
./xmlchange CAM_CONFIG_OPTS="-phys cam5 –clubb_sgs"
.
.
.
./cesm_setup
But buildnml says
ERROR: unrecognized arguments: –clubb_sgs
even though it lists clubb_sgs as an option.
Can't I modify a compset? Using the clubb compset is not a solution, because I don't actually want to use clubb. I'm just using clubb as an example of another option I've tried to introduce. If there is a way to modify a compset I'd prefer that over creating a new compset.

Steve Ghan

 

[jedwards]

Hi Steve, It looks like the option should be "-macrophys clubb_sgs" This is in cam/bld/config_files/definition.xml :

<entry id="macrophys" valid_values="rk,park,clubb_sgs,none" value="">
Macrophysics package: RK, Park, CLUBB_SGS.
</entry>

 

[eaton]

Note that the configuration parameter pointed out by Jim (macrophys) is *not* settable from configure's commandline.  It is set internally by configure based on specifying the -clubb_sgs option.Not sure what the problem is.  What version of CESM or CAM are you using? 

 

[santos]

Look very closely at this:"-phys cam5 –clubb_sgs"If you squint really hard, you can see that the first dash is a normal ASCII hyphen, but the second is an en-dash, which is longer. If that's the character that you actually put in CAM_CONFIG_OPTS, then it's no wonder the option wasn't recognized. In fact, the error message that you get back has an en-dash as well, which suggests that this really is the problem.I don't know how you got an en-dash in the first place, but the most common cause is copying-and-pasting an option from a document (office or PDF) that has been automatically formatted.