Denim Umeshkumar Anajwala

As far as we know you'd need a licensed copy. We're not aware of a free option at the moment.

We are working on such a link and a corresponding plug-in will be available soon.

That's quite unfortunate. Is there anyone else experiencing the same?

I am afraid that the help system is wrong with this respect - it will be corrected with the next patch. The Microsoft Access database engine only enables the Access formats; for using Excel files, you will need an Office installation. I apologize for the inconvenience.

http://forum.mikebydhi.com/index.php/topic,1904.0.html

Isn't there some time of the year coming up that is usually related to presents?

This zero pressure isoline does not relate to an actual water table as the model is calculated as fully confined. I highly recommend to do an unsaturated simulation if the phreatic surface needs to be considered.

Hi Laurie,

There's no pseudo-unsaturated approach for 2D vertical models. This means that unless you choose Richards' equation, the model will be fully saturated and calculated as confined. To get a quick solution, you might choose the unsaturated mode with simplified parametric relationships (e.g., the linear model).

Peter

Hi Ranjeet,

When FEFLOW continues to show up as process in the task manager after closing, this indicates that a thread initialized by FEFLOW (f.e. when clicking on a diagram, or the mouse-capture by the polygonal selection) got stuck. So even when the main program is closed, this threads still exists and shows up under processes. Killing this process is therefore ok, however, our support is going to have a more detailed look into this issue here and see if we can reproduce it.

Best regards,

Bastian

Hello Ranjeet,

The issue is related to the mouse click (capture), it may also happen when clicking polygonal selections. This capture event needs to interact with the operating system via the graphics' driver. Since this operation is taking place outside FEFLOW, it is not traceable for our developers in debug mode.

I found a workaround some time ago: Closing all active programs in the windows task bar (basically every program which is also addressing graphical features, such as browsers, mail programs...) helps. Uninstalling FEFLOW, changing the graphics driver or deactivating the hardware acceleration did not help in my case. My system specs are: Core I5 Windows 7 64 bit with 8 GB RAM and Intel HD 3000 graphics.

In the meantime our developers are looking for a solution, but since this bug is a tough one, it may take a while. Thanks for your understanding,

Bastian