Fix bug or update documentation for "How do I create a single-point run with the NUOPC (default) coupler?"

[samsrabin]

Apparently something has changed that makes the "How do I create a single-point run with the NUOPC (default) coupler?" instructions not work anymore.

Definition of Done:

• Adrianna will update the discussion
• Make sure subset_data tells you what you need to do to run the case after subset data
• Have subset data provide the right xmlchange to the user-mod directory it creates in shell_commands

[wwieder]

A bit more info on this bug.

• Using ctsm5.3.012
• trying to subset data and run a 'generic single point' run, here for Boulder.
• preview_namelist didn't work until I changed DATM_MODE with ./xmlchange DATM_MODE=CLMGSWP3v1

The full set of commands are below

ml conda
conda activate npl-2024a

cd tools/site_and_regional

./subset_data point --lat 40.0523560209424 --lon 255 --dompft 14 --datm-syr 2000 --datm-eyr 2001 --create-datm --create-surface --outdir ~/scratch/subset_data_boco_test --create-user-mods --overwrite

cd ../../cime/scripts/

./create_newcase --case /glade/derecho/scratch/wwieder/subset_data_boco_test/c4_sp1 --compset 2000_DATM%1PT_CLM60%SP_SICE_SOCN_SROF_SGLC_SWAV_SESP --res CLM_USRDAT --output-root /glade/derecho/scratch/wwieder/subset_data_boco_test --user-mods-dir /glade/derecho/scratch/wwieder/subset_data_boco_test/user_mods --run-unsupported

./case.setup
./xmlchange DATM_MODE=CLMGSWP3v1
./xmlchange DATM_YR_START=2000
./xmlchange DATM_YR_END=2001
./preview_namelists

./case.build

[samsrabin]

The problem is that this needs to be run with a GSWP3 compset. subset_data should ideally tell the users exactly what compset to use.