NGMS - Software workshop pre-release PR07

Discussions

Peter Gijsbers

16-17 January 2008NGMS4 - PR07 software workshop 2

Recharge pilot

16-17 January 2008NGMS4 - PR07 software workshop 3

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 byWillem van Deursen (PCRAster Environmental Software) Janet Rily (ESI) &Tim Leewis (Entec)

16-17 January 2008NGMS4 - PR07 software workshop 4

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

16-17 January 2008NGMS4 - PR07 software workshop 5

Recharge pilot results (EA-recharge)

16-17 January 2008NGMS4 - PR07 software workshop 6

Recharge pilot results (4R)

7NGMS4 - PR07 software workshop 16-17 January 2008

Model run and scenario issues

16-17 January 2008NGMS4 - PR07 software workshop 8

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

16-17 January 2008NGMS4 - PR07 software workshop 9

Presentation issues

Transmissivity and Thickness ? static dynamic

Boundary fluxes ?

Evaporation ?

16-17 January 2008NGMS4 - PR07 software workshop 10

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

16-17 January 2008NGMS4 - PR07 software workshop 11

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

16-17 January 2008NGMS4 - PR07 software workshop 12

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

16-17 January 2008NGMS4 - PR07 software workshop 13

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

16-17 January 2008NGMS4 - PR07 software workshop 14

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

16-17 January 2008NGMS4 - PR07 software workshop 15

Output acceptance

16-17 January 2008NGMS4 - PR07 software workshop 16

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

16-17 January 2008NGMS4 - PR07 software workshop 17

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

16-17 January 2008NGMS4 - PR07 software workshop 18

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

16-17 January 2008NGMS4 - PR07 software workshop 19

Archiving

16-17 January 2008NGMS4 - PR07 software workshop 20

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

16-17 January 2008NGMS4 - PR07 software workshop 21

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 ?