Jump to content
GMS, SMS, and WMS User Forum


  • Content Count

  • Joined

  • Last visited

Everything posted by Michal

  1. Hi, well, I think this feature that is not working properly. Here is an excerpt from MT3D manual, that describes how it handles units: "The MT3DMS code uses any consistent units for input and output variables. In the input file to the Basic Transport Package, the user decides the units for time, length, and mass. Then, any input variable or constant should be entered in units consistent with the three basic units. ..." [chapter 6.2 of Zheng, Wang (1998): MT3DMS A modular three-dimensional multispecies transport model for simulation of advection, dispersion and chemical reactions of contaminants in groundwater systems (Release DoD_3.50.A).] There is more in the chapter, so please read it. You can contact technical support for GMS and point them to the problem. I would treat the units specifed in GMS as purely informative for the user. I think the value for a given property you specify goes directly into the input files of MT3D. And therefore if you specify values of a mass rate in terms of different units compared to what your input concentrations are, your outputs will most likely be wrong (and cannot simply be rescaled). Also if there is any nonlinear process involved in the simulation the units must be consistent otherwise the results will be wrong.
  2. Hi, I agree it is poorly documented. I had to dig into the source codes to figure it out. It seems to be an excess infiltration volume rejected by the model. It can be routed to other packages as described in the ModelMuse documentation: "If the applied infiltration rate is larger than the vertical hydraulic conductivity, the actual infiltration will be reduced to the vertical hydraulic conductivity. Any remaining potential infiltration will be available to the MVR package as rejected infiltration." So I guess if you lower your infiltration rate this term should approach zero. I have no idea why the text description in the budget file states "HORT+DUNN". Maybe somebody else could clarify that.
  3. Hi Bruce, it is hard to tell. I suggest you to compare the HK and Sy arrays of the HDF5 and native MF version of your model. See if they are different. They should be exactly same. You could read the HDF file directly using Python for instance, see the discussion here. Good luck Michal
  4. Here is the relationship from the manual:
  5. Hi, I think what you are trying to achieve could be done only aproximately, because you only have to assume what the head in the model will be. Anyway, for a given cell Qb = cb (hb - h), where Qb is the flow into the cell from the source cb is the conductance between external source and the cell hb is the head assigned to the external source and h is the model calculated head in the reference cell You problably have measured hb, so I would calculate cb this way: cb = Qb / (hb-h) But as I said, you can only assume what the value of h will be. Maybe calibrating the model against the measured flow could be a better practice.
  6. Hi, it is actually quite simple. Each stress period is divided into one or more time steps. The time steps within a stress period does not have to be the same length, but can increase exponentialy in length in order to capture system response to change in stress more accurately. So by specifying a multiplier f, each following step is f multiple of the previous step. So if you have stress period of lets say 10 days and you want to solve it in 3 time steps with 4.0 as multiplier, modflow would calculate the following step lengths: {0.47619, 1.90476, 7.61905} It is not so hard to figure the realtion as for timesteps 0 to n: step_length_i=(perlen*f^i)/Sum[f^i, {i, 0, n - 1}]
  7. There is a trick that could be used with MODFLOW. One could think of the Z coordinate as Y and model it as single layer model. But this is off the table for SEAWAT due to gravity vector orientation.
  8. Hi, I think you could use the conceptual model approach. You need to think of your cross section model as a normal layered aquifer model, that has only a single row. Therefore everything has to be treated layer-wise. You need to follow the MODFLOW logic, there is no special case for cross section models. And you obviously need to add Y coordinate to your elevation dataset.
  9. Hi, well the message desribes the issue. There is only one point in the scatter point dataset you interpolate from. I would double check that the scatter points do not have this error.
  10. Hi Jonathan, I was dealing with similar issue some time ago. There is not a satisfying way how to do it in GMS. The solution depends on the complexity of the task, but it involves grid level approach. You can isolate cells by material, select boundary cells by intersecting with boundary Arc (from Top view, Orto off) and adding a Sink/Source term. In some situtions it may be convenient to map BC form conceptual model to all layers and delete from grid where appropriate. This works if the boundaries do not overlap. Or you can modify the Package outside GMS with some script.
  11. Hi Rachel, The problem is probably that the concentration observation file is not generated after your model finishes. Therefore PEST complains that it cannot find it. The reasons for this could be many. I suggest you to study how model equivalent concentration observations are generated with VM. Alternatively, you could do it manualy with MOD2OBS program from PEST utility suit for instance. When not sure what to do, read PEST manual.
  12. Hi, I think that what you describe could be achieved by general head boundary. Without specifying head at the boundary modflow cannot calculate groundwater gradient between the cell and the external region. So I think the problem is unsolvable the way you try to aproach it. I suggest using GHB package. If you have no information about heads outside the model domain, you could for instace specify GHB head the same as some initial model result head and together with lower conductance the head in the boundary condition cells will vary based on pumping/injection in the model domain. For higher conductance values the boundary will resemble constant head boundary while for lower values it will act more as no flow BC. The key is to find the right value which could be achieved through parameter estimation process.
  13. Hello, I think that MTD3MS was released long before MODFLOW-NWT. MODFLOW-NWT does not change IBOUND value to 0 if cell goes dry and this is probably the cause of problems you are facing. I think MT3D-USGS has improved handling of such situation: MT3D-USGS also includes the capability to route a solute through dry cells that may occur in the Newton-Raphson formulation of MODFLOW (that is, MODFLOW-NWT).
  14. Hi, I think it is not directly posible through MODFLOW, but maybe you could create the second drawdown dataset in postprocessing using GMS data calculator. Just compute difference in head between the first timestep of the first simulation and the transient head dataset of the second sim. That should be the drawdown you are looking for.
  15. You are welcome. I suggest you to read the MT3DMS v5.3 supplemental manual here: http://gmsdocs.aquaveo.com/mt3dms_v5_supplemental.pdf There is a section about the new TOB package. If you need data for each cell of the boundary condition, then you would probably have to prepare the input files by hand and include each BC cell as a mass-flux object/group for which the budget data are going to be saved.
  16. Hi Lalith, In the MT3D output file, there is cumulative mass budget associated with each BC type already listed. If you need more control then there is TOB package for MT3D. https://www.xmswiki.com/wiki/GMS:Transport_Observation_Package
  17. Michal

    Flow Budget

    Hi bokuhata, I assume you have maped a general head boundary (GHB) at the coastline. When you select an arc representing this boundary you see, in the tooltip area of GMS, a flow across this boundary to/from an external reservoir. On the other hand, the Zone flow in Zonebudget is the flow between the two zones in the model. From this you see it has to be different.
  18. Michal


    Hi Aly, I think there is no straight forward way to do this in GMS. I would suggest the following procedure: 1. Create the profile as a regular 3d grid with high enough resolution to carry the material information (1 row, many columns, many layers) 2. Export your grid into a text file with the following format: Cell_id X Y Z Y coordinate should be constant for all cells. 3. Swap Y<->Z 4. Import into GIS 5. Digitize the material polygons in GIS in X-Y space 6. Select the cell centers according to the material polygon and asign material ID into a new column in the atribute table (spatial join) 7. Export the atribute table into a text file 8. Copy the material column into a new file and format the new file as GMS 3d dataset format (see GMS wiki for details) 9. Import the new material dataset to the existing 3d grid 10. Select cells in GMS according to the material dataset and specify material properties as you like
  19. Yes, but if the model is steady, than the best approach is to set the initial heads high, because during the consecutive aproximation of the solution the chance of making cell inactive as a result of undershoot is lower. It can happen anyway, but in your case it looks fine. Btw. I think the cells never get rewetted because they are initialy dry.
  20. This result looks good to me. There seems to be no more flooded cells. What about the budget? The wetting capability is turned on in the LPF or BCF package. I usually use the default values first unless there is a problem with convergence.
  21. Hi, what about the dry cells in the above picture? Couldn't it be the explanation for what you observe? This could cause reduction in aquifer thickness and reduction of volumetric flow rate therefore. Is rewetting on?
  22. I would say that MF-USG is very different in terms of how the solution to the flow equation is aproached compared to the traditional structured modflow. However it is usually not too difficult to set up a MF-USG simulation in GMS. There are some tutorials out there that could help. I would recommend reading the MF-USG manual as well to grasp the internal differences. Regarding your second question. I believe there are other people here that could provide more accurate answer. The problem comes from the way MODFLOW solves the groundwater flow equation, that is by numerical approximation. During these approximations (in MF-2005) if head in a cell falls bellow the cell bottom the cell is assumed dry and is inactivated (becomes no-flow cell). However in subsequent approximation the cell could become wet and active again if certain criteria are met. For instace if head in the cell below (i,j,k-1) is 0.1 m above the cell (ijk) bottom. The 0.1 m would be the user specified threshold for conversion from dry to wet. This whole process brings instability into the solution and may cause convergence problems especialy if poor initial head values and low threshold values are specified. However MF-NWT adressed this issue in a brilliant way. It does not deactivate dry cells, but instead it uses upstream weighting approach to limit flow from dry cell to a neighboring partialy saturated cell. It also uses additional smoothing for conductance and storage functions which allows the use of newton numerical method for outer iterations. It therefore provides a continuous solution for all unconfined groundwater flow conditions and is very robust. However if you have steep aquifer your problem is different. Consider two neighboring cells of 10 m thickness. Lets say, under extremely steep conditions they share only 1 m thickness. However structured modflow will assume 10 m anyway and would not modify transmissivity accordingly. Such a solution would be incorrect. That is why I recommend using MF-USG in your case as mentioned earlier in my previous post. For literature I suggest reading the manuals published by USGS for modflow 2000, 2005, NWT and USG. There are plenty of further references there too.
  23. Hi, MODFLOW assumes flat continuous aquifer. You could probably overcome the drying/wetting problem by using Newton linearization implemented in MODFLOW-NWT. However, if there are large not negligible differences in elevation between two horizontaly adjacent cells MODFLOW results will be incorrect. Fortunately the finite volume formulation in MODFLOW-USG adressed this issue - it involves true interface area into the calculation. If I remember it right, this is supplied for each cell connection in the DISU file somewhere. If you use GMS, this should be done automaticaly for you. You could use the upstream weighting (LPF package) and newton linearization (SMS package) for a more robust solution. With this setup the model should converge to a correct solution.
  25. Ok, I see your dilemma, since the model was already calibrated. Try loading the .nam file via Read Solution command. It should have the same format as .mfn and it should load the binary output data referenced there. You could also try to run the model with the MF executable that worked through GMS via custom Run dialog.
  • Create New...