QWAST is using LHM output as initial and boundary conditions (decade timestep). QWAST needs the following:
- Initial water level of the lakes
- Chloride concentration for the whole calculation period
- Water demands for the whole calculation period
QWAST also imports results of LHM that are not used but shown for comparison:
- Water usage
- Water shortage
Creating a scenario to import
Every QWAST run is based on an LHM run. QWAST needs a set of variables from LHM. In the table below all the variables are listed and the possible name of files where they are coming. There are tree sort of files used: DM output files (most of the variables come from there), Chloride output files (for variable CL) from the post-processing and Mozart output files (for Netto_neerslag and Watervraag_peilbeheer). Therefore to create a QWAST run the locations of these three file types should be given.
| QST name | LHM name | Location | File name example |
| CL | Chloride | Krimpen a/d IJssel (chloride meetpunt) | ZW_ChloridePost_REF2017EP.nc (from another directory, NDBPost) |
| H | Peil_knopen | DMknopen | ZW_LHM_DM_LevelPoints_REF2017EP.nc |
| TekortNW_HandhavingPeil | Tekort_peilbeheer | DMknopen | ZW_LHM_DM_LevelPoints_REF2017EP.nc |
| VraagNW_Doorspoelin | Vraag_takdoorspoeling | DMtakken | ZW_LHM_DM_FlowPoints_REF2017EP.nc |
| TekortNW_Doorspoeling | Tekort_takdoorspoeling | DMtakken | ZW_LHM_DM_FlowPoints_REF2017EP.nc |
| Q | Takdebiet | DMtakken | ZW_LHM_DM_FlowPoints_REF2017EP.nc |
| VraagDW_Onttrekkingen | Gewenste_onttrekkingen_districten | Dmdistricten | ZW_LHM_DM_Districten_REF2017EP.nc |
| TekortDW_Onttrekkingen | Reductie_onttrekkingen_districten | Dmdistricten | ZW_LHM_DM_Districten_REF2017EP.nc |
| VraagDW_Lozingen | Gewenste_lozingen_districten | Dmdistricten | ZW_LHM_DM_Districten_REF2017EP.nc |
| TekortDW_Lozingen | Reductie_lozingen_districten | Dmdistricten | ZW_LHM_DM_Districten_REF2017EP.nc |
| VraagNW_HandhavingPeil | Watervraag_peilbeheer | DMknopen | MozartDM\DMNodes_Variabelpeil.nc |
| VraagNW_DrinkIndustrie | Vraag_onttrekkingen_DIW | DMknopen | ZW_LHM_DM_Knopen_Variabelpeil_REF2017EP.nc |
| VraagNW_SchutLek | Vraag_Schut-lekverlies_knp | DMknopen | ZW_LHM_DM_Knopen_Variabelpeil_REF2017EP.nc |
| TekortNW_DrinkIndustrie | Tekort_onttrekkingen_DIW | DMknopen | ZW_LHM_DM_Knopen_Variabelpeil_REF2017EP.nc |
| TekortNW_SchutLek | Tekort_Schut-lekverlies_knp | DMknopen | ZW_LHM_DM_Knopen_Variabelpeil_REF2017EP.nc |
| VraagNW_NettoNeerslag | Netto_neerslag | DMknopen | ZW_LHM_DM_Knopen_Variabelpeil_REF2017EP.nc |
| RealisatieNW_NettoNeerslag | Netto_neerslag | DMknopen | MozartDM\DMNodes_Variabelpeil.nc |
| VraagDW_Drinkwater | demand_pubwat | DMdistricten | ZW_LHM_MozartDistrict_REF2017EP.nc |
| VraagDW_Industrie | demand_industry | DMdistricten | ZW_LHM_MozartDistrict_REF2017EP.nc |
| VraagDW_Doorspoeling | demand_flush | DMdistricten | ZW_LHM_MozartDistrict_REF2017EP.nc |
| VraagDW_Peilhandhaving | demand_wm_todw | DMdistricten | ZW_LHM_MozartDistrict_REF2017EP.nc |
| VraagDW_Beregening | demand_agric | DMdistricten | ZW_LHM_MozartDistrict_REF2017EP.nc |
| RealisatieDW_Drinkwater | alloc_pubwat | DMdistricten | ZW_LHM_MozartDistrict_REF2017EP.nc |
| RealisatieDW_Industrie | alloc_industry | DMdistricten | ZW_LHM_MozartDistrict_REF2017EP.nc |
| RealisatieDW_Doorspoeling | alloc_flush | DMdistricten | ZW_LHM_MozartDistrict_REF2017EP.nc |
| RealisatieDW_Peilhandhaving | alloc_wm_dw | DMdistricten | ZW_LHM_MozartDistrict_REF2017EP.nc |
| RealisatieDW_Beregening | alloc_agric | DMdistricten | ZW_LHM_MozartDistrict_REF2017EP.nc |
| VraagNW_Kwel | Kwel_lozing | DMknopen | ZW_LHM_DM_Knopen_Balans_REF2017EP.nc |
| VraagNW_Lozingen | RWZI_lozingen | DMknopen | ZW_LHM_DM_Knopen_Balans_REF2017EP.nc |
| RealisatieNW_Kwel | Kwel_lozing | DMknopen | ZW_LHM_DM_Knopen_Balans_REF2017EP.nc |
| RealisatieNW_Wegzijging | Kwel_onttrekking | DMknopen | ZW_LHM_DM_Knopen_Balans_REF2017EP.nc |
| RealisatieNW_Lozingen | RWZI_lozingen | DMknopen | ZW_LHM_DM_Knopen_Balans_REF2017EP.nc |
| VraagNW_Wegzijging | Kwel_onttrekkin | DMknopen | ZW_LHM_DM_Knopen_Balans_REF2017EP.nc |
There is a script, compile-import-dataset-peil.py in the SVN repository that is copying the relevant files to the a user-chosen input folder. To run the script, the user has to give the location of the LHM results and the location of the desired compiled files. An example of the CSV file used as input for the scipt is given here:
Scenario,NetCDF,Chloride,Mozart,Result
REF2017VP,p:/11205271-kpp-dp-zoetwater/NWM/2020_NWM_productieomgeving/archief/2020_voorkeurs&economischpakket/netcdf/LHM/REF2017VP,p:\11205271-kpp-dp-zoetwater\NWM\2020_NWM_productieomgeving\archief\2020_voorkeurs&economischpakket\netcdf\NDBpost\REF2017VP,p:\11205271-kpp-dp-zoetwater\NWM\2020_NWM_productieomgeving\archief\2020_voorkeurs&economischpakket\modeldata\download,p:\11206800-012-optimaalwaterbeheer\test\
Importing scenarios to QWAST
The scenario should be placed in one of the scenario folders, for example REF2017. The time T0 should be in the beginning of the scenario (there are some post-processing scripts after the import). The import workflow: "Import data from LHM" should be run.
Import time period and t0
QWAST is reading the import files from t0 until which of these comes first : t0+100 years or the end of the data. Thus, check that your t0 corresponds to the beginning of your data.
