User Tools

Site Tools


start:hype_tutorials:transfer_lakebasin

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
start:hype_tutorials:transfer_lakebasin [2020/05/05 10:38]
cpers
start:hype_tutorials:transfer_lakebasin [2020/05/18 08:25]
cpers
Line 1: Line 1:
-===== Transfer ​lakebasin ​to HYPE version 5.11.0 =====+===== Transfer ​multi-basin lakes to HYPE version 5.11.0 =====
  
 In HYPE version 5.11.0 the function of multi-basin lakes has been changed. HYPE will strive to have a equal water level in all lakebasins belonging to the same lake. This means that although the upstream-downstream connection between lakebasins should be the main direction of flow sometimes the flow between lakebasins may go in the other direction and the output variable cout will then be negative. In HYPE version 5.11.0 the function of multi-basin lakes has been changed. HYPE will strive to have a equal water level in all lakebasins belonging to the same lake. This means that although the upstream-downstream connection between lakebasins should be the main direction of flow sometimes the flow between lakebasins may go in the other direction and the output variable cout will then be negative.
Line 12: Line 12:
 If there are branches from other lakebasins than the last one that leave the multi-basin lake, they now need to have specified outflow information. Earlier they were calculated as a fraction of the flow leaving the lakebasin ((1-//​mainpart//​) in [[http://​www.smhi.net/​hype/​wiki/​doku.php?​id=start:​hype_file_reference:​branchdata.txt|BranchData.txt]]). That is not possible anymore, additional outlet of a lakebasin lake now need to be specified in [[http://​www.smhi.net/​hype/​wiki/​doku.php?​id=start:​hype_file_reference:​lakedata.txt|LakeData.txt]]. If there are branches from other lakebasins than the last one that leave the multi-basin lake, they now need to have specified outflow information. Earlier they were calculated as a fraction of the flow leaving the lakebasin ((1-//​mainpart//​) in [[http://​www.smhi.net/​hype/​wiki/​doku.php?​id=start:​hype_file_reference:​branchdata.txt|BranchData.txt]]). That is not possible anymore, additional outlet of a lakebasin lake now need to be specified in [[http://​www.smhi.net/​hype/​wiki/​doku.php?​id=start:​hype_file_reference:​lakedata.txt|LakeData.txt]].
  
-All lakebasins will have the same ''​ldtype''​ (7). The last lakebasin (GeoData order) will be identified by HYPE. Note that lakebasins belonging to different multi-basin lakes should not be mixed in [[http://​www.smhi.net/​hype/​wiki/​doku.php?​id=start:​hype_file_reference:​geodata.txt|GeoData.txt]],​ i.e. all lakebasins of a multi-basin lake need to be following each other in GeoData without any other lakebasins in between (mixing with subbasins without lakes or with simple lakes are ok though).+All lakebasins will have the same ''​ldtype''​ (7). The last lakebasin (GeoData order) will be identified by HYPE. All lakebasins of a multi-basin lake need to be connected by maindown or branchdown. No subbasins without lakebasin or with a lake belonging to other lake/​multi-basin lake are allowed in between the subbasins of lakebasins. Note that lakebasins belonging to different multi-basin lakes should not be mixed in [[http://​www.smhi.net/​hype/​wiki/​doku.php?​id=start:​hype_file_reference:​geodata.txt|GeoData.txt]],​ i.e. all lakebasins of a multi-basin lake need to be following each other in GeoData without any other lakebasins in between (mixing with subbasins without lakes or with simple lakes are ok though). This might cause problems.
  
start/hype_tutorials/transfer_lakebasin.txt ยท Last modified: 2024/01/25 11:37 (external edit)