A Flurry of Activity
If you've been following this blog, you'll see we jumped from V5.12 Build 1 to V5.16 Build 1. Here is a summary of what has changed since V5.12 Build 1:
- There was a problem encountered when importing an existing MODFLOW Well package using the option to create Analytic Wells instead of BC Wells. If there were more than 9 wells in a single cell, then the ones beyond 9 were omitted.
- We added an error checking function for Fracture Wells to make sure they do not have a bottom layer that is in a no-flow cell. Turns out that MODFLOW-SURFACT cannot deal with this situation, giving bogus results when this occurs.
- We had to modify our DXF import routine for map files to account for some unexpected things in the Civil CAD program.
- When importing a transient calibration target or analytic well from a text file, you can often get trailing commas on the ends of lines when using Excel. In the past, GV would not import this type of file properly. We added some code to ignore these trailing commas so you no longer have to edit these files in a text editor after generating them from Excel.
- GV has long had a version of MODFLOW96 in double precision. We now added a version of MODFLOW2000 that is also in double-precision. Just go to Model/MODFLOW/Packages and check the double precision flag beneath the MODFLOW version selector. You will notice that the DLL is changed from MF2KWIN32.dll to MF2KDPWIN32.dll. The binary output files from these double-precision versions of MODFLOW are in single-precision so that there are no incompatibility issues with MODPATH and MT3DMS.
- When color flooding matrix properties you can now specify that only cells within the bounds of the matrix are color flooded. A matrix property is one that does not have an associated zone database. For example, bottom elevations are by default a matrix property. You turn properties from zone to matrix using Props/Options. By default, GV will assign blue to the lowest value in the matrix and red to the highest and color flood in between. You can manually change the bounds on a matrix to change what value represents blue and red using Props/Property Values/Manually Reset Matrix Bounds. Normally any value less than the lowest bound would still be blue and any value above the maximum value is red. If you select Props/Options and uncheck the option at the bottom of the dialog, however, then GV will not put a color in these cells that lie beyond the bounds you have established.
- Those of you with good powers of observation will see a new submenu under Model/Pest called Null Space Monte Carlo. This is a powerful feature in Pest where you can generate any number of calibrated models, all with different properties. These calibrated models can then be used to evaluate model uncertainty. This is analogous to the Stochastic part of Groundwater Vistas, which generates realizations that are not necessarily calibrated. In the past, you would need to use "Post Conditioning" to throw out realizations that do not meet some calibration criteria. Anyway, we are in the beginning stages of supporting Null Space Monte Carlo. For now, your menu will be grayed out so you cannot access it. We hope that by late April we will have this finished and those of you with the Advanced or Enterprise versions of Vistas will be able to start using it.
- There was a problem encountered when importing an existing MODFLOW Well package using the option to create Analytic Wells instead of BC Wells. If there were more than 9 wells in a single cell, then the ones beyond 9 were omitted.
- We added an error checking function for Fracture Wells to make sure they do not have a bottom layer that is in a no-flow cell. Turns out that MODFLOW-SURFACT cannot deal with this situation, giving bogus results when this occurs.
- We had to modify our DXF import routine for map files to account for some unexpected things in the Civil CAD program.
- When importing a transient calibration target or analytic well from a text file, you can often get trailing commas on the ends of lines when using Excel. In the past, GV would not import this type of file properly. We added some code to ignore these trailing commas so you no longer have to edit these files in a text editor after generating them from Excel.
- GV has long had a version of MODFLOW96 in double precision. We now added a version of MODFLOW2000 that is also in double-precision. Just go to Model/MODFLOW/Packages and check the double precision flag beneath the MODFLOW version selector. You will notice that the DLL is changed from MF2KWIN32.dll to MF2KDPWIN32.dll. The binary output files from these double-precision versions of MODFLOW are in single-precision so that there are no incompatibility issues with MODPATH and MT3DMS.
- When color flooding matrix properties you can now specify that only cells within the bounds of the matrix are color flooded. A matrix property is one that does not have an associated zone database. For example, bottom elevations are by default a matrix property. You turn properties from zone to matrix using Props/Options. By default, GV will assign blue to the lowest value in the matrix and red to the highest and color flood in between. You can manually change the bounds on a matrix to change what value represents blue and red using Props/Property Values/Manually Reset Matrix Bounds. Normally any value less than the lowest bound would still be blue and any value above the maximum value is red. If you select Props/Options and uncheck the option at the bottom of the dialog, however, then GV will not put a color in these cells that lie beyond the bounds you have established.
- Those of you with good powers of observation will see a new submenu under Model/Pest called Null Space Monte Carlo. This is a powerful feature in Pest where you can generate any number of calibrated models, all with different properties. These calibrated models can then be used to evaluate model uncertainty. This is analogous to the Stochastic part of Groundwater Vistas, which generates realizations that are not necessarily calibrated. In the past, you would need to use "Post Conditioning" to throw out realizations that do not meet some calibration criteria. Anyway, we are in the beginning stages of supporting Null Space Monte Carlo. For now, your menu will be grayed out so you cannot access it. We hope that by late April we will have this finished and those of you with the Advanced or Enterprise versions of Vistas will be able to start using it.
posted by Jim Rumbaugh at 9:33 AM
0 Comments:
Post a Comment
<< Home