Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

Single-point run doesn't reproduce an error

Status
Not open for further replies.

samrabin

Sam Rabin
Member
I'm trying to debug an error happening in a single crop patch, so I used subset_data to make input files for that gridcell:
Code:
./subset_data point --lon 74.75 --lat 51.75 --crop --create-user-mods --create-domain --create-surface --create-landuse --create-datm --include-nonveg
And then made a case for it:
Code:
./create_newcase --project P93300641 --compset IHistClm50BgcCrop --run-unsupported --user-mods-dir /glade/u/home/samrabin/ctsm/tools/site_and_regional/subset_data_single_point/user_mods --case /glade/u/home/samrabin/cases_ctsm/ts_20220523_2 --res CLM_USRDAT
I also had to set check_dynpft_consistency = .false. in user_nl_clm.

Unfortunately, when I run that case, I don't get the error. I've confirmed that the gridcell being run is the one I expected, and also that crops are being run.

It seems that there's a difference in the climate inputs. Upon sowing in 1979, in the original run, the patch had the following values:
Code:
gdd020  0.000000000000000E+000
gdd820  0.000000000000000E+000
gdd1020  0.000000000000000E+000
But in the single-point version, I get:
Code:
gdd020   2748.90010441609
gdd820   1464.79026691504
gdd1020   1176.90801308338

I notice that I never specified a resolution when creating the input files. Could this be the issue?

The original case is at /glade/u/home/samrabin/cases_ctsm/halfdeg_test_20220518 and was created as a clone of a case with --res hcru_hcru_mt13 --compset IHistClm50BgcCrop.
 

erik

Erik Kluzek
CSEG and Liaisons
Staff member
The files used by subset_data is going to be the files in the default_data.cfg file. Which currently points to the standard f09 files. So you should replace them with the half-degree files from your other case. Right now subset_data doesn't have a way to take in a resolution, that's something we want to add later. that should get you datasets that will match your half degree case.

I'd also compare the namelists between the two cases and make sure they the same other than the things that should be different. I would make sure for example that you are using the same finidat file for the two cases.

Make sure the fsurdat file you are using is for 1850 and the landuse timeseries file starts at 1850, thus having a fsurdat files and flanduse_timeseries file that should match, that should allow you to not have to set check_dynpft_consistency.

Hopefully, that should get you something that matches.
 
Status
Not open for further replies.
Top