Carlos Andres Rivera Villarreyes Global Product Specialist - FEFLOW

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

Hi Bohan

The API is named IfmSetMatFlowRechargeValue. You can find below the documentation for both C++ and Python, respectively:

http://www.feflow.info/html/help75/feflow/13_Programming/IFM/API/IfmSetMatFlowRechargeValue.html
https://dhi.github.io/ifm/api_doc.html?highlight=recharge#ifm.FeflowDoc.setMatFlowRechargeValue

Best
Carlos

Specific storage (compressibility) follows the standard definitions in hydrogeology.&nbsp;Specific storage describes the change in volumetric water content in an aquifer induced per unit change in hydraulic head under saturated conditions. Along with specific yield, specific storage describes the storage properties of an aquifer. As in unconfined layers specific yield typically exceeds specific storage by far, the influence of this parameter in aquifers with phreatic surfaces is usually negligible.<br> You can find all the parameters described in the online help:<br> http://www.feflow.info/html/help75/feflow/09_Parameters/Material_Properties/flow_parameters.html

The most probable is that the cache file is somehow damaged e.g, saving was interrupted, etc. You can delete the *.cache file, open the FEM file and FEFLOW will recreate the cache file again. If this does not help, please contact support.

We will make the test cases available soon. Thank you for understanding. What I can say for now is that the performance gain in PETSc with&nbsp; the GPU-accelarated AMG method becomes significantly visible for large FEFLOW models (e.g. at least with 1 million elements). This could be even a factor of 2.