Carlos Andres Rivera Villarreyes Global Product Specialist - FEFLOW

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

Hi Adaliyaz,
The situation described can only happen due to the following reasons:
- There is a boundary condition constraint (BCC) associated to the node.
- There is a time series assigned to the boundary, e.g. with a "GAP".
- There is a Modulation function assigned with a time series and this has a "GAP".

(Of course, there could be a user-imported Python script doing things during the run).

In case you have any further question, please get in touch with support (mike.de@dhigroup.com).

Cheers
Carlos

Hi Billy,
FePEST will recognize all nodal selections marked with the option "Budget-History charting". The option is found with a context menu of the specific selection in the FEFLOW GUI.
Subsequently, FePEST will offer you the options Fluid Rate/Period from the Obs. Def. section in the Problem Settings dialog.
Cheers
Carlos

The reason could be that you are solving the flow equation by using "Free and Movable" in the Problem Settings dialog. Inactive elements are not supported under this approach.

Hi Robin, I would recommend you to get in touch with our technical support team at mike.de@dhigroup.com.

Cheers
Carlos

Hi Joshua,
Typically, discrete features elements (DFEs) are fully coupled to the matrix. That is the default set-up, i.e. whatever happens in the pipe, it will also happen "outside". However, the exchange between the DFE and the matrix can be controlled. I would recommend you to look the online help system: http://www.feflow.info/html/help75/feflow/09_Parameters/DFE/nodesplit.htm
Cheers
Carlos

Hi Yonas,
Your post may not have came all the way. FEFLOW supports the connection of historical data (measurements as constant and/or time series) to any observation point. Data can be linked to process variables for the flow (head, pressure, moisture, saturation), mass transport (any species concentration), heat transport (temperature) and groundwater age transport (age, lifetime expectancy and exit probability).
Cheers
Carlos