Jump to content
GMS, SMS, and WMS User Forum

Hydrology

Members
  • Content Count

    154
  • Joined

  • Last visited

Community Reputation

-3 Poor

About Hydrology

  • Rank
    Senior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I tried the PCGN solver and it was awesome to see it use 90% of my 24 cores. But, strangely the PCGN took 17 hours to run using all 24 cores, where the PCG solver only took 30 minutes to run basically using one core.
  2. Hi thanks for responding. I have the 64bit option and parallel option checked. I am using the PCG package. Has the PCG package not been parallized?
  3. I don't know if this should be under the MODFLOW directory, but I have been trying to see if I can speed up my GMS runs. I have a GMS MODFLOW model that is taking about an hour to run and I would like to shorten that run time. I see that I am using about 2.5% of my CPU utilization and I am running about 300 kB/s in disk access time, well below the capacity of the CPU or disk. I have a dual processore Xeon system with 12 cores for each processor running at 3.2GHz. My disk drive is 4-2TB M.2 NVME SSD's running in a Raid 0 array in a PCIe slot. The system has 256GB of RAM. This configu
  4. This is a little late for adding to this topic, but your path name is really long. Try shortening up your directory path name and see if that helps.
  5. I am setting a drain with a specific elevation in a MODFLOW run, but the final gw elevation for the cell that the drain is located in, is not the same as the elevation that I set for the drain. It seems to vary depending on the hydraulic conductivity that I set for the layer that the drain is in. For low layer conductivities, the final drain elevation in the cell is close to the elevation that i specified for the drain, but for higher layer conductivities, the gw elevation in the cell can be several feet higher than the specified drain elevation. How can I get the drain to force the elevati
  6. Wrong forum. Move your question to the WMS forum.
  7. I just recently started having a problem displaying the grid. I create the grid and it is visible, but as soon as I map it to Modflow, the grid within the model boundary dissapears. You can still see the grid outside the model boundary until you activate cells in coverage, then those grid lines as they should. I have played around with the display options in 3D Grid Data, but the cell edges will not display. I have this same problem on about 7 different GMS models. It seemed to just start about a week or two ago. Does anybody else have this problem, or know of a fix. I just figured out
  8. I think that the problem ended up being a conflict between GMS and our firewall "Comodo". GMS creates 5 or 6 batch files in the Temp directory every time you zoom or pan the display. It then executes the batch files sequentially to redraw the bitmap. Our firewall would send up a popup every time GMS executed one of those batch files because batch files can be a big security risk. These popups would often occur 300 to 500 times during a single GMS session. I tried turning the firewall off to avoid the warnings, and that is what caused GMS to stop displaying bitmapped graphics completely.
  9. The files are local, but are on a different drive than the model files. I will try moving them to the GMS model directory and see if that helps.
  10. I have been working with a GMS model with two TIFF files for background information. After several days of working correctly, the model stopped displaying the imagery. It always took a long time to display them, but after 30 sec to a minute they would display. I deleted the images and reopened them but GMS still does not diaplay them. I tried closing GMS and reopening it, but GMS will still not display them. Does anybody know what is causing this, or have a workaround?
  11. Here is the screen capture of the model crash.
  12. I have a weird problem. I have a transient model that runs fine if I set the Output Control to "Output at last time step of each stress period". But when I set Output Control to "Output At Every Time Step", the program immediately crashes when I try to run it. Has anybody run into this problem before? I have tried to attach a screen capture of the crash error, but the forum wont let me even though it is only 112KB. The MODFLOW output file just contains the first the few lines of the run header.
  13. Thanks Michal, I will experiment with that and see if that approach gives me what I need.
  14. Hi Bri, thanks for the response. I am familiar with the references that you indicated. I often use the specified head and head dependent flux boundaries. I havent used the specified flux boundary, but that is not what I am looking for. What I am trying to set up is a boundary condition that will allow free flow across the boundary without restriction, so that the flow across the boundary will vary in time, depending on the amount of water that i pump into or out of the model domain. I don't want to necessarily fix the head across the boundary either because I think that would overly const
  15. Is the default boundary condition in MODFLOW a no flow boundary? If so how would I create a boundary condition that allows flow, but has a fixed head at either end of the boundary?
×
×
  • Create New...