Dear WRF community,
We are downscaling output from ECHAM5, we successfully wrote all the required fields to WPS intermediate format and the WRF could run through with out any problems. But the evapotranspiration in the output is too low. We think this problem comes from how we deal with the soil moisture.
In the ECHAM5 output, soil moisture is represented in the variable "soil wetness" with the unit of meter, which only contains one layer. However, soil temperature from ECHAM5 has five layers (3, 19, 78, 268, 698 cm), so we tried to distribute the soil wetness to these 5 layers with the soil moisture of every layer equal to soil wetness/6.98, where 6.98 is the soil height in meter. This means we equally distributed the soil wetness into every layer, which causes too low soil moisture in the shallower layer and leads to low evapotranspiration.
Do you have any experience with ECHAM5 as forcing data? How should we deal with soil moisture?
We are downscaling output from ECHAM5, we successfully wrote all the required fields to WPS intermediate format and the WRF could run through with out any problems. But the evapotranspiration in the output is too low. We think this problem comes from how we deal with the soil moisture.
In the ECHAM5 output, soil moisture is represented in the variable "soil wetness" with the unit of meter, which only contains one layer. However, soil temperature from ECHAM5 has five layers (3, 19, 78, 268, 698 cm), so we tried to distribute the soil wetness to these 5 layers with the soil moisture of every layer equal to soil wetness/6.98, where 6.98 is the soil height in meter. This means we equally distributed the soil wetness into every layer, which causes too low soil moisture in the shallower layer and leads to low evapotranspiration.
Do you have any experience with ECHAM5 as forcing data? How should we deal with soil moisture?