mksurfdata_esmf tools for grids crossing 0° lon

[Yuan Sun]

Hi all,

I am using mksurfdata_esmf from ctsm5.3 to generate the Europe domain (crossing 0°lon) with ESMF8.6.1.

The tool works well using mesh (-180°to180°) as shown in subplots a, b. However, using mesh (0°to360°) PCT_NATVEG is good (subplot c), but only PCT_URBAN is not (subplot d).

I attached the screenshots of surface outputs.

Based on my previous experience in generating a domain for the UK, the mksurfdata_esmf addressed the issue for the domain containing 0° lon using -180to180.

It is pitiful that using 0°to360° mesh could not generate valid data for PCT_URBAN, but other variables seem good.

As a result, I using a mesh -180to180 in lilac_in as:
&lilac_atmcap_input
atm_mesh_filename = '/work/n02/n02/yuansun/wrf/runs/wrf-ctsm_tutorial/configuration/CTSM/mask_lnd_mesh.nc'
/
&lilac_lnd_input
lnd_mesh_filename = '/work/n02/n02/yuansun/wrf/runs/wrf-ctsm_tutorial/configuration/CTSM/lnd_mesh.nc'
/

and in lnd_in using a domain 0 to 360 as:
fatmlndfrc = '/work/n02/n02/yuansun/wrf/runs/wrf-ctsm_tutorial/configuration/CTSM/domain.lnd.wrf2clm_lnd_noneg_wrf2clm_ocn_noneg.250511.nc'

Otherwise, a domain -180to180 led to the error ERROR: lilac_atmcap: n, lon, mesh_lon = 1 348.4434814453 -11.5565185547

Thanks for any comments.

Best,
Yuan

 

[slevis]

If I understood correctly, you ran without error by making the above choices for atm_mesh_filename, lnd_mesh_filename, fatmlndfrc.

 

[Yuan Sun]

If I understood correctly, you ran without error by making the above choices for atm_mesh_filename, lnd_mesh_filename, fatmlndfrc.

Yes，my WRF-ctsm5.3 case worked with both surface data.