Please wait...
×

Error

  • Re: Mike11, Feflow and ifmM11 conection

    In following please find some answers here:

    1. No, the different layers should represent your geological layers. There is no need for an extra layer.
    2. IfmMIKE11 will automatically assign Fluid-transfer BC's with a reference head which corresponds to the water level of the river computed by MIKE11. You need to assign corresponding In-transfer rate and Out-transfer rates.
    3. It depends on what exactly you want to do.

    For further questions, you can also contact the FEFLOW Support: https://www.mikepoweredbydhi.com/support
  • Re: Batched budget export

    Sure, if you write a module / script for retrieving the budgets you can save a remarkable amount of time. One option is to retrieve the budgets via the budget histories. You can retrieve the histories anytime (e.g. during the simulation or after the simulation). In my point of view, this option is the most comfortable way, because you do not need to loop through mesh nodes to retrieve the budgets.

    The FEFLOW Demo data provide a sample Python script which illustrates the workflow (getBudgetHistories.py):
    https://www.mikepoweredbydhi.com/download/mike-2017/feflow-demo-data?ref=%7B48049242-9F00-48BE-82FA-7D0C1820F7A8%7D

    Apart from retrieving the budget histories, the script also plots the histories as a png-file.

    Please note, due to historical reasons the budget histories are available in single precision only.

    Of course, alternative workflows for retrieving the budgets are also available. Please let me know if you do not like to use the histories.
  • Re: fully unstructured 3D mesh

    It's difficult to say what is causing the problem. In principle, one can transfer a geological model developed in Leapfrog to FEFLOW. In order to go into more details, please contact the FEFLOW Support Team: https://www.mikepoweredbydhi.com/support
  • Re: Flux vector at each element or element's faces

    The elemental Darcy flux can be retrieved as a scalar quantity in the Data Panel => Process Variables => Fluid flow
  • Re: Buondary and initial conditions

    At a first glance, it seems to me that the Fluid-Flux BC (Gradient) might be a possible option. http://www.feflow.info/html/help71/feflow/mainpage.htm#t=09_Parameters%2FBoundary_Conditions%2FFlow%2Ffluid_flux_bc_gradient.html%3Frhhlterm%3Dgravity%26rhsyns%3D%2520. If the Fluid-Flux BC (Gradient) is not what you are looking for more details are required to conceptualize your model. Please contact the FEFLOW Support: https://www.mikepoweredbydhi.com/support
  • Re: Transiente Conductivity

    Yes, there is a fast way in assigning time-dependent K-values for different layers. You can use a parameter for assigning the time-series. For each layer use a Parameter link. More information about the assignment of time-dependent material properties is provided here: http://www.feflow.info/html/help71/feflow/mainpage.htm#t=09_Parameters%2FMaterial_Properties%2Ftime_varying_materials.html
  • Re: Using Intel Compiler with IFM

    Which operating system are you using?
  • Re: FEFLOW 7.2 demo files

    Please note that FEFLOW 7.2 is not released. A half year ago we released FEFLOW 7.1 and FEFLOW 7.2 is still under development. Accordingly, demo data for FEFLOW 7.2 do not exist yet. If you are interested in the FEFLOW 7.1 demo data you can download it from the DHI website: https://www.mikepoweredbydhi.com/download/mike-2017/feflow-demo-data?ref=%7B48049242-9F00-48BE-82FA-7D0C1820F7A8%7D
  • Re: Potential error in reference density default value

    Thanks for the note. The bug will be fixed as soon as possible. Please note that the value used there does not affect your computations. It is used for plotting purposes.
  • Re: Multilayer well BC to simulate a horizontal well

    Sure, it is reasonable to assign horizontal wells if it represents the setting of your model domain. I agree, the name Multilayer Well might be misleading in this context.