Jump to content
GMS, SMS, and WMS User Forum

Rob Virtue

Members
  • Content count

    36
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Rob Virtue

  • Rank
    Senior Member

Profile Information

  • Location
    Australia
  1. Fonts and Icons in 10.3

    In Windows 7 (and presumably other versions) , it depends on the font size selected under Control Panel\All Control Panel Items\Display.
  2. TINs Question

    Dunaj, Check under HELP>REGISTER> that you have the TIN module enabled.
  3. Invalid Head File

    I used to get this a lot but it's been a while. If it is a transient model, make sure there are no observations in the first time step (or maybe first stress period?) . This can stop the model running or the head file saving properly.
  4. ET surface

    Kirk, We had the same issue recently (18 September 2015), with the option for "2D Dataset -> Array" being greyed out, and were given this work-around from Jack at Aquaveo support. It seems to have worked. "Currently the option to use the "2D Dataset -> Array" command for U-Grids is not available, however I believe that the developers are working to implement it in future versions of GMS. I've got a possible work-around for you. This assumes that your topographic surface can be represented as a 2D scatter set or TIN. In this case right-click on your U-Grid and select 3D->2D, and then select layer 1 so as to make a 2D U-Grid of the top layer of your 3D U-Grid. This ensures that the cell IDs of layer 1 in your 3D U-Grid line up with the cell IDs of the 2D U-Grid. Now select the 2D U-Grid to ensure that it is the active U-Grid, and select the topographic surface data that you have and convert it to a 2D scatter set. Then interpolate that 2D scatter set to the 2D U-Grid. Now you will right-click on the interpolated dataset on the 2D U-Grid, and select "View Values". Copy the column of f values here, click ok to exit that dialog and bring up the dialog for the EVT package on the 3D U-Grid. Now paste in those values to the array for the EVT package. You can check to make sure that the cell IDs are the same and line up all right. If you have trouble doing this, please let us know."
  5. Errors in Model checker

    Mina, I suspect you have specified head cells with the head elevation set below the base of the cell, which causes a terminal error. Use the automatic layer assignment option to ensure the elevations are set at the uppermost cell ("Auto assign to one cell") or the uppermost and all underlying cells ("Auto-assign including lower cells") where the elevation is above the base of the cell. If you are using transient heads, be aware that automatic layer assignment seems to use the elevations from the first stress period.
  6. Is this feature being added?
  7. Mgozdor, This occurs if you have the "use to define model boundary (active area)" box checked in ANY coverage in addition to your activation coverage. This is a common problem at the moment, because if you select "layer range" in a coverage, it automatically checks the "..active area)" box. A bit annoying really. It will cause the activation errors whether you map the coverage to the model or not, so make sure you check ALL of your coverage.
  8. PEST

    I am having the same problem (GMS 10.0.6). It appears that PEST is looking for flow observations for DRN and CHD boundaries, even though there are no coverages with flow observations in the current model.
  9. GMS transient flow model

    If you have a high conductance value for the general head boundary relative to the cell K, it will act as a variable head cell as there is not a significant restriction to flow. If you drop the conductance to a very low value relative to K (conductance can be varied over time just like head) flow is restricted so that the is negligable exchange to and from the GHB term. By varying the conductance, the GHB can be used like adding or removing a constant/variable head boundary, without the need to stop and start the model.
  10. GMS transient flow model

    Another option would be to use a general head boundary instead, with heads as you are using for the constant head boundary, and use the conductance values to turn it "on" and "off".
  11. Worldview temp files causing crash

    I was editing a large model and added one new scatter point, which caused GMS to crash. I could then not reopen the model. After the panic attack subsided, I noticed that my hard drive was full. After deleting or moving about 3 GB of files off my hard drive the model opened and edited OK for a while and then crashed again. I noticed the hard drive was full again and did some hunting around and found that there was about 30 GB of world imagery files in \temp. Two Lesson: - make sure the "online maps" box not checked in GIS once the image is downloaded, to prevent is downloading again every time the view changes; and - regularly clear the cache (under "advanced" options in "get on line maps") or delete temp files. Panic over and back to the model. And backing up the model.
  12. Are transient TINS and PHT3D in the recent release of GMS9.1.1?
  13. It would be handy to be able to have a small comment field attached to various data bases, coverages, scatter point stes etc to explain their use. For example there may be multiple recharge coverages for different climates or development scenarios. While this can be adressed to some extent with the coverage/set name, when more detail is required this would result in a very long and complicated names.
  14. Layer material coverage trap

    Alan, I created the first layer coverage with materials and various boundary conditions (GHB, RCH, DRN) assigned to layer 1-1. I then copied the coverage to produce the materials + colour polygons for the lower layers (2-4) and unclicked all the boundary/source/aerial property conditions, so that the copies only mapped colour and materials. Despite changing the materials and colours in the new coverages, when they were all mapped only the layer 1 materials applied. If I mapped the layers individually all was well, until I mapped the top layer. The problem was fixed by creating another copy of the primary, layer 1 coverage, for layer 1 materials and colour only. Thus I ended up with 5 coverages: boundary conditions for layer 1 (all other layers had no-flow external boundaries and no internal boundaries); then materials and colour for layers 1-4. It is not a problem I have ever noticed before, although I do not often use coverages to apply materials to layers.
  15. Layer material coverage trap

    Using 8.3.5 (and presumably older versions). If you are using material coverages for different layers, do not combine other attributes in the material coverage. If you include recharge in one of the material layers (typically layer 1) it will copy the material along with recharge from that coverage over all layers. If only materials (and colour) are used in the coverages, they map properly to the appropriate layers.
×