This page describes how to run smoketests that are intended to be run as part of a new release directly after the installation is finished. There are smoketests available for VE and ZW. The smoketests for VE and ZW should not be run simultaneously because some workflows are mapped to the same FSS. First perform and finish all smoketests VE, followed by all smoketests for ZW, or visa versa.
Before performing a smoketest the "tester" should make a snapshot of the approved runs to be able to approve these workflows again after the smoketest.
Smoketest VE
The required files are in the folder BatchRunsForSmoketests/nwm_VE_smoketest. Perform the following steps:
- Make a snapshot of the approved VE runs.
- Upload via the Configuration Manager link to config manager (CM) the locationSets.xml (see folder nwm_VE_smoketest); this file is located under RegionConfigFiles; Provide a description, that this location set is used for smoketest (see Figure 1); this location set is just a temporary one for the smoketests.
Figure 1: Upload via locationSets.xml via Configuration Manager (CM) - Start Client (OC)
- Open Starten workflow; push button Voorbereide taak uitvoeren...; go to folder nwm_VE_smoketest and select one .xml file starting by number one (see Figure 2).
Figure 2: Start batch runs
After the all runs of the selected batch run are finished (check Systeembeheer->Draaiende taken, see Figure 3)), continue with the next file-number.
Figure 3: Check if batch runs are completed The batch-runs contain (REF2015/WS2085) the following runs (see Table 1)
Table 1: Smoketest batch runs for VE
Name Description Expected
run time1_NWM_smoketest_VE_Import.xml All import workflows for all regions < 1 min 2_NWM_smoketest_VE_Hydrodynamic_update.xml The hydrodynamic update runs for RMM (Sobek) < 1 h 3_NWM_smoketest_VE_Hydrodynamic.xml The hydrodynamic forecast runs for Rijn, Maas
( all WAQUA) and RMM (Sobek) with reduced forecast time< 2 h 4_NWM_smoketest_VE_PPHydrodynamic.xml The processioning runs for the WAQUA
calculations of Rijn, Maas< 5 min 5_NWM_smoketest_VE_HydraZoet.xml The HydraZoet runs for IJVD, Rijn, Maas, RMM
for a reduced location set (2 locations Rijn, Maas,
RMM) and Markermeer and IJsselmeer (all locations)
TODO: Extend smoketest to all scenarios< 15 min 6_NWM_smoketest_VE_PPHydraZoet.xml he postprocessing of the HydraZoet runs for a reduced
location set (2 locations Rijn, Maas, RMM)
and Markermeer and IJsselmeer (all locations)< 5 min - After finishing the smoketest re-upload via the Configuration Manager (CM) the locationSets.xml, which is provided in the Configuration under RegionConfigFiles; this file contains the full locations set again for further calculation.
The generated data have a expiry time of 7 days. If you want to delete them before, perform following steps (see Figure 4):
- Open in OC Management Modelruns; go to tab Verlooptijdstip voorspelling
- Mark the model runs which should be deleted, e.g. gebruiker smoketest_batch
- Push button Verwijderen
- Approve the runs in the window management modelruns->actuele voorspelling. You can select multiple workflows (SHIFT+mouseclick) and click approve.
In the next rolling barrel run, the model runs will be deleted from database.
Figure 4: Delete batch runs from database
Smoketest ZW
The required files are in the folder BatchRunsForSmoketests/nwm_ZW_smoketest. Perform the following steps:
- Start Client (OC)
- Make a snapshot of the approved ZW runs.
- Open Starten workflow; push button Voorbereide taak uitvoeren...; go to folder nwm_ZW_smoketest and select the .xml file there (see Figure 2 above).
The batch-run contains LHM, LSM Light, NDB and LTM Light workflows (see Table 2 below)
Table 2: Available smoketest batch runs for ZW (the release nr "ZW_smoketest_releaseXXXX" indicates which smoketests are required for the active release)
Name | Description | Expected run time |
---|---|---|
release_1440.zip | Contains Smoketests for all S1 and S2 workflows for the years 1911-1912 and 2003. To run these smoketests, all workflows belonging to the same scenario should be mapped to the same unique FSS | ~37 h per scenario per year |
release_2000.zip | Contains Smoketests for all S1, S2, and S3 workflows for the years 1911-1912 and 2003. To run these smoketests, all workflows belonging to the same scenario should be mapped to the same unique FSS | ~37 (S1/S2) to ~50h (S3) per scenario per year |
Contains Smoketests for all six BP18 workflows for the years 1911-1912 and 2003. To run these smoketests, all workflows belonging to the same scenario should be mapped to the same unique FSS, except for LHM which has its own dedicated FSS for parallel computing; The batches should be run in the correct order following the number prefix of the batchfiles; Only use Release_2100.zip OR Release_2100_gebundeld.zip (both these zips contain all smoketest runs) | ~19h (per scenario per year), depending on the nr of cores avaiable for LHM | |
Smoketesten 2_1_1_0.zip | Contains Smoketests for selection of six BP18 workflows (Ref and Stoom) for the years 1911-1912 and 2003. To run these smoketests, all workflows belonging to the same scenario should be mapped to the same unique FSS, except for LHM which has its own dedicated FSS for parallel computing; The batches should be run in the correct order following the number prefix of the batchfiles. | ~19h (per scenario per year), depending on the nr of cores avaiable for LHM |
Smoketesten 2_1_2_0.zip | Contains Smoketests for one BP18 workflows (Dparijs) for the years 1911-1912 for only LHMZ0 run. To run these smoketests, the workflows should be mapped to an available FSS, one of the FSS's dedicated FSS for LHM parallel computing (FSS06 for DPAR). For a more extensive smoketest files from Smoketesten 2_1_1_0.zip can be used (see above) | ~18h (per scenario for the two years), based on 8 core computation |
Smoketesten 2_2_0_0.zip | Contains Smoketests for two BP18 workflows (DPGL2050 and DPWH2050) for the years 1972-1973 for LHM - LSMLT - LTMLT runs and exports. Also smoketests for the new NDB export are provided To run these smoketests, first the new workflows should be mapped to an available FSS, with the LHM workflows mapped to the dedicated FSS for LHM parallel computing. The smoketests should be run in order of the numbered xml-files | ~22h (per scenario for the two years), based on 8 core computation |
Smoketesten 2_2_1_0.zip | Contains Smoketests for two BP18 workflows (D2085, R2085, W2085 and S2085) for the years 1972-1973 for LHMZ0 - LSMLTZ0 - NDB - LHM - LSMLT - LTMLT runs and exports. To run these smoketests, first the new workflows should be mapped to an available FSS, with the LHM workflows mapped to the dedicated FSS for LHM parallel computing. The smoketests should be run in order of the numbered xml-files | ~44h (per scenario for the two years), based on 8 core computation |
Contains Smoketests for two BP18 workflows REF2017 and S2050) for the years 1911-1912 for LHMZ0 - LSMLTZ0 - NDB - LHM - LSMLT runs and exports. The smoketests should be run in order of the numbered xml-files. Prior to running the smoketests (for S2050) the what-if scenario (WhatIf_rivmorf.xml, included in the "Smoketesten 2_2_3_0.zip" file) should be imported into the database, as follows:
See What-if scenario starten for a more elaborate explanation on how to use the What-if Scenario Display. | ~44h (per scenario for the two years), based on 8 core computation | |
Smoketesten 2_2_4_0.zip | Contains Smoketests for four workflows (REF2017VP, REF2017EP, S2050VP, S2050EP) for the years 1911-1912 or 1976-1977 for LHM - LSMLT - NDBpost runs and exports. To run these smoketests, first the new workflows should be mapped to an available FSS, with the LHM workflows mapped to the dedicated FSS for LHM parallel computing. The smoketests should be run in order of the numbered xml-files. One can choose to run 1911-1912 (normal starting years) or 1976-1977 (which includes a dry year 1976). | ~24h (per scenario for the two years), based on 8 core computation |
Contains Smoketests for four workflows (REF2017VP, REF2017EP, S2050VP, S2050EP) for the years 1911-1912 for LTMLT runs and exports. To run these smoketests, first the new workflows should be mapped to an available FSS. The smoketests should be run in order of the numbered xml-files. | ~2.5h (per scenario for the two years) | |
Contains Smoketests for nine export workflows (ZW_*ExportArchive* (S2050BP18Z0 / S2050VP)) for the years 1911-1912. To run these smoketests, first the new workflows (ZW_LSMLTExportArchive_WABES*, ZW_LHMExportArchive_GxGverschil*) should be mapped to an available FSS. The smoketests can be run in varying order. | no modelruns, only exports | |
Contains Smoketests for one workflows (REF2017BP18) for the years 1911-1912 for LHM Z0- LSMLT Z0 - NDB - LHM - LSMLT - LTMLT - NDBpost runs and exports. To run these smoketests, first the new workflows should be mapped to an available FSS. The smoketests should be run in order of the numbered xml-files. | ~38h (per scenario for the two years), based on 8 core computation | |
Contains Smoketests for workflow REF2017BP18 for the years 2009-2011 for the new 'modeltrain' LHM Z0- LSM3 Z0 - LHM - LSM3 runs and exports + workflow S2050BP18 for the year 1911 for the old 'modeltrain' LHM Z0- LSMLT Z0 - NDB - LHM - LSMLT - LTMLT runs using a WhatIf. | ~78h for scenario REF2017BP18 (for the three years), based on 8 core computation ~19h for scenario S2050BP18 (1 year), based on 8 core computation | |
Contains Smoketests for workflows REF2028BP24a for the years 1991-1992, S2100BP24c for the years 2101-2102, and RP2050BP24b for the years 2026-2027 for the new 'modeltrain' LHM Z0- LSM3 Z0 - LHM - LSM3 | ~48h for each scenario (for the two years), based on 8 core computation | |
Contains 12 Smoketests (split into two parts) for workflows REF2028BP24a, b and c for the years 1991-1992, S2100BP24a, b and c for the years 2101-2102, S2050BP24a, b and c for the years 2034-2035, and RP2050BP24a and b, DP2050BP24b for the years 2026-2027 for the new 'modeltrain' LHM Z0- LSM3 Z0 - LHM (part 1 to run on large FSS) - LSM3 (part 2 to run on small FSS). | ~48h for each scenario (for the two years), based on 8 core computation | |
Equal to Smoketesten 2_4_1_0_patch.zip, see row above | ~48h for each scenario (for the two years), based on 8 core computation | |
Equal to Smoketesten 2_4_1_0_patch.zip, see row above | ~48h for each scenario (for the two years), based on 8 core computation |
The generated data have a expiry time of 4 days. If you want to delete them before, perform following steps (see Figure 4 above):
- Open in OC Management Modelruns; go to tab Verlooptijdstip voorspelling
- Mark the model runs which should be deleted, e.g. omschrijving "ZW smoketest"
- Push button Verwijderen
- Approve the runs in the window management modelruns->actuele voorspelling. You can select multiple workflows (SHIFT+mouseclick) and click approve.