Denim Umeshkumar Anajwala

[quote author=dstone link=topic=406.msg920#msg920 date=1209144551]
The FEFLOW online help indicates that a 3D (X-Y-Z-F) export option should be available for outputting nodal/elemental values as points in the Plotting Output Options of the Data View, Operation, and Export dialogue box for 3D models. However, this option does not appear for my 3D model; it only allows 2D output for the current slice. Is there some other switch that needs to be set to enable this feature? I encounter the same problem whether I am trying to export from the Problem Editor (e.g., Flow Materials, using the "Special" option) or from the Postprocessor (View Results).
[/quote]

Dan

If you select ASCII databases (XYZF) (*.dat) as the output type, you will be given another dialog where you can choose all slices (or layers) OR only the current slice (or layer).

I am not aware of any special switch or setting which controls this behavior. I tried setting up a mock 3D, 1 layer model, and it asked me if I wanted to export data for all layers. A 2D model only allows export of XYF data.

Dwaine Edington

Hey Pejman,

yes, you will need a C++ compiler (I don't think a C compiler will do). However, Microsoft started providing some of its software for free, as what they call their Express versions. You can download Visual C++ Express from

http://www.microsoft.com/express/download/

I haven't used it (we use a licensed version of Visual Studio .Net), but I tried SQL Server Express before and that worked fine.

The trickiest part will pbly be to get the compiler set up correctly. There is a section in the IFM documentation, that describes it, but you might have to adjust that for using Visual C++ Express and the newest version of FeFlow, which saves some shared files in different locations (see my post in "creating module with published source code" in the "IFM and Filter Programming" section). If you can't figure it out (with help from the support team), let me know and I'll see what I can do.

Good luck, Chris

Hey Pejman,

personally, I would stay away from messing around with the FEM file. Once you've read the file specs, you'll pbly understand why.

The "wise way" that I'd rather suggest is using the InferFace Manager (IFM) to create your own data importers (and exporters, if needed). This can be done, so that these importers are called automatically before every flow simulation (PreSimulation) for example. All you need to do then, is manipulate the default input files for those importers externally. This, however, can be done in a much safer way, since you define the format of these input (ASCII) files yourself, and hence you know exactly how to modify the data.

We've used this approach with SensAn, a Sensitivity Analysis tool, that's freely availbale as part of the PEST package. See attached flowchart for details.

Coming from MatLab, you pbly know enough C syntax already. That plus a C compiler is all you need really.

Chris

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

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.