Denim Umeshkumar Anajwala

Yes, if any of your folder or file names contain blanks, you need to put those in quotes ("), otherwise the command is not read correctly. I made it a habit to include those all the time, so you never run into this problem.

You also need to set up a FEMDATA folder for your FEM files, and a RESULTS folder for your DAC/DAR files. FeFlow expects these default folder structure when running in batch mode as documented in the online help.

Once you got it figured out, it's pretty neat though and opens the door to a lot of cool applications, like PEST or automated Sensitivity Analyses (SensAn).

Good luck, Chris

Hey Gnapser,

which programming environment are you using? Visual C++? Visual Studio .net? This problem has to do with you "include directory" settings, and depending on what software you use, this is set slightly differently.

It also depends on the version of FeFlow you're using, since starting with version 5.3 (I believe it was), the location where FeFlow saves its shared files has changed. It now supposedly uses the Vista default location for shared files :-\

In any case, you need to find the location where 'X11/Intrinsic.h' is saved first.
FOR ME, this [u]used to be [/u]
[b]"C:\Program Files\WASY\FEFLOW 5.3\sdk\ifm\include\xdk"[/b],
but in the latest version of FeFlow it [u]changed to[/u]
[b]"C:\Documents and Settings\All Users\Documents\WASY FEFLOW 5.3\sdk\ifm\include\xdk"[/b].
Once you're in folder xdk, you should see a subfolder X11 and in there file "Intrinsic.h". Found it?

Now you need to specify this path (up to ...\xdk) as an "include directory":
For [b]Visual C++[/b], this is shown under "1) Add IFM include and lib paths to the VC global settings" in the documentation you mentioned (unless this has changed in a newer version of Visual C++).
In [b]Visual Studio .Net[/b] you'll find these settings under "Project - Properties - Configuration Properties - C++ - General - Additional Include Directories"

In the same way you should add the "...\WASY FEFLOW 5.3\sdk\ifm\include" directory.

The other setting you might wanna check/correct is the Library files folder. For Visual C++, see your documentation. For Visual Studio .Net go to "Project - Properties - Configuration Properties - Linker - General - Additional Library Directories". The path ends in "...\WASY\FEFLOW 5.3\sdk\ifm\lib\x86", and again depends on where FeFlow saved those shared files on your system.

Try to make those changes and compile your project again. Let me know if it works this time!

Cheers, Chris

I am working in a Open Pit too, I try to modelizy the influence zone.

I think the best to model the mine, is constant HEAD ( 1 firs condition) with the value of the bottom of the pit

Cheers

hi!
what you are actually determine is the depth of the well screens.
i.e. the z coordinate of slice 2 is the position (depth) where the screens are.

Elad Dafny

1) how much does 400 m3 makes in % of your total budget?
if it is just a small percent you can ignore it!
2) when you set the 3rd. kind boundary you can constrain the in and out flux.
    maybe you haven't done that?

all the best,
Elad Dafny

hi torsten-
try to delete the two top lines.
leave only two columns of numbers..

gooday...
Elad

Qinghuai:

There is no difference really, other than the data input. In (a) Multi-layer mode you can simply put in the top and bottom depth (or elevation) of the well and the pumping rate. FeFlow will figure out which slices should have BCs. If you use (b) Single well mode, [i][b]you[/b][/i] need to figure out, which slices you need to put the BCs on. Option (a) is easier.

Chris

Hey Thomas,

thanks for you interest in our IFM modules.

I hope our paper didn't say, that the TecPlot IFM exports particle tracks?! As much as I wished we could do that, that's unfortunately not possible at the moment, since FeFlow doesn't provide access to the particle track data through API functions :(

Our TecPlot IFM "only" exports the following data:
     - nodal properties:        head, pressure, velocity (Vx, Vy, Vz), saturation, mass
     - elemental properties: conductivity, kZones (an elemental reference distribution)
The data gets written to a PLT file as a FE data set, which can afterwards be imported and visualized in TecPlot. The module provides similar data as Dr. Braun's "Interface to TecPlot" (listed on before-mentioned web page), which ours is actually based on.

I've developed over 50 IFM modules at AquaResource over the last couple of years. Some of them are extremely powerful and automate our work-flow to a large extent, which makes data exchange with FeFlow not only a lot faster, but also a lot less error-prone. We are currently preparing to make some of those IFM modules available to interested FeFlow users, but I can't quite say, when exactly that will be. There is a good chance that we'll announce the launch date in this forum though :D

Hope that helps, Chris.


PS: I attached the mentioned paper ''IFM tool development to streamline data management for large-scale models'' for the curious reader.

Please take a look at the seepage face boundary condition. For details see the documentation (e.g. users manual).

How about increasing K for the part of the model domain that gets excavated? That's the second change we normally make, but is that even required/suggested?

Thanks, Chris