Carlos Andres Rivera Villarreyes Global Product Specialist - FEFLOW

Hi Ludwig,

Unfortunately at the moment, FePEST graphical interface does not support unsaturated parameters as a Parameter Definition for calibration.
However, you can still calibrate these variables including a so-called IFM-implemented parameter definition. You will need to write an IFM plug-in to retrieve and set unsaturated parameters, basically you will use the following functions:

IfmGetMatUnsatAirEntryPressureHead
IfmGetMatUnsatFittingCoefficient
and their corresponding IfmSet... functions.

Cheers,

Carlos

Hi Roby,

You need the following steps:

1) In FEFLOW 6.2, you need to assign manually the BC corresponding to the first and final nodes.
2) Next to the assignment toolbar, you will find a new icon named 1D Linear Interpolation. This is together with other options such as Assign Data by Map (Point, Line or Polygon).
3) After having activating 1D interpolation option, you will have to trace a line connecting the first and last nodes.
4) Ready :-)

Carlos

Hi Elena, could you be more specific?

Hi,

You can make the assignment of the pumping wells via the Parameter Association Dialog (right click on a specific file in the Map panel). Here, you can find several ways for Neighborhood Relationship. In the help system there is a fill description of all variables.
In principle, it is always recommended to make a local refinement around pumping wells in order to improve the numerical solution. So, if you are not very far with the model setup, I would highly recommend you to go back to the Supermesh View and reformulate your conceptual model (e.g. include new wells, generate new mesh with local refinements, etc.).

Cheers,

Carlos

Hi Adam,

If a client command does not complete FePEST gives up after <Timeout> seconds, but then repeats the failed command. The idea behind this is to try to make FePEST tolerant of temporary network problems.

We have tried starting a FePEST server with an invalid FEFLOW license and ran a parallelized FePEST problem. The server log repeated the message “not licensed”, just as you mentioned. However, pressing stop on the client cancelled the PEST run, after a short delay. (In some cases it may be necessary to stop the server first). So, we weren't able to reproduce your problem, just by making the license unavailable. I guess what your workflow must have been slightly different.

Cheers,

Carlos

Hi Adam,

Here we go...

The default Timeout is 30000 msecs (= 30 seconds), which is the time the client or server waits until assuming that the requested operation failed, and repeats it. This default value is also the default of the underlying library function used by FePEST. It may be possible to lower this without side effects, but beware, if the network is responding badly, or if the FEM is very large then a low timeout could mean client/server communication can never succeed. You can modify its value with a registry entry named Timeout.

In general you can track errors using the log FePEST file: %TEMP%\.fepest62\log.txt

To forcibly stop PEST, you should use red stop button. Sometimes you may have to wait a number of seconds until it works. This is because is carrying out the last FEFLOW run. The black Kill button is more brutal, and kills the process and so should be used only if the red stop button fails.

Cheers,

Carlos

Hi Adam,

Good to know that you are intensively testing new features in FePEST! Here some ideas you could use in your workflow:

- FePEST can be started in server mode directly from the command line:
e.g. [color=red]"C:\Program Files\WASY\FEFLOW 6.2\bin64\fepest62.exe" -mode=server[/color]

- You can alter the port on which the FePEST server (where the slaves run)  using a registry setting. This should be created in the following manner:
e.g. [color=red][HKEY_CURRENT_USER\Software\DHI-WASY\FEFLOW Parameter Estimation] --> "Port"=dword:000013bb[/color]

- This registry setting must also be set on the client (master) computer. Please note, the input is in hexadecimal but you can also choose decimal using regedit. Deal with careful any modification in the Registry Editor, incorrect changes can affect FePEST installation. The port on which BeoPEST runs, is set in the FePEST Settings dialog on the Parallelization page.

- PSLAVE.EXE is part of the parallel pest solution PPEST. FePEST uses BEOPEST (third-party software) and, as stated above, this port is specified in the FePEST Settings.

Hope I could clarify your doubts. Let me know you have other questions under specific circumstances of your network.

Cheers,

Carlos

Hi nnoufysalam,

I can give some general tips for your purpose. Of course there are so many details to handle via forum.

Regarding to the concentration boundaries of river water or sea water, you need to know first the groundwater flow direction. Do you have issues of seawater intrusion? If so, it is good to prescribe a fixed concentration on these nodes. If you have outflow from the model to the river boundary all the time, concentration may not be necessarily prescribed, just leave that FEFLOW computes these values. But if you want to simulate the interaction between river and aquifer, then concentration should be prescribed in case of inflow from river to aquifer.
FEFLOW provides possibility to use the so-called constraints in order to activate or deactivate boundary conditions. I guess you can find additional info in the forum and for sure in user manual and help system.

For the case of the artificial pond, you can prescribe both water levels and concentration as Dirichlet boundary condition, if these are known.
Percolation flux from the artificial pond can be easily computed using budget panels. There is a plenty of information about this in FEFLOW User Manual and Help System.

Hope you get some idea how to start...

Cheers,

Carlos

Hi Adam,

Thanks for sending us your files. After developer checked case, he could reproduce your problem. The reason is that the FEM file was saved in ASCII format. If you save in a binary format, problem is gone.

A future version of FePEST will handle this special case, but until then please use this workaround.

Cheers,

Carlos

Hi Adam,

Thanks a lot for reporting this. Could you please send us both fem and fps files to the FEFLOW support address?

Cheers,

Carlos