Carlos Andres Rivera Villarreyes Global Product Specialist - FEFLOW

It will be helpful if you describe the parameter used and the workflow. In the attached image, you can see that FEFLOW recharge applied as In/outflow on top/bottom takes into consideration the area only. I believe you are using other parameter, applying an expression to the parameter, or other configuration, which could cause the unexpected values. In case you have very specific questions about your model, the technical support (mike.de@dhigroup.com) can take provide you detailed guidance. Best regards Carlos Rivera  

In the case of a 2D Discrete Feature Element (DFE), FEFLOW considers as thickness the dimension perpendicular to the plane. Best regards Carlos

Hola Cecilia, In general FEFLOW 7.0 is a very old version. Please be aware that Fully supported operating systems are Windows 7 Professional Service Pack 1 (64 bit), Windows 10 Pro (64 bit), Windows Server 2012 R2 Standard (64 bit) and Windows Server 2016 Standard (64 bit). The freezing behaivoir can be trigged by several issues, including the plug-in itself. I can only recommend you to work with the latest update of FEFLOW 7.0. Best regards Carlos Rivera

Hi Tomás,
With your explanation, it looks to me that the expression does not spatially constraint the operation. A mathematical expression is applied to the FEFLOW's parameter and to all the mesh elements (automatically). So, you need to reformulate the express, eg. to apply the In/Outflow on top/bottom only to specific areas. A tip: Expressions works also with Elemental User Distributions. You can use them for creating the constraints.
Please follow-up with our technical support at mike.de@dhigroup.com for details on the workflows.
Cheers
Carlos Rivera

Hi Emilia,<br> The definition is available in the White Paper Vol. IV page 49. Here is the link:<br> https://www.mikepoweredbydhi.com/-/media/shared%20content/mike%20by%20dhi/flyers%20and%20pdf/product-documentation/feflow%20white%20papers%20vol,-d-,5.pdf<br> <br> If you have any question about the applicability in a FEFLOW project, I would recommend you to contact the FEFLOW technical support at mike.de@dhigroup.com<br> <br> Best regards<br> Carlos

Hi Josue,<br> <br> Without looking the file, my first guess is that the observation points are just directly in the frozen soil. FEFLOW piFreeze reduces significantly the hydraulic conductivity and &quot;close&quot; the porosity in order to mimic the freezing conditions. For example, if you have low K values and together a boundary node at the same location, which could cause outflow, the situation may be an uncontrolled decrease in head.<br> <br> Please get in touch with MIKE Support (mike.de@dhigroup.com) for further discussion.<br> <br> Best regards<br> Carlos

Hi,<br> The problem is that you are missing the dongle drivers in your Linux OS. Please get in touch with MIKE Support (mike.de@dhigroup.com) for getting the installation packages.<br> Best regards<br> Carlos Rivera

Hi Philip,<br> Indeed, your observation is correct. FEFLOW automatic time stepping scheme will not necessarily fit the times of the observed time series. If that would be the case, an improper time series can &quot;damage&quot; the model performance significantly. Therefore, if you export the results corresponding to the time series of the simulated values, the export function will include all time steps. There are two cases:<br> (1) If the export does also contain the observed times, then it is just a matter to filter and discard all other times. You can do this task e.g., with a script. You can also have your own script accessing the FEFLOW - Python interface to loop from time steps within an existing FEFLOW result file (*.dac) and then export only data at time fitting your reference.<br> (2) If the export does not contain data at the observed times, I would recommend you to do an interpolation in between FEFLOW simulated times.It is always a prefer solution, so you do not need to affect much the automatic time stepping with extra values.<br> <br> Please reach out support at mike.de@dhigroup.com for specific details.<br> <br> Best regards<br> Carlos Rivera<br> <br> &#160;

Hi Matan,<br> We are not aware about a bug in piFreeze. But to me this sounds to the following problem: piFreeze will simulate the freezing conditions and therefore, it will change the conductivity and others. If the Fluid-Flux BC on the top boundary is not adjusted, then the amount of fluid could be excessive for the low conductivity values (let's say frozen conditions).<br> In general, you can always set a min./max. hydraulic-head constraint to the nodes associated to the Fluid-Flux BC.<br> Cheers<br> Carlos

Hi Tiago,<br> If you like to discard nodes to the coupling with PHREEQC, the only workaround is to use Inactive Elements. Although, this will inactivate all these nodes entirely from the flow and mass transport calculations.<br> Regarding to the error message with the OnTimeStepConstraint, it is something unknown to DHI. I recommend you to contact us via support.<br> Finally, the automation of files used in the pIchem GUI is not supported.<br> Cheers<br> Carlos