stormchasegenie
Member
Greetings,
My name is Stefan, and I am a postdoc at UCLA downscaling CMIP6/CESM2.
I have created an NCL script that reads in required 3-D 6-h fields (u, v, T, q, phi, psfc, pmsl) and daily 2-D fields (t2, q2, skintemp, soilhgt, landsea, soilmoisture, and soiltemp). The 3-D fields are interpolated to 25 isobaric surfaces from 1000 hPa to 30 hPa. Each slice of the 3-D data are dumped out sequentially to dated binary files along with the 2-D fields using the code example in the WRF/WPS Users' Guide (http://www2.mmm.ucar.edu/wrf/users/docs/user_guide_V3.9/users_guide_chap3.html#_Required_Meteorological_Fields).
Geogrid.exe and metgrid.exe run successfully. The 6-h data look excellent; they mirror the data in the original .nc CMIP6/CESM2 files. There is no specific SST variable written to my binary files. However, I do write SKINTEMP to the binary files. Over the oceans, the SSTs (taken to be skin temperature) look great. Over land however, SKINTEMP doesn't look right. Soil moisture and temperature also don't look right.
SKINTEMP is a daily 2-D variable (as are soil fields), thus, SSTs are updated daily, while the 3-D fields and psfc and pmsl are updated at 6-h intervals.
What could be going on here in running metgrid.exe that could be leading to correct SKINTEMP mapped to the oceans, but different SKINTEMP being mapped to land areas?
As an aside, I can run WRF stably with the resulting met_em files. The simulation quickly equilibrates to the local radiative and thermodynamic conditions at a given gridcell, even though the simulation is initialized to a weird SKINTEMP and weird soil variables over land. Again, SSTs look great.
Thanks,
-Stefan
My name is Stefan, and I am a postdoc at UCLA downscaling CMIP6/CESM2.
I have created an NCL script that reads in required 3-D 6-h fields (u, v, T, q, phi, psfc, pmsl) and daily 2-D fields (t2, q2, skintemp, soilhgt, landsea, soilmoisture, and soiltemp). The 3-D fields are interpolated to 25 isobaric surfaces from 1000 hPa to 30 hPa. Each slice of the 3-D data are dumped out sequentially to dated binary files along with the 2-D fields using the code example in the WRF/WPS Users' Guide (http://www2.mmm.ucar.edu/wrf/users/docs/user_guide_V3.9/users_guide_chap3.html#_Required_Meteorological_Fields).
Geogrid.exe and metgrid.exe run successfully. The 6-h data look excellent; they mirror the data in the original .nc CMIP6/CESM2 files. There is no specific SST variable written to my binary files. However, I do write SKINTEMP to the binary files. Over the oceans, the SSTs (taken to be skin temperature) look great. Over land however, SKINTEMP doesn't look right. Soil moisture and temperature also don't look right.
SKINTEMP is a daily 2-D variable (as are soil fields), thus, SSTs are updated daily, while the 3-D fields and psfc and pmsl are updated at 6-h intervals.
What could be going on here in running metgrid.exe that could be leading to correct SKINTEMP mapped to the oceans, but different SKINTEMP being mapped to land areas?
As an aside, I can run WRF stably with the resulting met_em files. The simulation quickly equilibrates to the local radiative and thermodynamic conditions at a given gridcell, even though the simulation is initialized to a weird SKINTEMP and weird soil variables over land. Again, SSTs look great.
Thanks,
-Stefan