Jump to content
GMS, SMS, and WMS User Forum


  • Posts

  • Joined

  • Last visited

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Wellington, NZ

mwtoews's Achievements


Newbie (1/14)



  1. In MODFLOW-2005, PCG2 was upgraded to PCG7. As of GMS 10.0.10 (Jun 10 2015) only PCG2 is shown and supported, even when choosing either MODFLOW-2005 or related (such as MODFLOW-NWT). The only difference is the support of the optional [iHCOFADD] parameter, which is a flag that determines what happens to an active cell that is surrounded by dry cells: 0—cell converts to dry regardless of HCOF value. This is the default, which is the way PCG2 worked prior to the addition of this option.Not 0—cell converts to dry only if HCOF is 0 (no head-dependent stresses or storage terms) ) PCG2 should still be utilized for MODFLOW-2000. See more about this modification in RevisedMF2005Input.pdf and/or readme_PCG.txt
  2. Ok, it turns out this issue was related to Novell, although an IT Administrator needed to release the file locks. All good afterwards.
  3. When using a GMS 10.0 project, if my computer crashes, the project does not open when the computer starts up again. What I see if I try to open it is an error dialog: GMS 10.0 (64-bit) Could not open the file I:\path\to\my\file.gpr for reading/writing. File may be open in another process. Check permissions. None of the advice in the dialog is useful. It could be relevant that the project files are stored on a Novell Network drive, but only my one computer is using the project, and I don't see any properties with the "Novell Info" panel of the file properties that are different to any other GPR file. Furthermore, the normal files properties don't have anything different (e.g. "read-only" attribute is not active). Inspecting the same file with HDFView shows that the file is somehow "in use", so the HDF5 container appears to be locked. My workaround is to rename the GPR file to another name, and sometimes the prefix for the "_MODFLOW" directory too. Is there a better recovery technique?
  4. Currently with the conceptual model approach in GMS 10.0, arcs used to represent streamflow routing segments (SFR2) can be linked to nodes connected to polygons used to represent lakes (LAK3), however with the Map -> MODFLOW conceptual model conversion, the OUTSEG and INSEG IDs of the SFR2 Package are all 0, meaning their relations are not understood by GMS. As per the SFR specification, OUTSEG and INSEG connections to/from lakes are negative lake IDs. As a workaround, these need to be manually edited in the SFR2 MODFLOW dialog after performing a Map -> MODFLOW conversion. This feature request is to enable automatic LAK3 and SFR2 linkages with the conceptual model approach, as is currently done with reaches of SFR2 arcs. That is, identify OUTSEG and IUPSEG based on connections to either other streamflow routing reaches (positive) or lake IDs (negative). This can be automatically be done by identifying the direction and connection of SFR2 arcs to polygons associated with the Lake Package. A good example of combining stream and lake interactions is Test 2 of "A New Streamflow-Routing (SFR1) Package to Simulate Stream-Aquifer Interaction with MODFLOW-2000".
  5. Fantastic, I found and modified the registry key, and it works. Thanks!
  6. I have GMS 10.0, and I recall when I first opened up a text file, for instance a MODFLOW simulation listing file, GMS asked me my preferred text viewing application, with a default to Notepad.exe. Now I want to change it to a different text viewing program, however I cannot seem to find the setting. I've looked in the Preferences, and even reset to factory defaults, but I don't see where I can modify this. Any ideas on how to change the default text viewing application?
  7. When viewing a MODFLOW model using the Lake package (LAK), the Lake cells cannot normally be selected, unless either viewing the Ibound dataset or changing 3D Grid Display Options for Inactive cells. Note that the cells in Ortho mode appear to be missing (empty fill), as they are inactive, but still have a Lake MODFLOW BC Symbol in the center. The error message when attempting to select a Lake cell is "You must first select a gridcell(s) in order to change its attributes." This is because the cells are coded as inactive (IBOUND = 0), as specified by the LAK Package. It would be nice to allow the the "Select Cells" tool to be allowed to select cells that use the Lake BC, without needing to change the inactive cell option in the 3D Grid Display option or when viewing the Ibound dataset.
  8. When starting a new GMS project, I find that I keep needing to remember to reset metric units. Units such as "ft" are almost exclusively used in the United States, but most other countries use length units of "m". Thus, I find myself frequently going to "Display > Display Projection" and correcting both Horizontal and Vertical units. Even if I import a spatially referenced file (e.g., with a .prj file) with a projected metric coordinate system (e.g., UTM), it will update the Global projection with metric units, but the vertical projection will still remain as "U.S. Survey Feet". As I need to repetitively change these units for each new project, it would be of great convenience to have the project default units set in the Preferences dialog, rather than assuming default "ft". Even further, the "Factory Preferences" used to first populate the Preferences could determine if the computer uses metric units based on the locale, but this would be getting fancy.
  9. With the "Grid Overlay" method of the "Solids -> MODFLOW" operation, I would like to have a thickness bias option. This would be easy to add to the existing dialog (underneath Minimum Thickness): The purpose of allowing a thickness bias option of, e.g. 0.75, would create thinner grid cells near the top, and thicker grid cells near the bottom. This bias principle is the same when creating a 3D Grid for MODFLOW, and should not be difficult to enable. Currently there isn't a bias control, so it is effectively 1, which creates equal cell thicknesses for all layers at a given grid location. Simply put, there is better geologic data and more interesting GW interactions near the surface, so I would like the grid to be refined near the surface. As a result of more geologic information near the surface, my Solids data are often more detailed near the surface, and less detailed and with less certainty at depth. This level of detail near the surface is neglected with no bias control.
  10. This could be due to many things. First, it should converge with the WEL package turned off. Second, check your units to make sure they make sense. I'm guessing you are using either days or years, in which case, double check your hydraulic conductivities and pump rates so they have the same time dimensions (and that they conceptually make sense, such that you aren't pumping excessively high for certain materials). If these don't work, try increasing the number of time steps per stress periods, and try modifying the multiplier to something like 1.2 or so. (You may want to change some output control options to reduce the size of files from your simulation, since you may not need to record each time step, and just keep the last time step for the end of month.)
  • Create New...