-
Notifications
You must be signed in to change notification settings - Fork 321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some issues with creating surface datasets for the nldas2 grid... #1408
Comments
The 0.125nldas2 grid doesn't seem to be recognized in mksurfdata.pl, so I'm surprised that the process works to create that grid. Possibly there was a manual override that was put in place to create the first version of the surface dataset for it. |
That is surprising. It seems like this error check would fail if it were thought to be a global grid: CTSM/tools/mksurfdata_map/src/mkgridmapMod.F90 Lines 498 to 510 in 2a90c20
(It looks like that's the only place where regional vs. global matters.) |
The reason I noticed this was because of a problem that @swensosc ran into as follows...
I told him how to get around it, but wondered why the NLDAS2 case didn't show the problem. |
I'm changing the name of this to be specific around the nldas2 grid. I tried creating a surface dataset and the first problem I ran into required this XML change... diff --git a/bld/namelist_files/namelist_defaults_ctsm.xml b/bld/namelist_files/namelist_defaults_ctsm.xml
index 50fbadc3..b0021079 100644
--- a/bld/namelist_files/namelist_defaults_ctsm.xml
+++ b/bld/namelist_files/namelist_defaults_ctsm.xml
@@ -2366,7 +2366,7 @@ lnd/clm2/surfdata_map/release-clm5.0.30/surfdata_ne0np4.CONUS.ne30x8_hist_78pfts
<map frm_hgrid="3x3min" frm_lmask="nomask" to_hgrid="0.125nldas2" to_lmask="nomask"
>lnd/clm2/mappingdata/maps/0.125x0.125/map_3x3min_nomask_to_0.125nldas2_nomask_aave_da_c200309.nc</map>
<map frm_hgrid="1km-merge-10min" frm_lmask="HYDRO1K-merge-nomask" to_hgrid="0.125nldas2" to_lmask="nomask"
->lnd/clm2/mappingdata/maps/0.125x0.125/map_1km-merge-10min_HYDRO1K-merge-nomask_to_0.125nldas2_nomask_aave_da_c140702.nc</map>
+>lnd/clm2/mappingdata/maps/0.125x0.125/map_1km-merge-10min_HYDRO1K-merge-nomask_to_0.125x0.125_nomask_aave_da_c140702.nc</map>
<map frm_hgrid="5x5min" frm_lmask="nomask" to_hgrid="0.125nldas2" to_lmask="nomask"
>lnd/clm2/mappingdata/maps/0.125x0.125/map_5x5min_nomask_to_0.125nldas2_nomask_aave_da_c200309.nc</map>
<map frm_hgrid="10x10min" frm_lmask="nomask" to_hgrid="0.125nldas2" to_lmask="nomask" |
The next issue I ran into was...
|
I get a similar problem if I remove the "-hirespft" option as well. In order to get past those problems I had to make these changes in xml... diff --git a/bld/namelist_files/namelist_defaults_ctsm.xml b/bld/namelist_files/namelist_defaults_ctsm.xml
index 50fbadc3..2913250d 100644
--- a/bld/namelist_files/namelist_defaults_ctsm.xml
+++ b/bld/namelist_files/namelist_defaults_ctsm.xml
@@ -2358,19 +2358,19 @@ lnd/clm2/surfdata_map/release-clm5.0.30/surfdata_ne0np4.CONUS.ne30x8_hist_78pfts
<!-- Created by lnd/clm/bld/namelist_files/createMapEntry.pl-->
<map frm_hgrid="0.125x0.125" frm_lmask="nomask" to_hgrid="0.125nldas2" to_lmask="nomask"
->lnd/clm2/mappingdata/maps/0.125x0.125/map_0.125x0.125_nomask_to_0.125nldas2_nomask_aave_da_c200206.nc</map>
+>lnd/clm2/mappingdata/maps/0.125x0.125/map_0.125x0.125_nomask_to_0.125x0.125_nomask_aave_da_c200206.nc</map>
<map frm_hgrid="0.5x0.5" frm_lmask="nomask" to_hgrid="0.125nldas2" to_lmask="nomask"
->lnd/clm2/mappingdata/maps/0.125x0.125/map_0.5x0.5_nomask_to_0.125nldas2_nomask_aave_da_c200206.nc</map>
+>lnd/clm2/mappingdata/maps/0.125x0.125/map_0.5x0.5_nomask_to_0.125x0.125_nomask_aave_da_c200206.nc</map>
<map frm_hgrid="0.25x0.25" frm_lmask="nomask" to_hgrid="0.125nldas2" to_lmask="nomask"
->lnd/clm2/mappingdata/maps/0.125x0.125/map_0.25x0.25_nomask_to_0.125nldas2_nomask_aave_da_c200309.nc</map>
+>lnd/clm2/mappingdata/maps/0.125x0.125/map_0.25x0.25_nomask_to_0.125x0.125_nomask_aave_da_c200309.nc</map>
<map frm_hgrid="3x3min" frm_lmask="nomask" to_hgrid="0.125nldas2" to_lmask="nomask"
->lnd/clm2/mappingdata/maps/0.125x0.125/map_3x3min_nomask_to_0.125nldas2_nomask_aave_da_c200309.nc</map>
+>lnd/clm2/mappingdata/maps/0.125x0.125/map_3x3min_nomask_to_0.125x0.125_nomask_aave_da_c200309.nc</map>
<map frm_hgrid="1km-merge-10min" frm_lmask="HYDRO1K-merge-nomask" to_hgrid="0.125nldas2" to_lmask="nomask"
->lnd/clm2/mappingdata/maps/0.125x0.125/map_1km-merge-10min_HYDRO1K-merge-nomask_to_0.125nldas2_nomask_aave_da_c140702.nc</map>
+>lnd/clm2/mappingdata/maps/0.125x0.125/map_1km-merge-10min_HYDRO1K-merge-nomask_to_0.125x0.125_nomask_aave_da_c140702.nc</map>
<map frm_hgrid="5x5min" frm_lmask="nomask" to_hgrid="0.125nldas2" to_lmask="nomask"
->lnd/clm2/mappingdata/maps/0.125x0.125/map_5x5min_nomask_to_0.125nldas2_nomask_aave_da_c200309.nc</map>
+>lnd/clm2/mappingdata/maps/0.125x0.125/map_5x5min_nomask_to_0.125x0.125_nomask_aave_da_c200309.nc</map>
<map frm_hgrid="10x10min" frm_lmask="nomask" to_hgrid="0.125nldas2" to_lmask="nomask"
->lnd/clm2/mappingdata/maps/0.125x0.125/map_10x10min_nomask_to_0.125nldas2_nomask_aave_da_c200206.nc</map>
+>lnd/clm2/mappingdata/maps/0.125x0.125/map_10x10min_nomask_to_0.125x0.125_nomask_aave_da_c140702.nc</map>
<map frm_hgrid="0.9x1.25" frm_lmask="nomask" to_hgrid="0.125nldas2" to_lmask="nomask"
>lnd/clm2/mappingdata/maps/0.125x0.125/map_0.9x1.25_nomask_to_0.125nldas2_nomask_aave_da_c200206.nc</map>
Then I ran into a subscript overflow issue... |
We should try this in the new mksurfdata_esmf and make sure it works there. |
I saw this comment just now. I tried mksurfdata_esmf and it worked:
where the SMS test pointed to the surface dataset I just generated: |
It seems like this has been fixed. |
It would be useful to have a naming convention for regional grids, so that the tool chain can recognize if the flag mksrf_gridtype should be global or regional. Right now mksurfdata.pl has logic to set it to regional if the name starts with either 1x1_ or 5x5_. If we have a consistent naming convention the tool chain can just set that variable to regional for grids following the regional or single-point naming convention.
I do think the convention I've been following of number of grid points in N-S by E-W followed by underscore and then a descriptive name (where I've used something like townname in lowercase, and State or Country in Caps. For tower sites they often have a descriptive short name that can be used at the end there.
The NLDAS2 regional grid doesn't follow the above convention and is called "0.125nldas2" which is the rough grid size and then nldas2 as the description. Since NLDAS2 is well known that seems to work.
@negin513 @swensosc
The text was updated successfully, but these errors were encountered: