Jump to content
GMS, SMS, and WMS User Forum

All Activity

This stream auto-updates     

  1. Last week
  2. Importing Mesh into HEC-RAS

    Try going to the "Data" menu and choose "Switch Current Model...". From the options in the "Select Current model" you should choose "Generic Mesh" for HEC-RAS meshes. After selecting this you should be able to link the mesh to the simulation. Let us know if that does not help. -Cody
  3. Importing Mesh into HEC-RAS

    Hello, I am working with SMS Version 12.2 and try to import my created mesh into HEC-RAS. I already read the providet tutorial and everything workt out fine. But when i try the same with my own mesh I am not able to link the mesh with the HEC-RAS simulation ( Step 3.4 in the Tutorial). It used to be an easy step but I can´t find a solution for this problem. Any suggestions?
  4. Well screens

    Thank you Lalith for the reply You just confirm what i was thinking before. It seems that my GMS as a software bug or glitch
  5. Well screens

    I use both of these options all the time. I have had no issue. If you do not specify the screen, extraction would be taken place from the layer ranges specified. If you specify the screen levels, it would be taken from the cells that intersect within the screen levels.
  6. If you have refinement on, please check your "bias". reduce that number. you can get rid of them. However that might results in a higher resolution grid, which might lead to higher computational times
  7. Well screens

    Hi all, Using the option "use screen" for "wells" in sources/sinks, am I telling the model that the water extraction is only carried out in this interval? When I turn on this option GMS transforms my extraction wells in injection wells!! Why is that? Is it a software problem? Best regards Filipe Miguéns
  8. Observation points using MODFLOW USG

    Hello everyone, Can someone tell me if there's a limited number of observation points using MODFLOW USG? I have 77 observation points for my model, but when I create the files in GMS it considers only 7 of them! I started my model from scratch using MODFLOW-USG, so I cannot import the 3D Grid files as exemplified in the tutorial. Another thing that occurs in my model after running it, is that the observation targets don't show the same value as the generated head surface?! Can you help me? Best regards Filipe Miguéns
  9. Cell dimension change more than 50% in .............

    Note that it is just a warning and not an error. The model will still run. Typically, it is preferred to have cell sizes transition from smaller to larger without too big of a jump. Better for numerical calculations. This warning is probably due to your layer thicknesses being more than 50% different....and is not unusual, especially when dealing with lower layers in a model.
  10. Dear all, can you paste some references on how to use SEAWAT in GMS. Thanx in advance
  11. Dear colleges can any one tell me what is the wrong with this message and how to solve it please Cell dimension change .......... THANX IN ADVANCE
  12. Missing Case.dat Error

    Cody, Thanks for the quick reply. I was in fact getting the error message below in the SRH-Pre run and was able to resolve using the wiki page. Thanks again or your help.
  13. Missing Case.dat Error

    This error usually indicates that something went wrong when SRH-Pre ran. If SRH-Pre runs into an error, the simulation *.dat file is not created and when SRH-2D tries to run, it will report that it cannot find the file (the error shown in your screenshot). There is usually a more descriptive error in the SRH-Pre model wrapper window. Have a look at the SRH-Pre error and refer to the SRH-2D error wiki page for a description and resolution. If that page is not much help for the error you see, please post the error you are seeing along with any information about your model that may help to identify the issue. -Cody
  14. Missing Case.dat Error

    Hello, I am working in Version 12.2.11 of SMS and am running into the following error when I try to run the created simulation in SRH2D. Does anyone know of a fix for this error?
  15. Event is over due to flow below cutoff value

    Thank you Calberts for answering my question. You helped me a lot. I was a little confused with the shortcut of the Unit of Discharge in Cubic meter per second “CMS”. I am used to the abbreviation m3/s.
  16. Event is over due to flow below cutoff value

    There is an input in the GSSHA long term simulation options called "Minimum event discharge". I believe this message shows up when you have specified something other than the default of "0". It is a way to tell GSSHA to end the event and move on if the discharge falls below the flow specifed. You can read more about this in the following wiki page: http://www.gsshawiki.com/Long-term_Simulations:Global_parameters -Calberts
  17. Earlier
  18. Hello, Does anyone know the cause or the meaning of this message” Event … is over due to flow below cutoff value” which appears in WMS Model Wrapper?
  19. MT3DMS

    Hi, I am working on a MODFLOW and MT3DMS simulation set up. I have some constituent observations at different locations. I would like to create a 3D constituent plume using these observed data and use that 3D plume as the initial condition for MT3DMS model simulation. I am able to make the 3D constituent plume using these observed data with 3D Geostatistic methods. However, I don't know how to map this 3D plume to the MT3DSM grid as the initial condition. Would you please explain this to me? Thank you, Lalith
  20. Pre Run Error Code

    Given the broad range of changes that were made and the fact that the error message shown is not indicative of anything specific, I would recommend contacting the Aquaveo Technical Support Team and providing them with your files. They will be able to troubleshoot the issue and give some steps to resolve the error. You can contact them by emailing support@aquaveo.com. -Cody
  21. Hi, I made a model with solids and materials in GMS and then I used HUF package to define uniform model layers (cells with same thickness in Z directions). in eahc layer I have about 62500 cells (50 by 50 meter each). now I want to add salt into model and run 2 simulation one with 200 year and one with 150 years. MT3DMS run in each takes about 1.5 hour for each one. for SEAWAT I set transport time step to 365 days (one year) but it changes to one day and it takes for ever to be finished! (it does not even give me how long would it take for the model to reach the resullts!) I thought having uniform layers will help SEAWAT to be faster! And one more thing, each model is about 20 to 30 GB! is there any way to make it faster? and lighter? I wanted to run SWI for faster calculation time but it gives me an error which says HUF layers are not compatible with SWI! is there a problem with my model layers? or HUF and SWI don't work together? is it possible to run SWI with HUF? is there any way to export the HUF layer data and use it in LPF? because the input files with HUF are different. there is only one big text file with all the data for HUF and it does not have data of cells! I could not find if they are compatible or not in Moflow USGS site ( https://water.usgs.gov/ogw/modflow-lgr/MODFLOW-LGR-Guide/index.html?package_incompatibilities.htm ).
  22. The time step must be an integer divisible into 60

    Thanks Chris, I did not notice any significant change in my results when using a Time step = 300 seconds, except for a significant shortcut in the time necessary to complete the simulation. This encouraged me to try even greater values of time steps (for example 600 seconds) to see how this increase can affect the results. Nevertheless, one must be very careful when implementing this increase and must monitor all types of outputs and not focus on a specific output.
  23. Pre Run Error Code

    I recently updated my boundary coverage, boundary conditions, material coverage, monitor points and mesh. Before making adjustments my model ran, however with the adjustments I am getting the error code below. Are there ideas/suggestions about what it is trying to tell me? Or where I went wrong? forrtl: severe (157): Program Exception - access violation Image PC Routine Line Source srh_pre_3.1.exe 00007FF7301AAB8A Unknown Unknown Unknown srh_pre_3.1.exe 00007FF7301E2161 Unknown Unknown Unknown srh_pre_3.1.exe 00007FF730199E99 Unknown Unknown Unknown srh_pre_3.1.exe 00007FF73020805B Unknown Unknown Unknown srh_pre_3.1.exe 00007FF730303D7C Unknown Unknown Unknown srh_pre_3.1.exe 00007FF7302E449F Unknown Unknown Unknown KERNEL32.DLL 00007FF9F6052774 Unknown Unknown Unknown ntdll.dll 00007FF9F7D70D51 Unknown Unknown Unknown
  24. Hello, I am currently in the middle of parameter estimation process of transient MODFLOW model. The model has 21 stress periods. To obtain a good differentiability of model outputs with respect to parameter change convergence criteria had to be set quite strict in the NWT solver settings. This resulted in run time ranging form 30 to 75 minutes per run depending on the actual parameter set. Each stress period consists of a single time step. I was thinking, what the effect of different time stepping would be on the model run time? Would increasing the number of time steps per stress period make the model run faster or slower? Any experiences or advice on optimum time stepping with respect to model performance are welcome.
  25. The time step must be an integer divisible into 60

    Hi, Your comment sounds correct. If you are able to run GSSHA without errors, you can probably ignore the model checker output. Chris
  26. Export native modflow files with Pilot Points

    Yes, this is my a workflow too. There are useful utility programs in PEST to use with pilot points, like PPKREG1 and VERTREG. The native PEST approach to pilot points is necessary to use with these programs.
  27. Export native modflow files with Pilot Points

    Hi Michal -- I do all of my pest work outside of GMS. I set up the pilot points and other variables in GMS, save and run the files - up to the point where the *.PST file is written. I stop the execution in GMS and do all of the PEST work in DOS prompt windows. The *.PST file usually requires extensive edits but when I get in all back together, PEST works fine.
  1. Load more activity