You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Introduction

QWAST allocates water based on priorities between users according to LHM. As the priorities in LHM 4.3 have been changed, QWAST also have changed to accomodate them. Before LHM 4.3, QWAST was reading district water demands based on user (e.g. water demand for irrigation). QWAST itself gave a priority to the user, which is as close as possible to LHM.

After LHM 4.3, QWAST is reading district demands per priority, he does not read the user (e.g. water demand priority 4). As a consequence, QWAST does not know any more who the user is. However, QWAST has now exactly the same priorities as LHM.

Input files needed for QWAST

NetCDF files that are outputs of NWM:

  • ZW_LHM_DM_LevelPoints_REF2017BP18.nc
  • ZW_LHM_MozartDistrict_REF2017BP18.nc
  • ZW_LHM_DM_Districten_REF2017BP18.nc
  • ZW_LHM_DM_Knopen_Balans_REF2017BP18.nc
  • ZW_LHM_DM_LevelPoints_REF2017BP18.nc

One file that contains Chloride data:

  • ZW_LSM3_Chloride_REF2017BP18Z0.nc

One file from Mozart containing data about the rainfall:

  • ...\LHM_4_3\postprocessing\output\dm\DMNodes_Variabelpeil.nc

Exchange files from Mozart:

  • ...\LHM_4_3\model\dm\DwExchanges_NwSim.txt


QWAST calculates on year bases, using decade data, from time January 1 to January 1.

The given NetCDF files contain data (including) January 1 to January 1. There are just some exceptions: the file DMNodesVariabelpeil.nc starts January 11.

Note

Do all the imports at once for a certain scenario. If not, some interpolated data might not be overwritten.


  • No labels