Skip to main content

Integrated groundwater and surface water modeling: how to make use of the MODFLOW Listing file

Whatever version of MODFLOW you are using for groundwater modeling, knowing how to make use of the list file can help a lot to understand what you are actually doing.

As the official MODFLOW manual document describes:
"The Listing File is a key file to which model output is written. As MODFLOW runs, information is written to the Listing File, including much of the input data (as a record of the simulation) and calculated results."
"The Listing File includes a summary of the input data read for all packages. In addition, the Listing File optionally contains calculated head and drawdown controlled by layer and time step, and the overall volumetric budget controlled by time step. The Listing File also contains information about solver convergence and error messages. Output to other files can include head, drawdown, and cell-by-cell flow terms for use in calculations external to the model or in user-supplied applications such as plotting programs."

Therefore, the Listing file actually contains a lot of important information.
In my point of view, the Listing file is a critical way to examine some important variables and outputs. I will briefly talk about several usage of the Listing file with a few examples.

First, the Listing file can used to output all types of inputs in a readable way. MODFLOW provides several utilities to read different types of data. One of them would be real array data. However, a lot of time, even you have prepared the right data, it may not be in the right format or right order. The executable program will run anyway, but none of the inputs actually makes any sense. You probably are not aware of these types of situation at all. For example, you were supposed to input the initial head for three layers, and you mistakenly messed up the order of the layers. But the program will not give a red alert at all. However, if you output this inputs into the Listing file, it maybe very easy for you to catch this error. Another good example is that when have used specific storage (Ss) when the the specific yield (Sy) is needed. When you looked the Listing file, you can immediately pinpoint this issue. Again, the program will probably not complain when you gave a unusual value because it is still within the range.

Second, one of the most annoying parts of a successful MODFLOW simulation is the convergence. A lot of time has been wasted trying to converge. In fact, the Listing file contains very useful information for you to debug the problem. By looking at the convergence information, you can easily identify which cell is causing the problem and infer the reasons. You can also look at the volume changes of each terms (e.g. stream leakage) to identify the water balance issue. With appropriate adjustments, you can quickly improve the convergence efficiency using the water balance information.

Comments are welcome! 


Popular posts from this blog

Spatial datasets operations: mask raster using region of interest

Climate change related studies usually involve spatial datasets extraction from a larger domain.
In this article, I will briefly discuss some potential issues and solutions.

In the most common scenario, we need to extract a raster file using a polygon based shapefile. And I will focus as an example.

In a typical desktop application such as ArcMap or ENVI, this is usually done with a tool called clip or extract using mask or ROI.

Before any analysis can be done, it is the best practice to project all datasets into the same projection.

If you are lucky enough, you may find that the polygon you will use actually matches up with the raster grid perfectly. But it rarely happens unless you created the shapefile using "fishnet" or other approaches.

What if luck is not with you? The algorithm within these tool usually will make the best estimate of the value based on the location. The nearest re-sample, but not limited to, will be used to calculate the value. But what about the outp…

Numerical simulation: ode/pde solver and spin-up

For Earth Science model development, I inevitably have to deal with ODE and PDE equations. I also have come across some discussion related to this topic, i.e.,

In an attempt to answer this question, as well as redefine the problem I am dealing with, I decided to organize some materials to illustrate our current state on this topic.

Models are essentially equations. In Earth Science, these equations are usually ODE or PDE. So I want to discuss this from a mathematical perspective.

Ideally, we want to solve these ODE/PDE with initial condition (IC) and boundary condition (BC) using various numerical methods.

Because of the nature of geology, everything is similar to its neighbors. So we can construct a system of equations which may have multiple equation for each single grid cell. Now we have an array of equation…

Lessons I have learnt during E3SM development

I have been involved with the E3SM development since I joined PNNL as a postdoc. Over the course of time, I have learnt a lot from the E3SM model. I also found many issues within the model, which reflects lots of similar struggles in the lifespan of software engineering.

Here I list a few major ones that we all dislike but they are around in almost every project we have worked on.

Excessive usage of existing framework even it is not meant to Working in a large project means that you should NOT re-invent the wheels if they are already there. But more often, developers tend to use existing data types and functions even when they were not designed to do so. The reason is simple: it is easier to use existing ones than to create new ones. For example, in E3SM, there was not a data type to transfer data between river and land. Instead, developers use the data type designed for atmosphere and land to do the job. While it is ok to do so, it added unnecessary confusion for future development a…