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

Compare with Current View Page History

« Previous Version 47 Next »

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:

  1. Make a snapshot of the approved VE runs.
  2. 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)

  3. Start Client (OC)
  4. 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

  5. The batch-runs contain (REF2015/WS2085) the following runs (see Table 1)

    Table 1: Smoketest batch runs for VE

    NameDescriptionExpected
     run time
    1_NWM_smoketest_VE_Import.xmlAll import workflows for all regions< 1 min
    2_NWM_smoketest_VE_Hydrodynamic_update.xmlThe hydrodynamic update runs for RMM (Sobek)< 1 h
    3_NWM_smoketest_VE_Hydrodynamic.xmlThe hydrodynamic forecast runs for Rijn, Maas
     ( all WAQUA) and RMM (Sobek) with reduced forecast time    		< 2 h
    4_NWM_smoketest_VE_PPHydrodynamic.xmlThe processioning runs for the WAQUA
    calculations of Rijn, Maas    		 < 5 min
    5_NWM_smoketest_VE_HydraZoet.xmlThe 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.xmlhe postprocessing of the HydraZoet runs for a reduced
     location set (2 locations Rijn, Maas, RMM)
     and Markermeer and IJsselmeer (all locations)    		< 5 min


  6. 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):

  1. Open in OC Management Modelruns; go to tab Verlooptijdstip voorspelling
  2. Mark the model runs which should be deleted, e.g. gebruiker smoketest_batch
  3. Push button Verwijderen
  4. 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:

  1. Start Client (OC)
  2. Make a snapshot of the approved ZW runs.
  3. 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)

NameDescriptionExpected
 run time
release_1440.zipContains 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.zipContains 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
Release_2100.zipRelease_2100_gebundeld.zipContains 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.zipContains 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

The generated data have a expiry time of 4 days. If you want to delete them before, perform following steps (see Figure 4 above):

  1. Open in OC Management Modelruns; go to tab Verlooptijdstip voorspelling
  2. Mark the model runs which should be deleted, e.g. omschrijving "ZW smoketest"
  3. Push button Verwijderen
  4. Approve the runs in the window management modelruns->actuele voorspelling. You can select multiple workflows (SHIFT+mouseclick) and click approve.


  • No labels

Disclaimer