Agenda - Council - 07/28/2015 - Laserfiche WebLink

Home

To: Lanya Ross, Anneka LaBelle, Ali Elhassan From: Evan Christianson, Ray Wuolo Subject: Metro Pumping Optimization 3 Date: April 2, 2015 Page: 6 The source code for this script is provided with the project deliverables and is documented internally. A brief description of how the script works is provided below for those not familiar with the python programing language. GWM-VI creates a file called MMProc.in jtf at the start of an optimization run that acts as a template file for well pumping rates. Throughout the optimization, GWM-VI (or a runner program called jrunner if running in parallel mode) uses MMProc.injtf to create a file called MMProc.in which contains pumping rates for MODFLOW to use. Updated pumping rates are pulled from MMProc.in and used by pyMMProc.py to generate a new Well (WEL) Package and Revised Multi -Node Well (MNW2) Package files for MODFLOW. pyMMProc.py then executes MODFLOW. After MODFLOW is completed, pyMMProc.py extracts hydraulic head and river flux data from MODFLOW output files associated with the head and river observation packages. Selected hydraulic head data are used to calculate groundwater flow -directions by solving a three-point problem. The deviation in groundwater flow direction from a provided base condition is then determined. The change in river flux from the base condition is also calculated. All hydraulic head, change in flow direction, and change in river flux are written to a file called Simulated Values.out which is read directly by GWM-VI. pyMMproc.py also checks to make sure that MODFLOW converged and that no pumping rates were reduced by the MNW2 or Upstream Weighting (UPW) Package. Convergence status and pumping rate status are written to a file called modflow.status which is read directly by GWM-VI. The use of pyMMproc.py necessitates slight modifications on how GWM-VI input files are set up that may not be initially intuitive. Input files were set up to treat all constraints, including baseflow and flow -direction constraints as head constraints. All constraint types are included in the head constraints (HEDCON) input file. This was necessary due to GWM-VI only supporting the Stream Package, whereas the Metro Model 3 uses the River Package. If GWM-VI input files were set up using the stream constraints (STRMCON) input file, GWM-VI would expect to find a Steam Package, which does not exist for Metro Model 3. 2.4 Limitations of GWM-VI During the course of this optimization several hindrances were encountered that relate to the GWM-VI software. We have notified the developers of GWM-VI about these issues; however, there is currently no timeline for fixing them. A discussion of these issues and current workarounds to each are described below. 1.) Solving of the linear program (LP) is not optimized or parallelized. The SLP solver used by GWM-VI has two main phases: 1) calculation of the response matrix, which requires MODFLOW to