-
No, there is currently no pilot point support in the internal PEST interface in FEFLOW. For using pilot points, you'd have to use PEST as a standalone program, running FEFLOW in batch mode. On http://www.feflow.info/miscellaneos.html, you find FEFLOW-specific data tools for PEST that make the use easier.
-
The function you mention calculates fluxes at boundary conditions. If you have set a boundary condition around the tunnel, the amount of inflow is not limited to the amount of water in the tunnel.
-
You can jsut see the coordinate.
-
Using discrete elements, the fractures will be 'between' the layers (if you think about horizontal fractures). They will be reduced in the model to 2D. FEFLOW does not handle a double porosity approach, where the same layer has different properties for the fracture and matrix parts.
-
For transient simulations, you can do scatter plots either for one time step and different locations (in the same way as for steady-state models), or for one location and different time stages. For the latter, right-click into the diagram, select 'properties', load a reference curve for the observation point you want to do the scatter plot for and click the scatter plot button.
Peter
-
The default condition is no flow/mass flow/heat flow.
-
When compiling for 64-bit, make sure that you use "<FEFLOW Root Folder>\[b]bin64[/b]\feflow.exe" in step 4.3 ;)
I normally change the configuration to 64-bit first and then set the project properties. I found, it works better that way, but forgot why. The above mentioned setting was one reason though ....
Cheers, Chris
-
You can find a description of all the functions in Appendix B of the IFM part in the FEFLOW help system.
-
Currently indeed there is no joining option for polygons in the boundary condition editor. One option would be to create a zig-zag line inside the river. Other options include putting the bc manually, by using a line in the middle of the river and a higher snap distance (assuming the the width of the river is more or less constant), and exporting all the FEFLOW nodes to a GIS format, clipping the ones in the river and importing them back as a BC.
-
Output made in IfmDebug will be written to the debug window, which can be opened from the Window enty in the FEFLOW main menu.
The program can have as many functions/classes/etc. as you want to.