This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
start:hype_model_description:hype_routing [2018/06/12 10:06] cpers |
start:hype_model_description:hype_routing [2018/08/10 15:50] cpers [Simple outlet lake or dam (olake)] |
||
---|---|---|---|
Line 66: | Line 66: | ||
The delay in the watercourse (//transtime//) in days is determined by the length of the watercourse (//rivlen//) and the water’s maximum velocity (//rivvel//). The maximum velocity is a general parameter with unit //m/s//. The delay in the local river is dependent on subbasin size, as stream length calculated from its area. The delay is a pure translation. The delay is divided into whole days (//ttday//) and parts of the day (//ttpart//). | The delay in the watercourse (//transtime//) in days is determined by the length of the watercourse (//rivlen//) and the water’s maximum velocity (//rivvel//). The maximum velocity is a general parameter with unit //m/s//. The delay in the local river is dependent on subbasin size, as stream length calculated from its area. The delay is a pure translation. The delay is divided into whole days (//ttday//) and parts of the day (//ttpart//). | ||
- | <m> transtime = rivlen/{rivvel~8.64~10^4} </m> | + | <m> transtime = rivlen/{rivvel*8.64*10^4} </m> |
<m> ttday = INT(transtime) </m> | <m> ttday = INT(transtime) </m> | ||
Line 255: | Line 255: | ||
In LakeData.txt a specific rating curve may be set instead of the general parameters. This is done by setting the //rate// and //exp// larger than zero in LakeData.txt. | In LakeData.txt a specific rating curve may be set instead of the general parameters. This is done by setting the //rate// and //exp// larger than zero in LakeData.txt. | ||
- | <m> outflow = rate * (wlm – lake_depth) ^ {exp} </m> | + | <m> outflow = rate * (wlm - lake_{depth}) ^ {exp} </m> |
=== Regulated lake === | === Regulated lake === |