You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Presently, in the form of daily climate files, we provide a daily high+low temperature along with a liquid precipitation amount. WEPP takes it from there in computing snowfall and keeping track of snowcover. We don't have any current knobs to turn to goose these parameters to better match observations.
Question
How closely does WEPP/DEP track observations with regards to snow cover / snow depth?
So this issue will track code work and discoveries in this space. An initial discovery is that the snow-water content is likely a field that has been quelled in the DEP modifications of wepp within the water balance output file, le sigh.
The text was updated successfully, but these errors were encountered:
Initial doubt into the difference between snodpt and snodpy. snodpt is documented as snow depth, but snodpy is what was previously included in watbal.for output 🤷 . A test run had the values equal, so will stick with snodpy for output along.
Also including densg to get the snow density and thus be able to compute snow water equivalent.
Presently, in the form of daily climate files, we provide a daily high+low temperature along with a liquid precipitation amount. WEPP takes it from there in computing snowfall and keeping track of snowcover. We don't have any current knobs to turn to goose these parameters to better match observations.
Question
How closely does WEPP/DEP track observations with regards to snow cover / snow depth?
So this issue will track code work and discoveries in this space. An initial discovery is that the snow-water content is likely a field that has been quelled in the DEP modifications of wepp within the water balance output file, le sigh.
The text was updated successfully, but these errors were encountered: