Jump to content
GMS, SMS, and WMS User Forum

Michal

Members
  • Content count

    44
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Michal

  • Rank
    Senior Member

Profile Information

  • Location
    Czech Republic

Recent Profile Visitors

913 profile views
  1. Hi, I would like to see a functionality in GMS, that would make working with pumping data more easy. Let me make an example to explain what I mean. Consider we would like to import pumping schedule for a single well into a transient model with three periods with a length of 30 days each. The well Q for first period was -100, for second the well was off and for third it was -200. The pumping schedule extracted from a database has this format: well_name time Q well1 1 -100 well1 61 -200 I would like GMS to ask me during import, how do I want to treat the stress periods without any pumping data, in this case the second period. I would like to have an option to choose, that when there are no data for a given period GMS would add 0 for that period automaticaly, e. g. the well is off for that period. This would be realy useful, because otherwise one easily forgets to add the zeroes manualy and ends up with incorrect schedule.
  2. SFR2 not working with MODFLOW 2005

    Hi Niklas, I have encountered similar problem with MODFLOW-NWT. After an update MF-NWT started to report head below cell bottom error and a model that run ok with previous version was terminated due to this. I solved it by increasing the head slightly as it was only a very small difference. My point is that MF developers added a check module that was not in the old version and you are probably strugling with something similar. MF2K5 being smarter in finding the errors then MF2K (or the SFR2 module). As the best option of fixing the errors is not feasible, you could try looking into MF2K5 change log and maybe try to use older version of MF2K5 that may not contain the check. Or you could disable the check module in the SFR2 source code and recompile MF2K5 yourself. It is a matter of compiling MF2K5 with ICHKSTRBOT_MODULE located in gwf2sfr7.f modified accordingly. Just be aware that you may get incorrect solution as the check has its purpose.
  3. Remove Drains from Exported Transient Observations?

    Hi Carrie, you can uncheck the Enable saving of computed flows for all source/sink objects in the Output control.
  4. Problem with Null-space Monte Carlo

    Hi speedy, I have also struggled with krigging setting not saved properly. But this was solved in GMS 10.3.4. I have recently succesfuly solved inverse problem with Aquaveo MODFLOW model using PEST. There was pp kriging set up for several parameters. Although it worked ok for me , I would still prefer GMS to use native PEST tools for pp interpolation and PEST structure files for storing interpolation setting as it would allow us to use native USGS modflow for calibration with pilot points very easily. Anyway, thank you for sharing your experience on the forum. It is always very helpful. Best Michal
  5. MT3DMS THKSAT error

    Hi, mt3d is trying to read the saturated thickness array from the flow-transport link file (.hff) on unit 10. I suggest you to check that the .hff file is written correctly by modflow. It must be allowed in the GMS output control dialog.
  6. Determing boundary condition

    Hi, I think the flow could be calculated as a difference between the head in the model cell and corresponding head at the boundary. Conductance is the proportionality constant. Therefore Q = C (h1 - h2). If you know the head at the boundary (in the neighboring aquifer) and in the model cell, conductance could be easily calculated from the above formula for each model cell and the flow through the boundary would be as specified for each cell.
  7. Transient spatially distributed recharge

    Thank you for sharing the solution. Nice one Have you used some sort of interpolation to obtain modflow compatible dataset from the raster data? Or is the grid and rasters identical in number of rows and columns?
  8. Hi, try preparing the transient dataset so, that for each polygon in GMS coverage, there is a corresponding timeserie with the polygon id assigned at each row of the dataset. It will be a large dataset, but GMS should handle it unless you run out of memory.
  9. I agree with Hisham on this. There is no such concept as multipart polygon in GMS, as far as I know.
  10. Hello, this is interesting. Maybe there are 553 multipart polygons in the shapefile and when converting to feature object GMS performs multipart -> singlepart conversion. http://desktop.arcgis.com/en/arcmap/10.3/tools/data-management-toolbox/multipart-to-singlepart.htm
  11. PEST Observation Groups

    Hi Bruce, that would be very nice GMS feature. It could be even so, that head observations for different coverages would fall into different observation groups in the PEST control file. Also parameter grouping with custom naming would make thinks a lot easier. I can imagine, you could specify PEST parameter group in the Parameter dialog for each entry.
  12. Transient spatially distributed recharge

    Hi, I think it could be possible by interpolating transient TIN data (or maybe even rasters) into Recharge package using Interpolate to Modflow layers command. But I have not done it before. Let us know how you manage to handle it.
  13. Modflow 2000-transient model result

    Helo, try using MODFLOW-NWT instead of MODFLOW-2000. Its excelent in handling problems with cell drying/rewetting. In the LPF package set all layers to convertible. If insist on using MF-2000, maybe try different timestepping scheme to avoid overshoots.
  14. 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.
  15. 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.
×