Versions Compared

Key

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

...

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
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.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
Smoketesten 2_2_0_0.zipContains 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.zipContains 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:

  1. Open the Operator Client, navigate to the What-if Scenario Display
  2. Import the xml file ("WhatIf_rivmorf.xml") using the "Importeer .."-button
  3. Select one of the imported what-if scenario from the drop-down list
  4. Save the selected what-if scenario using the "Geselecteerd scenario bewaren"-button
  5. Repeat steps 3 and 4 for the other imported scenario's ('rivmorf_LSMLT_BP18Stoom2050')
  6. When all what-if scenario's have been saved close the What-if Scenario Display
  7. Make sure the what-if scenario zip files are placed on the FSS's in the correct place (e.g. D:\what_if_scenarios\), the directory should correspond with the location that is referenced in the What-if Scenario Display for the concerning what-if scenario, i.e. the File_path which is visible under "5:Properties":


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

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

...