Jump to content
GMS, SMS, and WMS User Forum


Popular Content

Showing most liked content since 07/28/2009 in all areas

  1. 2 points
    Include an option to export/save materials from the "Edit | Materials" window. The user who suggested this to us asked: "Is there a way to save the materials designations (by this I mean the name, color, pattern, and so forth of the soil units or horizons) so that these can easily be imported into a new project. I realize they are saved if I save the project I created them in, but I’d like to be able to just import this information if I create a new project rather than having to rebuild the designations."
  2. 2 points
    Unfortunately, there is not an automated method to export well transient pumping data for all wells in the format you'd like it to be in. However you can export out the pumping data for each well (if you have them assigned as feature points in the map module) by following the steps below. 1. Double click on a feature point representing a well with transient pumping data 2. Select the button in the "Flow rate" column with the three dots to bring up the XY Series Editor 3. Select the "Export..." button 4. Specify the file name and location and then select "Save" I realize that with many wells this will be a tedious process. I am therefore submitting this as a feature request to the GMS developers. I apologize for the inconvenience.
  3. 1 point
    Customer: Ma'mmon Ismail He cannot find the projection in GMS for his data. Here is the coordinate system information: Projected Coordinate System: Palestine_1923_Palestine_Belt Projection: Transverse_Mercator False_Easting: 170251.55500000 False_Northing: 1126867.90900000 Central_Meridian: 35.21208056 Scale_Factor: 1.00000000 Latitude_Of_Origin: 31.73409694 Linear Unit: Meter Geographic Coordinate System: GCS_Palestine_1923 Datum: D_Palestine_1923 Prime Meridian: Greenwich Angular Unit: Degree More info can be found here: http://spatialreference.org/ref/epsg/28192/
  4. 1 point
    Dear Colleagues: This is only a help for the case you get problems when installaing SMS. I have just moved to Windows 7 ultimate, and SMS could not be installed. I got a message "Error 1935.An error occurred during the installation of assembly - HRESULT: 0x80070020". I haved spent some 5 or 6 hours looking for a solution, since I am in a hurry, trying to finish a modelling. Well, after finding several possible solutions and buying a couple of cleaners, the way to fix the problem was very, very simple: - The main problem is the size limit of the registry - The solution: -- Open the registry (regedit) -- Go to HKEY_LOCAL_MACHINE ---------System ---------CurrentControlSet ---------Control ------------ Key: RegistrySizeLimit, type REG_DWORD ------------ Change the size to FFFFFFFF -- Close and reinitiate Cheers, Jose
  5. 1 point
    In the Stress Periods dialogue box you have the option of checking a "Steady State" box for each stress period. What impact does this option have on the model?
  6. 1 point
    Remove the "MODFLOW is steady state and one or more of the coverages are transient” warning that appears when trying to save a MODFLOW simulation with transient data in the map module while the MODFLOW simulation is steady state. (requested by a user who says that it gets on their nerves while working with transient models. They said that the warning will always come up since that will always be the case – steady state and transient coverages.)
  7. 1 point
    Is there a way to vertical hydraulic conductivity values using fixed head differences between two boreholes at the same Horizontal location? For example, if I drill two boreholes just a few feet apart but at different depths there is a good chance that the heads could be different. I want to calibrate my vertical hydraulic conductivity so that there is a few feet head difference between the boreholes. Any suggestions for how to proceed?
  8. 1 point
    Is there a way in SMS 10 or 11 to save a default display option? On one of my computers some options are selected to display by default (nodes, element, boundary, etc.) and on my other machine only elements are displayed by default. I am hoping I can select and save out what I want SMS to display by default when I open the program. This may save a few minutes so I do not have to set my usual display options every launch of SMS.
  9. 1 point
    Great! this solves the model checker error message. I made a simplified version of the femwater model and compared it to a modflow one. - brief one layer two bc - constant head (h=2 and h=0 sea level) top and bottom elevation derived from boreholes data (scatter data) refined elemnts I attached the following screen capture show computed head contouring: 4-1 = modflow with 1 layer grid (top and bottom elevation interpolated), plus obs wells, everything seems ok 4-2 = modflow with grid (mean values for top and bottom elevation), plus obs wells, everything seems ok 4-3 = femwater with 1 layer grid (top and bottom elevation interpolated), plus obs wells. The 4-3 model show the total head that is the same as head in modflow. Is it correct? Why the contouring 4-3 is so different? I run the model with different starting heads and the computed heads depends from the initial condition. I coudn't get the obs wells (in conceptual model - obs point) to have the computed head value. I tried to fix their z elevation to match the 3d grid elevation but without success. Thanks dlattuada
  10. 1 point
    Can you Please Email me at Support@aquaveo.com and I send some Trouble shooting steps. We would love to get this working for you.
  11. 1 point
    I was able to run the MODFLOW SFR2 tutorial model. I would recommend going through the MODFLOW-SFR2Package.pdf tutorial located in C:\Program Files\GMS 7.0\tutfiles\MODFLOW. There it explains how to set up a model using the SFR2 package. You can also see a finished model that uses the SFR2 package in C:\Program Files\GMS 7.0\tutfiles\MODFLOW\trans\sample. If you need to download the tutorials, you can find them here.
  12. 1 point
    The option to specify if the polygon is land or ocean was removed recently because it is not really needed. The tutorial should be updated in the next version of SMS. You can just skip over that step in the current tutorial.
  13. 1 point
    SMS reads values larger than 360 degrees however these values correspond to a value between 0 and 360 degrees (ie. 540 degrees = 180 degrees) so there is no need to enter in any values greater than 360. The degree is measured from the positive x-axis counterclockwise. This makes straight up 90 degrees (or 450 or 810, etc) You may check what units RMA2 is looking for by opening the .bc file and checking the BWC Card. The second value is the IWMX flag and as stated in the manual this value corresponds to the units: 0 = miles/hour 1 = meters/second I believe by default this value is set to 1 meaning the winds would be entered in m/s but can be changed to 0 for mph if desired. The .bc file generated by SMS can be opened in a text editor like notepad.
  14. 1 point
    Sorry for the slow response. Here is a version that is compiled for 10000 stress periods. ftp://pubftp.aquaveo.com/download/temp/mf2k_h5.zip
  15. 1 point
    Joel et al, This problem has been resolved in the latest version of SMS 10.1.
  16. 1 point
    I am using the method discussed in Tutorial Vol 2, Chapter 6, "GENERATING MODFLOW DATA FROM SOLIDS". I talked to ERDC yesterday and sent them my file. They were not able to create a grid from the solid model in GMS 6.5. However, they created the 3-D grid from the solid model using GMS 7.0. I am not running 7.0; I'm running 6.5. I don't really understand why this is. The tutorial file associated with Vol 2, Ch 6. runs in GMS 6.5. It will take me a few days to get 7.0 loaded on my PC.
  17. 1 point
    You may find the following post helpful: http://aquaveo.invisionzone.com/index.php?showtopic=379 See the PDF posted towards the bottom.
  18. 1 point
    If you are having problems getting your FESWMS model to run, you may want to consider trying the following: Transform your mesh so it is close to the origin (0,0). For some reason if the x and y coordinates are large and mesh element sizes are small, FESWMS can have problems. Try using the Steering Tool Make sure your mesh does not have incorrect elevation values (often due to extrapolation). Try looking at the mesh in a rotated view. Verify that wetting / drying is turned on in the FESWMS model control Is the problem a known issue with the version of FESWMS you are using? Keywords: ds=0, ds = 0, convergence, error
  19. 1 point
    Hi, I am using TUFLOW in SMS 10.1 and I would like to link a fine Grid in some areas to a coarser Grid. We already ordered the multiple domains license. When I try to link the two 2D domains according to the help file on http://www.xmswiki.com/xms/SMS:TUFLOW_Linking_2D_Domains as below To setup multiple 2D domains in SMS: 1. Create multiple TUFLOW grids and associated grid components. 2. Define a 2D/2D Linkage coverage and attributes (see below). 3. Add all the 2D domains being used and the 2D/2D Links Coverage to the simulation. the program always tells me, that "this component already has a grid linked to it!". So what can I do to get this thing done? I already posted my question in the TUFLOW forum and they gave me a Tutorial. Unfortunately the multiple domains tutorial is not yet documented and so it is not easy to understand, how to use this tool. Kind regards
  20. 1 point
    When you open a GMS:FEMWATER project, GMS does not read in the print times.
  21. 1 point
    1. Variable flux bcs in steady state model: I think what FEMWATER is doing is figuring out whether flux is inward or outward at each node. It could be outward if the water table comes near the surface so that net flux is outward. For some reason it (perversely) initially assumes it is outward everywhere. 2. Slow convergence: I found the cause behind my slow convergence was poor resolution in the van Genuchten curves. GMS produces curves that have poor resolution at the dry end of the curve. If you have the FEMWATER spline interpolation switched on, this can then produce curves that are non-monotonic I think, which screws up convergence. It worked better for me when I dramatically increased the number of points in the VG curves to 500 (I had increase MXSPMK and recompile FW to do this). Also note that the GMS preset VG curves are incorrect if your length scale is not centimetres. 3. Minimum pressure head: I think the only purpose of this parameter is to truncate the pressure head at the surface to limit how dry it can get, to avoid running off the end of the VG curves for instance. I am assuming this is only applied at the variable flux bc nodes but I am not sure.
  22. 1 point
    Hi I am applying FEMWATER at a small field research site (80m x 40m, 20m deep), and having problems with flow convergance and boundary conditions. The domain is roughly rectangular (slightly converging) and slopes downhill. I have set constant head bcs at the top and bottom boundaries (according to measured well levels) and no-flow on the side boundaries (assumed to follow streamlines). There is constant recharge on top, and no flow on the bottom. At the moment I am looking for a steady-state flow solution. I've attached a plot of a moisture content solution (which didn't converge properly). Firstly, convergance problems seem to arise near the water table due to the sharpness of the van Genuchten release curves for the soil (ignumbrite, which I have approximated as a loamy sand). The linear iteration converges fast enough when I use the PGCM (Choleski preconditioner) option but the non-linear (Picard) iteration is painfully slow. Could this be due to my spatial scale being too coarse? I was wondering what grid resolution I am likely to need to get a fast, stable, correct result. Currently my (unstructured mesh) elements are about 4.0 m horizontally and 0.2 m vertically. Are there any general guidelines for grid resolution that I should be aware of? I have read a little about numerical dispersion re Peclet and Courant numbers, but what about for unsaturated flow solutions? Secondly, I am seeing some strange artifacts near the boundaries. The unsaturated nodes directly under the specified head boundaries (top and bottom) are much drier than their neighbours, giving a large horizontal gradient in the unsat zone near the boundaries. It doesn't look right. It's almost like no recharge is being applied at the boundary. Has anyone seen this kind of thing before and know what to do about it? Thanks in advance for your suggestions.
  23. 1 point
    We've posted a new update. Please let us know if you continue to have problems. Thank you, John
  24. 1 point
    Doesn't work for me too.... looking forward for the next update. thanks greetz Chris
  25. 1 point
    John, Please let me know when the new version is ready. Thanks, Chris
  26. 1 point
    John, The BOUSS-2D model executable for SMS 10.1 is not currently working. We are working with the model developer to find a solution. This is a problem with the model and not SMS. You can either work in SMS 10.0 or use the BOUSS-2D model executable from SMS 10.0 with SMS 10.1. http://xmswiki.com/xms/SMS:Bugfixes_SMS_10.1
  27. 1 point
    I found if you work on a GMS:FEMWATER project for some time, changing bcs and materials, GMS does not throw out the old XY1 series (mostly boundary condition values and unsaturated material properties). So you get a 3bc file with many XY1 series, many of them redundant, and particularly the ids of those series start to get large. When the XY1 id values exceed 250 FEMWATER reports an array bound error. It would be good if there was some way in GMS to renumber the XY1 series and throw out the old ones. PS: I managed to do a workaround by deleting the 3bc file then restarting GMS. I may have deleted the materials and Simulation too (I don't remember). So I had to reenter the material properties and simulation options, but GMS did regenerate the 3bc file without all the old XY1 series/series numbers.
  28. 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.
  29. 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.
  30. 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.
  31. 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
  32. 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.
  33. 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)
  34. 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.
  35. 1 point
    Rusty, How do I recover the autosaved files? Chris
  36. 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.
  37. 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.
  38. 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
  39. 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
  40. 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?
  41. 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
  42. 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
  43. 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.
  44. 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)
  45. 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.
  46. 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.
  47. 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
  48. 1 point
    Joel, The PTM model executable has been updated recently, with fixes to several problems. The models can be downloaded here. Thanks, John
  49. 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.
  50. 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.