1. NGMS - Software workshop pre-release PR07 Discussions Peter Gijsbers

2. 16-17 January 2008NGMS4 - PR07 software workshop2 Recharge pilot

3. 16-17 January 2008NGMS4 - PR07 software workshop3 Recharge pilot Purpose:. investigate if PCRaster dynamic script language could be used to represented recharge proces models   prevents the need for recharge module adapters   may provide flexibility in recharge modelling. Case studies  East Kent (EA-Recharge)  Test Itchen (4R). Conducted by  Willem van Deursen (PCRAster Environmental Software)  Janet Rily (ESI) &Tim Leewis (Entec)

4. 16-17 January 2008NGMS4 - PR07 software workshop4 Recharge pilot conclusions Conclusions  both EA and 4R models are straightforward to convert to PCRaster script  EA, 4R and PCRaster model outcomes are practically similar  delays and exchange to Modflow have to be dealt with in NGMS  not all options of 4R and EA-code dealt with, but no reason to believe it cannot be dealt with  some minor issues in process representation require attention in future  data conversion is straightforward, can be automized  uniform naming/identification scheme desired for soil types, crop types, geology typesand land use types

5. 16-17 January 2008NGMS4 - PR07 software workshop5 Recharge pilot results (EA-recharge)

6. 16-17 January 2008NGMS4 - PR07 software workshop6 Recharge pilot results (4R)

7. 16-17 January 2008NGMS4 - PR07 software workshop7 Model run and scenario issues

8. 16-17 January 2008NGMS4 - PR07 software workshop8 In general Models handed over are not consistent  how consistent should they be on the system >transmissivity & thickness >boundary fluxes >horizontal flows >evaporation  Better instructions needed from seniors/custodians

9. 16-17 January 2008NGMS4 - PR07 software workshop9 Presentation issues Transmissivity and Thickness ?  static  dynamic Boundary fluxes ? Evaporation ?

10. 16-17 January 2008NGMS4 - PR07 software workshop10 Temporal resolution. monthly. half-monthly. each 10 days. each 3 days (output only). daily (run in combination with monthly) High resolution creates large data sets  few Gbs  compression algorithms cannot beat this  network and download times are affected

11. 16-17 January 2008NGMS4 - PR07 software workshop11 Are those resolutions needed ? Run purpose:  scanning alternatives  detailed analysis of preferred alternative  Most runs can be done with larger step size  Some runs require the temporal details

12. 16-17 January 2008NGMS4 - PR07 software workshop12 Resolution Proposal Distinguish two types of runs (if indicated and prepared by custodian)  monthly (or as needed for flow representation)  detailed (e.g. daily or 3 daily) Advantage:  most runs require have ‘small’ output sets >faster runtime >faster download >smaller database / less free disk space needed  few runs require details >no problem to wait Disadvantage:  more maintenance (configuration)  Scenarios need to be redefined

13. 16-17 January 2008NGMS4 - PR07 software workshop13 Scenario definition issues - accommodated Accommodated:. modification of existing groundwater abstractions. specification of new groundwater abstractions. input file selection (e.g. LTA) Not tested:. modification of existing surface water abstractions/discharges

14. 16-17 January 2008NGMS4 - PR07 software workshop14 Scenario definition issues – what else ? Recharge:. rainfall: pointbased or grid based ? Abstractions:. Ely Ouse: abstractions 50% of LTA Groundwater schemes  how/where  what (thresholds, time series ?)

15. 16-17 January 2008NGMS4 - PR07 software workshop15 Output acceptance

16. 16-17 January 2008NGMS4 - PR07 software workshop16 Acceptance Responsibilities. Custodians are responsible for testing and acceptance of model outputs. HQ is responsible for testing and acceptance of software features Please don’t wait till the last end Ask for a stand alone application if desired Testing takes place in June/July/August  reserve time

17. 16-17 January 2008NGMS4 - PR07 software workshop17 Output check. Requires small test plan per model. which runs. which outputs (parameters/locations/balances). criteria for acceptable deviation to pass test Note. default runs: use all Modflow files as is. modified runs: RCH and WEL are generated by NGMS/ModuleAdapter. Modflow-executables are compiled with Intel compiler version 10

18. 16-17 January 2008NGMS4 - PR07 software workshop18 Output check Default runs. compare Modflow.out from NGMS with original. compare output from NGMS with original at selected locations. compare water balances from NGMS with original Modified runs. compare difference between NGMS_default and NGMS_modified run without any modifications

19. 16-17 January 2008NGMS4 - PR07 software workshop19 Archiving

20. 16-17 January 2008NGMS4 - PR07 software workshop20 Archiving – why and when do you use it ? When to use to archiving ?. ….. What to archive. default scenarios. valuable what-if scenarios When. after  before uploading/upgrading new model How ?. manually  scheduled

21. 16-17 January 2008NGMS4 - PR07 software workshop21 Archiving – what (content and procedure) What content to archive. default scenarios. valuable what-if scenarios What procedure. after  before uploading/upgrading new model. How ?: manually  scheduled. Who ?