If a user is using gridded meteorological forcing and supply only dew point temperature (no vapor pressure or relative humidity) then the model produces anomalous results for the ET module.
The problem seems to be fragile code in tEvapoTrans.cpp that expects the user to provide RH and VP in the gridded data file as "NO_DATA" like
TD pathtoraster/DewPoint_ asc
RH NO_DATA NO_DATA
VP NO_DATA NO_DATA
When the user does not provide the RH and VP as shown above the code sets dew point to 0degC which results in the model pixel outputs showing -273.15degC.
The fix could be as simple as changing the value that the three moisture variables are initialized to in tCNode from 0 to -9999 but not sure how this would affect the point station forcing routine.
If a user is using gridded meteorological forcing and supply only dew point temperature (no vapor pressure or relative humidity) then the model produces anomalous results for the ET module.
The problem seems to be fragile code in tEvapoTrans.cpp that expects the user to provide RH and VP in the gridded data file as "NO_DATA" like
TD pathtoraster/DewPoint_ asc
RH NO_DATA NO_DATA
VP NO_DATA NO_DATA
When the user does not provide the RH and VP as shown above the code sets dew point to 0degC which results in the model pixel outputs showing -273.15degC.
The fix could be as simple as changing the value that the three moisture variables are initialized to in tCNode from 0 to -9999 but not sure how this would affect the point station forcing routine.