• Re: in-/active option

    It seems that the phreatic surface in your model is being simulated with the 'free&movable' option. In this case, element deactivatoin is not supported. You'll have to either use the 'Phreatic' mode or a fully unsaturated model in order to use inactive elements.
  • Re: Import elevation data in .asc

    Hi Boris,

    FEFLOW does not allow to load ESRI ASCII grids directly. I recommend to export the mesh nodes as shp, attach the values from the .asc grid to the points in a GIS system, and import the elevations back to FEFLOW. Alternatively, you can convert the .asc grid to points and use these for interpolation in FEFLOW. The latter option, however, will give you a very large point file that is not required with the former one.
  • Re: multilayer Well

    Here's what I do to avoid selecting slice edges as well: I use selection of join edges, and then convert them to edges after selection via the context menu of the current join edge selection. Same the other way round for seleting edges in a slice only.

    I guess I should add [22 May 2017] that in FEFLOW 7.1 there's a selector for selecting both slice and join edges, or only one of the types when selecting edges. You find the switch on top of the current view window.
  • Re: Feflow 7.1 Release date?

    FEFLOW 7.1 has already been released. It can be downloaded from https://www.mikepoweredbydhi.com/download/mike-2017/feflow. Please note that the updater in FEFLOW only installes new minor updates, the major versions are installed separately. With this, you get the possibility to have more than one major version installed in parallel.
  • Re: Ifm deactivating elements and the DAC file

    I think they're not - as all other material property changes that you do during the simulation via IFM/Python. The DAC format currently only provides the possibility to record changes in BCs (as they can also occur without using plug-ins due to constraints), and the option to record reference distribution changes.
  • Re: Temp. dependecy of Thermal Conductivity ..

    Maybe I should also add that the answer to question 2 has changed as well since 2008. FEFLOW does now support directional anisotropy in the dispersion tensor.
  • Re: Temp. dependecy of Thermal Conductivity ..

    FEFLOW itself is still not. There is, however, a plug-in that we developed in collaboration with a client. We haven't completely finalized it yet in terms of testing and documentation, but I might be able to send you a preliminary version. The plug-in covers a number of different relationships for the dependency that can be applied (element by element using different relationships in the model if appropriate). As all plug-ins by DHI that are not contained in the FEFLOW installation, this will come without any warranty or liablility on the side of DHI.
  • Re: Rate Budget Fluid Imbalance

    Actually the help was updated. When you look at the 'Rate Budget Panel' page in the help system, you'll find exactly the three components listed that are mentioned in the other post. Regarding your model, it is hard to give you a recommendation without seeing it. Maybe you can narrow down the imbalance spatially by using the Subdomain Rate Budget / Subdomain Period Budget panels for parts of the model.
  • Re: Budget table - imbalance term


    The definition depends a little bit on the FEFLOW version, which is why you might have found different definitions. In later versions, the storage capture/release has been added to the budget calculation, leaving the imbalance to only reflect a remaining imbalance of all terms above, representing, for example, numerical errors. In your case, the release from storage (POSITIVE value) represents the amount that the storage in the system changes, i. e., the overpumping. The reason that the value is positive is due to the fact that water coming from storage in the model can be seen as a source of water for the model that can leave the model through any of the boundary conditions. Water that is additionally stored in the aquifer, vice versa, can be seen as moving into a 'sink', and consequently is shown as NEGATIVE.

    Good luck!
  • Re: Defining a coastal boundary as one of my boundary conditions using FEFLOW

    As a first step, you may have a look at the 'Henry' benchmark that comes with FEFLOW. It'll give you an idea of how to choose the BCs for the sea.