How do I create a regional run with the NUOPC (default) coupler?

[sophmaca]

Discussed in #1833

^{Originally posted by adrifoster August 26, 2022}
We get this question a lot:

I am trying to set up a case for a specific latitude and longitude. I want to use GSWP3 climate data, how do I set this up?

^{My issue}
This discussion has been very helpful and I am able to create a single-point run using the instructions on Derecho. However, I am interested in creating a regional run and cannot produce the regional datm files.

Using the commands on Derecho:
conda activate ctsm_pylib
./subset_data region --lat1 $my_lat1 --lat2 $my_lat2 --lon1 $my_lon1 --lon2 $my_lon2 --create-surface --create-datm --create-user-mods --create-domain --create-mesh --outdir $my_output_dir

I expect this last command to create the surface data file, CLM domain file, mesh file, and datm files (for default GSWP3 years 1901 to 2014) for my region of interest using default_data_2000.cfg. After I run that line, there is no error produced and I get all files except for the datm files ($my_output_dir/datmdata is empty). Could this be an error in my use of ./subset_data region?

[olyson]

I wonder if it has something to do with this recently posted bug?

#2890

[olyson]

Although I think it should still produce datm files. The bug appears when you use ./preview_namelists.

[olyson]

Ok, it is due to this bug, which I posted some time ago but forgot about :)

#2110

Hasn't been fixed. I think you can still run your case using the global datm files.