-
In many such cases a larger model area would be a good idea, at least if the outflow occurs in the same aquifer the river is in. Putting a boundary condition below the river can of course produce a model outflow, but - no matter what the BC is - most probably not reflect the natural conditions very well. For example, the aquifer on the other river side in reality will contribute to storage etc., and you cannot consider this by just putting a BC. As a personal opinion I think that groundwater models are way too often cut off at rivers as assumed natural boundaries, while in reality there is significant flow across the river in the aquifer below, and the conditions on both sides of the river influence the groundwater conditions.
-
Hi,
The file looks OK at least at first glance. Did you check the properties of the Observation Point in the corresponding dialog after import to make sure the import worked well?
Peter
-
The expressions can currently only be used to assign values to a BC, not as expressions that are evaluated during run time. This is only possible for the recharge and source/sink parameters (flow and transport). If this is about an open-loop geothermal system, where the injection temperature is 5K different from the extraction temperature, the FEFLOW support team can provide you with a free plug-in achieving this (OpenLoop). If it is nodes other than pumping wells, you'd have to program your own plug-in or python script.
-
Well, I just received an answer from WASY. FEFLow 6.211 (p11) works better witn VS 2013.
-
Hi.
Anyone knows which version of Visual Studio is compatible with FEFLow 6.2 (p11) to write plug-ins?
Thanks in advance.
-
FEFLOW uses the concept of an 'equivalent freshwater head' where the hydraulic head is expressed in terms of an equivalent head at freshwater conditions. Thus in case of saline groundwater, hydrostatic conditions result in an equivalent freshwater head that increases linearly with depth. The same concept has to be applied to initial head throughout the model domain. So in FEFLOW 'head' never means 'saltwater head' but always 'equivalent freshwater head'.
-
Just export any nodal property (e.g., hydraulic head) with a right-click on the parameter in the data panel.
-
Selva,
You may have a look at the Henry example which is very simplified, but based on the same principle. Let us know if you still encounter problems. Once you've installed the FEFLOW Demo Data package, you'll find the Henry benchmark in C:\Users\Public\Documents\WASY FEFLOW 6.2\demo\benchmarks\femdata\bench_henry.fem (path for Windows 7, can be different on other operating systems).
-
This is not a bug. The switch only provides alternative access to the setting for the top and the bottom. It is not a switch that changes any option in the model - the model switch is the 'constrained' vs. 'unconstrained' for both top and bottom.
-
You can keep the whole FEFLOW GUI with all the panels on one screen, while you have one view on the other screen: Just use the context menu of the view you would like to get in full screen mode and choose 'Full Screen on display ...'. With this, you can dock the panels as usual.