modflow-usgs / zonebudget Goto Github PK

Chris,

In the Great Basin version 3 model, I have zones that split some of the hydrographic areas into mountains and valleys. The zones were already 3 digits so that they could (in most cases) match the official HA number. To split them I added a fourth digit. Zonebudget seems to be able to handle this, and the .csv and .2.csv files are readable, although there is no space between the word zone and the number. The .zblst file, however, prints those zone numbers out as ***. This causes a problem when trying to use GWChart to look at things. Is there any way to fix that? And if you are changing things anyway, is there any way to make Zonebudget work with alphanumeric zones instead of only numeric zones. That way I wouldn't have to name HA 240B, for example, as 340 because HA 240A is already named 240. And flow regions could be named by an abbreviation instead of a number that means nothing.

I'm underfunded this year. If you could send me funding and money to get a compiler, I could look at this.

Lynette

Lynette E. Brooks, P.E.
Hydrologist
U.S. Geological Survey
Utah Water Science Center
2329 Orton Circle
Salt Lake City, Utah 84119-2047
(801) 908-5014

I think we may have found a bug in zone budget (in zonbudusg, but also likely in structured zone budget), and I wanted to get your opinion to see if I am missing something obvious. Here is the situation:

1. Compact budget option is NOT used
2. Wells are on in stress period 1 but later, the number of active wells is specified as 0
3. Zone budget is asked to write a CSV2 file

In this situation, the non-compact budget file has an entry for WELLS in stress period 1, but it does not have an entry later on. It appears that zone budget gets confused for the CSV2 case because the number of columns has changed.

Does this sound like something you have encountered or seen before? When I run the model with COMPACT BUDGET everything works as expected.

If this is a bug, it seems like a fix would be to read through the entire budget file and determine names for all of the columns, and then go back and process the file.

The SWI flow terms need to be added to FLOW RIGHT FACE, etc.