Jump to content
GMS, SMS, and WMS User Forum


Popular Content

Showing content with the highest reputation since 07/28/2009 in all areas

  1. 1 point
    When you open a GMS:FEMWATER project, GMS does not read in the print times.
  2. 1 point
    Just as an update - we rewrote some of the code in SMS to reduce the amount of memory used while reading in large scatter sets. You should now be able to read in large scatter sets and still check the triangulate button.
  3. 1 point
    I don't think that is quite right. There are two compressibilities: The value supplied to the MP3 card (beta) is the compressibility of water in units of L T^2/M. According to the manual (page 41) Femwater converts this to modified compressibility (betap, Equation A23, manual page 93). This occurs at line 5137 of the source code. So GMS should not (and I think does not) modify this. Freeze & Cherry (1979, page 529) suggest a value of 4.4E-10 m^2/N = 5.9E-20 m d^2/kg, similar to what Rob quoted. The value supplied to the MP2 card (alp) is the compressibility of the medium, also in units of L T^2/M. According to the manual (page 47) Femwater converts this to modified compressibility (alp, Equation A22, manual page 93). This occurs at line 5109 of the source code. GMS should not (and I think does not) modify this. Freeze and Cherry (1979, page 55) suggest values of 1E-6 to 1E-11 m^2/N across a range of materials. By the way, I am using GMS 6.5.6.
  4. 1 point
    I am running a contaminant transport model in FEMWATER. I am wondering if I have set up the dispersion coefficient parameters correctly. In the FEMWATER manual it gives the equation for the D tensor as theta D = aT |V| delta + (aL-aT) V^2 / |V| + am theta tau delta where theta is the moisture content (not the porosity) delta is the Kronecker delta function (basically an identity matrix) am * tau is the molecular diffusivity D* V is the fluid velocity aL is the longitudianl dispersivity aT is the transverse dispersivity My problem is the first theta. In all the other references I have seen it is not there, for example Zheng & Bennett 2002. I am wondering if it is a typo. If it is not a typo then the parameters in this equation are different the usual form such as given in Zheng & Bennett and it would make a big difference. Would appreciate your help. Thanks. Edit: Update: Actually V in the above equation is the Darcy velocity = theta * Fluid (seepage) velocity. So theta appears in every term. It seems this equation is the correct form for unsaturated conditions. My mistake.
  5. 1 point
    Onur, Thank you - it is much easier to fix problems with a smaller case. I will keep you updated of any progress we make. Regards, John
  6. 1 point
    I believe ADCIRC may be more stable when wetting and drying is occurring. However, if you want to use your hydrodynamic solution to run RMA4, you will need an RMA2 solution. It sounds like you have most of the data you would need to use the reflection / absorption BC - can you also get TAREA? You may also want to consider extending the mesh if possible so you don't need to use a reflection / absorption BC. It is more difficult to get a solution from models with wetting / drying - I also believe the reflection / absorption BC can be difficult, and it is hard to know what value to use for BETA.
  7. 1 point
    Are you able to extend the domain further upstream? If you are, I believe this would be preferable to using the reflection/absorption BC. The user manual also offers the warning, "This boundary condition has been found to work far better when applied to a one-dimensional element rather than to a two-dimensional element." Although the reflection / absorption boundary condition does not require transient water surface elevation data (how the water surface elevation changes with time), it DOES require other information, such as the steady state water surface (SSWSE) and flowrate (AC1X) to be known / specified. As stated in the manual, SSWSE is the mean value about which the progressive or reflective wave crossing the boundary oscillates. You said no precise flowrate data is available for the upstream boundary. In this case, I don't think you will be able to use the Reflective / Absorption boundary condition since flowrate information is required as part of the specification of a reflection / absorption boundary condition. From page 145 of RMA2 user manual VARIABLE, VALUE, DESCRIPTION AC1X -, 0, + Average (net) river discharge ft3/sec or m3/sec, (Variable Qo in the equation below). BETA 0 to 1 Reflection/Absorption coefficient used to calculate A2 in the rating curve equation below. BETA = 1 specifies total reflection at the boundary. BETA = 0 specifies total absorption at boundary. SSWSE -, 0, + The steady state solution for the water surface elevation at the first node on the specified continuity line number. If SSWSE is less than or equal to zero, RMA2 will incorporate the steady state solution (Eo) before advancing to dynamic. Note: If Hotstarting a steady state run, use a value of –1. If Hotstarting a non-steady state (dynamic) run, you must supply SSWSE with at least 4 significant figures past the decimal. THETA -, 0, + Direction of flow into the mesh in radians measured counterclockwise from the x axis. Note: The program adjusts the boundary directions to maintain flow parallel to the edges for nodes at the ends of the continuity line. TAREA 0, + Surface area of tidal storage beyond the boundary. Used in defining standing wave flows. TAREA is the maximum tidal discharge divided by the maximum fall rate of water surface for a given time step. TAREA = Velocitymax * Width * Depth / Rmax Rmax = Δ WSELV / (ΔT * 3600)
  8. 1 point
    SMS 10.1 Beta launch We are ready to release the beta version of SMS 10.1. This version has been in development for approximately a year and a half and has numerous new features and feature enhancements. You can download the executable from the following link: SMS 10.1 Download What's New We have focused special attention to working on features that all SMS users can benefit from regardless of the numeric engine you use with SMS. 64-bit version available. The installation comes with installations for both the 32-bit and 64-bit versions of SMS. The 64-bit version requires a 64-bit operating system to run and use. We have made particularly useful improvements in dealing with TINS in the scatter module including: breakline support including several creation options, GIS and AutoCAD conversion options which preserve triangulation, and the ability to merge scattersets of different priorities and maintain the initial triangulation in non-overlapping areas. Another new feature is the dataset toolbox which includes several new options for creating datasets from existing data. Annotations is a new feature for creating North Arrows, screen space images (logos), scale bars, as well as rectangles, lines, and ovals. The new annotations exist in layers that can be turned off and on independently. In addition to the general improvements made to the SMS interface, several of the model interfaces have been updated and improved. These are only a few of the new features of SMS 10.1. For a full list of our new features, please see the following page on our wiki: http://www.xmswiki.com/xms/What's_New_in_SMS_10.1 Licensing The beta version of SMS 10.1 works with your existing SMS 10.0 registration and should work automatically. When SMS 10.1 is released in full, passwords will be available for all users with up to date maintenance contracts. Contact sales@aquaveo.com to get your maintenance up to date to prepare for the SMS 10.1 release. Feedback We are interested in your experiences with SMS particularly during the beta period. Please send feedback to sms.feedback@aquaveo.com. A Word About Beta Software This beta release is meant for experimentation and testing purposes only and not for production work. We will continue to develop this release until we feel it is suitable for final release. Please keep a backup of your files in the event something does go wrong during your testing. We welcome any feedback you may have.
  9. 1 point
    Rusty, How do I recover the autosaved files? Chris
  10. 1 point
    Ok you're talking about Soil properties for unsaturated zone in FEMWATER (SP1 card) (next time be more specific) Yes I agree the preset Silt in GMS:FEMWATER is different from the parameters in Table 5 in the FEMWATER manual. The parameters in the manual are just examples, maybe they changed the defaults for GMS. Or there may be an error in the manual or in GMS. I notice that the alpha parameter is inverse-length-dependent, maybe they don't adjust the default value properly for units in GMS.
  11. 1 point
    I think combining would be better (at the moment, with small member numbers) because 1) some of the MODFLOW forum issues are probably actually GMS issues, so I want to know about them. 2) more people means more help with my problems. 3) more activity would make the forum better, it might get to critical mass.
  12. 1 point
    Good afternoon, I have a *.tif image that I'm using as a SMS background while I'm developing an ADCIRC mesh. The image was originally unreferenced, and I geo-referenced it to NAD83 via the "Register Image" option. I then loaded in my lat/lon *.cst file, and the CST data and the image line up very nicely. So, I'm assuming I did all that correctly... After creating an ocean boundary, I then transformed my project coordinates to UTM NAD83 (zone 18), and the image and CST data seem to transform differently. The CST data skews to the left, while the image skews to the right, although the two still overlap. Based on previous experience, I'm guessing that the CST transformed correctly, while the image did not. I took snapshots of the SMS screen before and after transformation, and uploaded them in the file "mdp_conversion_problem.jpg" (83Kb) to demonstrate the issue. Do you have any suggestions? Thanks, -- Mark
  13. 1 point
    Mark, We received your files and I just took a look at them. I was able to reproduce the issue with the files you sent. I have submitted it for review. Thank you, John
  14. 1 point
    I am trying to run a contaminant transport simulation using GSM:FEMWATER. I am getting several bugs. First, I set up a steady state flow model and ran that. All fine. Although I notice that GMS doesn't save and reload several simulation options properly (name of existing geometry file to use, geometry titles, parameters in van Genuchten curve generator). Then I created a transient transport only model. I copied the (ascii) geometry (3dm) and pressure head (phd) files from my flow solution into the same folder as the transport model super (fws) file. I defined a cold start with initial concentration 0 everywhere, and using my steady state ascii phd file from the flow model solution. FEMWATER iterates and converges fine, but when I plot the solution (con) it looks like I am only getting dispersion, and no advection. I am guessing there is a bug with how it imports and uses the pressure heads from my flow solution. I have also tried a coupled flow and transport model, and I get the same results. Has anyone out there successfully run a FEMWATER Transport model?
  15. 1 point
    Hi Simon and cnr3, @ Simon: Thank you for passing my query. @cnr3: Thank you for your response. This time I send a 2D mesh and a cross section of my model. The locations with the large vertical extents are tailings. I tried to do as you told me. I changed the material outside the tailings to the material 'Mutterboden' for all layers. This can be done quite comfortable because by draging several elements the elements in all layers are marked and the material can be changed for them. As victim for this I loose my lowest layer. Leaving the vertical extent of the layers which pinch out at 0.001 m the model still doesn't react outside the tailings. Changing the material inside the tailings is practically not possible since you have to select every single element with one mouseclick, for every sublayer! So I decided now to increase the vertical extent of the pinched out layers to 0.5 m although it is not correct. So the model reacts everywhere, but still it reacts most in the tailings. I also send a cross section of the new model. If you or someone else has a better idea, let me know. Thanks Maik
  16. 1 point
    Many Thanks for Responce Sean, I have managed the data entry using another text editor.I was lucky because I have only 4 year simulations , not too much data, but I have to note that one has to check GMS after using its xy series editor.Some times it can give you different things . Regards
  17. 1 point
    I can see it is a problem, but can't really say what is going on. "It is not allow me to enter originals." That's the part that concerns me more than anything. If you can't figure out a way to do it in the program, edit the recharge file outside of GMS with a text editor and then open up your model again.
  18. 1 point
    Matevz, You may want to check your units. They should be consistent each time your are entering parameters for the model. The "Edit | Units" dialog should be set up correctly, and these units should be used in each subsequent step. In the "Seep2D | Analysis Options" dialog, is the "Compute flow lines" check box activated? If not, it should be in order for them to appear. Regards, Todd XMS Technical Support
  19. 1 point
    Sorry to hear of your troubles. We aren't aware of problems with dragging nodes. If you can find a set of repeatable steps, please contact our technical support and give them a description of the steps so we can get this fixed. There were a couple changes in SMS 10.0 that affect memory use. One change would give some savings to overall memory use was how we allocated storage. This gives some memory savings but the bigger effect was faster building of scattersets. If you are talking about switching from SMS 9.0 to SMS 10.0, you would also have the changes impacted by the development of SMS 9.2. I can't remember all of the details of the changes between these versions, but something along the way might have increased our memory use for some kinds of data. Are you saying that in SMS 9.0, you could have the original scatter set and 5 sub-sets all in SMS at the same time? What size of a scatterset are you working with? Off the top of my head, I'm not sure that I have a definitive recommendation. You could try filtering your scatter set. If you use a small angle like 1 or 2 degrees, it will only remove points that really do not contribute much of anything to the shape of the surface. However, if you are running up against the memory limit performing the filter may itself cause you to exceed the memory limit. In the next version of SMS, we plan to distribute a 64-bit version of our software which may help alleviate some problems like this. You will want a computer with lots of available RAM to work with large datasets in this version. The 64-bit version has pros and cons. It allows you to access far more memory with a single process, but the data storage mechanism requires more memory. We hope that this version will be released in beta sometime in the next month or two. Sorry that this is not an immediate help. I would be interested to look at your data to try some things to see if I could come up with some more solid recommendations. Could you contact our technical support and get them your data? If that is possible, it would help us give you better guidance for your situation.
  20. 1 point
    Our latest newsletter is available for viewing on our News Page: January 2009 Newsletter (PDF, 846 KB) Previous newsletters: October 2008 Newsletter (PDF, 2.12MB) July 2008 Newsletter (PDF, 628 KB) April 2008 Newsletter (PDF, 395 KB) January 2008 Newsletter (PDF, 200 KB) October 2007 Newsletter (PDF, 826 KB)
  21. 1 point
    I've been transferring a model back and forth from a computer with XP to one with Vista and am finding that when I'm in Vista, the labels for the materials legend, borehole names, and horizon IDs all show up as symbols rather than text. Any thoughts on this? This occurs in both v6.0 and v6.5.
  22. 1 point
    Joel, You may also want to make sure that you have turned on "Currents" in the PTM Model control on the computations page. There are very few times when this should not be turned on.
  23. 1 point
    Hi all I have been trying to run a simple PTM run to test it's capabilities. First I tried forcing the particles with outputs from a CMS-FLOW simulation I completed recently. While I followed the documentation as closely as I could, and was confident that I had set everything up correctly, the model would not run, and kept giving the following error message: forrtl: severe (157): Program Exception - access violation I thought that perhaps the problem was with using the CMS-FLOW outputs, so I tried to force the particles with outputs from the ADCIRC tutorial simulation. Again, after setting up the model I received the same error. I have tried a number of variations on the model setup: different time steps, with and without particle sources/traps, etc. I also downloaded and installed the latest model exe updates, without success. If someone could provide any insight on whether I'm doing something wrong, or whether there is a bug in the model it would be much appreciated. Regards Joel
  24. 1 point
    It looks like your computer is good enough to handle it, so it must be something else. If you would like, you can contact support@aquaveo.com and we will look at your files.
  25. 1 point
    GMS 6.0 and 6.5 do not support Windows Vista. The next version of GMS will support Vista. You can run GMS on Vista but you will get these display oddities, typically dealing with fonts.