Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

...

NameDescriptionExpected
 run time
View file
namerelease_1440.zip
height250
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
View file
namerelease_2000.zip
height250
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
View file
nameRelease_2100.zip
height250
View file
nameRelease_2100_gebundeld.zip
height250
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
 
View file
nameSmoketesten 2_1_1_0.zip
height250
 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

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

...