All Activity

This stream auto-updates   

  1. Earlier
  2. If it is the case, that there is a bug in gms, so that it does not perform the final model run with the best parameter values stored in the case.bpa you would probably have to move the entire analysis out of GMS. I would suggest you to look at There you will find some guidelines on how to formulate the problem for the NSMC analysis to get the desired results. The usage of parrep utility is prety simple, it is command line utility, so since it is in your environment PATH variable you can run it from CMD: parrep parfile.bpa case_orig.pst case_new.pst The common framework for any NSMC analysis would be to manualy generate random parameter sets with the randpar utility then to project these sets into the solution space using pnulpar. Then runing PEST for each projected parameter set with 1 or 2 optimisation iteration to account for model nonlinearities and colect the best parameter values (.bpa files). Finaly you may run the model with these parameter sets to collect the predictions of interest.
  3. I have a model that was created in Vistas which I'm attempting to convert over to GMS. Note that the original model did not include nested grids, so the node number should be the cell number. Anyways, I have the grid set up and was able to get the recharge in. However, the source/sink files (drn, riv, str, etc.) use nodes. I attempted to drop the information into the MODFLOW files, but I get the error that it wants to look to the HDF5 file for the data. How can I get around that? I put in a test drain, saved the file (the data apparently went to the h5 file)....but when I tried to comment out the reference to the h5 file and attempted to add/read in a couple more drains in the MODFLOW file, the model still pulled in the data from the h5 file. I thought that was a bit odd. Anyways, I have all of these node-based points which I should be able to read in, but can't figure out the best way to do it. Any thoughts?
  4. Hi Jonas. I’ve experienced similar unusual responses when using PEST within GMS, with and without SVD and SVD Assist. Sometimes PEST will reduce my error nicely; other times it gets nowhere. Yet, when it goes nowhere I can manually adjust parameters myself and reduce the error. I’m not sure of the reasons, but it may be related to GMS and it writing the MODFLOW files from pilot points. I’ve had particular problems using kriging interpolation, so much so that I have now switched to IDW interpolation. While I now have less problems, I still experience unusual PEST behaviour. It’s a problem I’ve experience on and off for several years now. I’d be interested to see if others have had any similar problems. My models are with Aquaveo support, but the problem can’t be consistently repeated, so it is difficult to fix. Have you tried importing the optimal parameters from the PEST run into another forward run? Perhaps PEST is writing the new *.par file o.k., but GMS is not updating the screen with the final result (I note GMS’ printing of the *.rec file shows a mixed up version of the actual *.rec file). Try importing the *.par file and running a forward run (saving as a new model name in case something goes weird) then see how the new result looks. Regards, Julian
  5. Hi Tertia, I am not aware of an option to interpolate cross sections with nodestrings. But I am confident there is a way to accomplish what you are trying to do. The most efficient way is dependent on what you currently have. It sounds like you have a scatter set surface right now and cross section data in some format. In what format do you have your cross section data? (XYZ text file, CAD file, Shapefile, etc)
  6. Hello to everybody!! I am using T-PROGS to try to simulate a complicated geological situation within a context of outwash glacial deposit, with silt clay with intercalations of sand lenses. I have some boreholes with information but in some cases distance between wells for a valid correlation are too far (ca 500m) therefore i was advised to use T-PROGS which seems to be perfect for problems of horizontal correlation. main groundwater flow from N to south (Y+ to Y-), distance along the groundwater flow between wells is from 50m to 450m, but i am having some issues: 1- while deciding the lag distances (strike(x) Markov chain) i would like to know what could be useful to put as max lag distance?? because i have no way to see if the values i am using are valid or not, only until the end of the whole flow model of mod flow 2- in the same manner while putting the lag distance of Y (dip (y) Markov chain) can anyone shed some light here PLEASE 3- besides, while creating the grid and the successive T-PROGS for the unconfined aquifers i want to have different materials within the same layer is this possible with the HUF, to avoid dry cells. THANKS A LOT IN ADVANCE FOR YOUR COOPERATION AND REPLIES ALEXANDER
  7. This error comes up if WMS does not have the location of your cross section database or if there are no cross sections or an error reading the database. I'd recommend double-clicking on your cross sections and making sure cross sections geometry is defined for each of your cross section arcs. If there's an arc without any cross section geometry defined or if there's an error loading the cross section database, that's your problem. You might have to re-extract all the cross sections to a new cross section database if some of the cross sections do not have geometry. Hope this helps, Chris
  8. Thanks for your quick reply Michal, I agree on that it seems like PEST is doing its job but GMS does not read in the result properly. But I can't find the reason for this since the same modelling procedure has worked for other models. Quite frustrating. How do use the PARREP utility? Should I use it outside of GMS interface? Kind regards, Jonas
  9. Hello Jonas, from my humble opinion it looks like PEST is doing its job well. It decreases Phi to 63.5% and finish optimisation after one iteration since NOPTMAX is set to 1.Which is probably correct if you try to do NSMC analysis. The reason it does not load solution into GMS may be a GMS glitch. What I think is happening, when PEST is run using svd-assisted inversion it does not carry the final model run using the best parameter values. As is described in the manual to PEST, it is encouraged for the user to do it him/herself using the PARREP utility and setting NOPTMAX to 0 in the PEST control file. So I am guesing that GMS does not do this for you. It would be best if someone from the GMS devs looked into it. Kind Regards Michal
  10. I extracted my drawn-in cross sections from the TIN to create a new cross section database (in prep for HEC RAS). When saving and exiting my .wms file, I was given the following error message (image below). Should I be concerned with this, and if so, how do I address it? Why did this occur? Thank you.
  11. This is what typically happens when running with SVD-assist. As can be seen from the blue marked line, PEST is able to reduce the error to 98.885 from the initial error of 155.76. But, then something goes wrong since this solution never comes up as a iteration before the parameter estimation is finished.
  12. I often experience problems when running a PEST parameter estimation model with SVD-assist. I find it quite arbitrary when it work and when it does not work. For some occasions it seems to work just by moving the modelling files to another computer and run the model on that workstation. For my current model, SVD works but SVD-assist does not. To reach reasonable results with NSMC is even more problematic, in particular for transient models. I run the latest nightly build and NWT as solver. Someone with similar experiences or suggestions to a more streamlined and stable model procedure?
  13. Dear all, I am a recent user of GMS-MODFLOW and one question came into my mind. For the purpose that I am using the software, in most cases the groundwater height in (meters above sea level) is not relevant. It is more important to know the groundwater depth below surface. Is there an option to calculate and visualize this with GMS-MODFLOW? Thanks in advance for the responses.
  14. Why does SMS use both Arc IDs and Arc Names? When you are plotting observation lines you have to know the "Arc Name", but you only have the option of displaying "Arc ID" in the Display Options window. This can lead to confusion when Arc IDs and Names get out of sync when merging coverages. In my current project I have Arc ID 1 through Arc ID 703 and Arc Name 710 through Arc Name 1412. If someone could highlight the advantage of having two ways to reference the same arc, that would be great. Or perhaps the Display Options could be updated to include the Arc Name. Thanks!
  15. Yes, there is an option for Hydrograph output that will show up as the 3rd column in the point/node attributes window if you have defined your 1D Hydraulic Model channels (trapezoidal or cross sections) on arcs in the map module and define the Diffusive Wave routing option in the GSSHA Job Control dialog. Turn this option on to generate hydrographs at any point in your 1D stream network. Chris
  16. Hello, My project has two large drainage basins that were delineated by creating two outlet points. However, after running the simple GSSHA model, only one hydrograph and summary data is created. Is it possible to generate hydrographs for both outlets as well as at other nodes in the model? Thank you in advance!
  17. By any chance is there a Linux-compiled version of the MODFLOW-NWT_h5_64 executable available? I wanted to use a cloud environment to calibrate a GMS created model but the cloud operating system is Linux.
  18. Gina, If you can get your materials file from SRH2D into a WMS "Area Property" coverage, WMS will get the Manning's roughness values from this coverage when you extract the geometry for your cross sections. To extract the geometry for your cross sections, you need a 1D Hydraulic Centerline and a 1D Hydraulic Cross Section coverage in WMS. In the centerline coverage, you would define your stream centerlines and your bank lines (bank lines are optional, but recommended). In the cross section coverage, you define your cross section locations. I think you're saying you've already created these coverages or layers in Civil 3D and you don't want to create them again. If you have your HEC-RAS geometry file, you can export a GIS Export file from HEC-RAS and read this file into WMS. The 1D Centerline and Cross Section coverages will be created if you do this, but you will need to re-extract the cross sections (including the geometry) to assign Manning's roughness values in your Area property coverage to your cross sections. Here are the steps for doing this: 1. In the HEC-RAS main window, select File | Export GIS Data... 2. Turn on the options to export your User Defined Cross Sections and your Bank Stations and select Export Data. 3. In WMS, open the .sdf file as a HEC-RAS .geo file. Just select File | Open and select HEC-RAS GEO file from the window that comes up and select OK. 4. Enter a filename for the cross section database file. The default filename is probably OK. 5. Go to your 1D cross section coverage and select River Tools | Cross Sections->TIN. 6. Bring in your Manning's roughness areas as an area property coverage. Make sure you have polygons in this covearge, make sure you have defined Materials (Edit | Materials), and make sure you have a material assigned to each polygon in the coverage. 7. Now go to your 1D cross section coverage and select River Tools | Extract Cross Section... 8. Generate your point properties from the arcs in the Centerline coverage and Generate your line properties from your Area Property coverage and select OK. 9. Now go to the Hydraulic Modeling Module, HEC-RAS menu and define your Manning's roughness values under the Material properties for each material type. You also want to set your model control to use the Materials (under the HEC-RAS menu, there's a Model Control menu item for doing this). Hope this helps, Chris
  19. This functionality of this package will be available in MODFLOW 6. A new version of MODFLOW that will become the "new" main version of MODFLOW (like MODFLOW 2005). It has not been formally released yet but should be available in the fall of 2017.
  20. Hello, I have a model in HEC-Ras version 5.0.3 that I set-up in Civil 3D 2017 (stream alignment, cross sections, LOB, ROB) and I was asked to add in the Manning roughness values from SRH2D. I was asked to do this because I was told that the .geo file from WMS brings in all of the n-values along the cross section, creating a more real-world HEC-Ras model. Currently, I have only 3 n-values. I found a forum that displayed how to correctly transfer the materials file from SRH2D to WMS, and then create essentially the geometry file in WMS to export to HEC-Ras, but I already did most of this in Civil 3D. I don't want to re-do my .geo file in HEC-Ras because it is basically complete. Is there a way to import only the n-values from SRH2D without re-doing my entire HEC-Ras model created from Civil 3D? Thank you
  21. Hi, I'm writing to ask if there is such a function in GMS stochastical modeling that can stochastically randomize the distribution of parameters within the aquifer. I know in GMS, we can randomize the value of different parameters (for example, to randomize the hydraulic conductivity K by defining the sampling range to produce several realizations). But I want to ask if it's possible to generate a stochastically distributed aquifer with one or two parameters being stochastically distributed within the aquifer (for example, K is stochastically distributed within the aquifer by following lognormal distribution, therefore, the aquifer is with different K values at different location, rather than the different constant value for different realizations). I think this may represent the natural heterogeneous aquifer better. I know in HYDRUS 3D, it is possible to construct such an aquifer, but MODPATH is not supported in HYDRUS, therefore, I want to ask if it's possible to do it in GMS. Thanks so much for your attention and any comments are welcome! Yue
  22. Hey, thanx for replying! sorry for being unspecific. It is like you said, the tracer concentration is always zero. I have checked all the potential problems that you mentioned but still, the problem is there. I attached a picture of the model, if maybe that helps someone with an idea... Thanx again!!
  23. Hi, There is a way to re-extract and update only selected cross sections but it's not an easy procedure and would require you to edit some of the WMS .map and cross section database files using a text editor. I guess I don't really recommend this approach. I guess you have a couple of options. One is the approach you mention, where you extend any cross sections that don't intersect the bank lines so they're beyond the bank lines. This would require you to re-extract all your cross sections, and your edits based on survey data would be deleted. You would need to re-enter your survey data for each of your cross sections in this case. This should not be too difficult since you should already have the survey data saved as a cross section database file. It would just be time-consuming, especially if you have lots of cross sections. Another approach is to edit each cross section's geometry and point properties by going to the cross section attributes | Assign Cross Section | Edit and then adding the left and right bank stations manually into the Point Props window. The drawback of this method is that your left and right overbank lengths will not be computed by WMS for the cross sections where the left and right banks are manually defined. When you run HEC-RAS, you will get an error message for each of these cross sections. You can then compute the left and right overbank lengths for these cross sections using the measure tool in WMS. You would have to re-enter these lengths in HEC-RAS each time you export your model from WMS. So it may be worth it to you to update your cross section arcs in WMS, re-extract the cross sections, and re-merge your surveyed cross sections, but that's up to you. I agree that it would be nice to just update selected cross sections in your cross section database file, but this option is not yet available in WMS. Hope this helps, Chris
  24. I created a HEC-RAS network schematic, and was in the initial stages of running HEC-RAS when a series of errors occurred. These errors stemmed from the fact that some of my cross sections did not intercept the left overbank (LOB) and / or right overbank (ROB) lines (middle image). Compare to the top image, where the cross section intercepts both LOB and ROB. I did not realize this was critical when creating the cross sections in WMS. Extending the cross sections beyond the LOB / ROB would seem to solve the problem. As you can see in Image 3, when the cross section does not intercept one of the bank lines, it assigns both bank stations to the zero point. My question is - is there a way to edit the cross sections (i.e., extend them) after a network schematic has been created? Since I merged all extracted cross sections with field data, I'd hate to go back and redraw all cross sections, extract again, and then merge again. I attempted to draw extensions onto the cross sections in WMS (create feature arc tool, then use "node-to-vertices" option to create a single line), however, this seemed to "unlink" the cross section with my merged data. So, is there a quick way to extend cross sections beyond LOB / ROB centerline coverage, to eliminate the HEC-RAS errors? Without having to redraw / extract / merge all cross sections again. Thank you!
  25. Chris, Thank you for the advice. I ended up removing points from the extracted cross section prior to merging - this worked nicely.
  26. Helo, it is hard to say without seeing the model. Could you be more specific in what do you mean by "nothing happens"? Do you mean like, the tracer concentration is zero everywhere through the simulation? First look at the mt3dms list file (case.out) and make sure, that the simulation ended without any errors. Then I would suggest to look at Output control in the basic transport package and make sure it is set properly, so MT3d is writing the concentration binary arrays at correct times. Also try to look at the model cell containing the injection well via sources/sinks dialog and check, that there is associated concentration with it.
  1. Load more activity