Hector Montenegro Feflow-Anwender

Dear group,

I have identified  steep elements as a possible source of instabilities during an 3D unsaturated calculation.
Having around 25 000 elements I wonder if there is a tool to inspect the mesh topology. I need to have a kind of coincidence matrix with the relation between element and node's elevation.
The table should have the the following structure:

element nr. | node1 | node2 | node3 x1| y1 |z1 |x2 |y2 |z2 |x3 |y3 |z3

Then I could check where those elements lie spanning extreme elevation differences.
Is there some tool how to obtain such a structure from fem-data?

Regards

Hector

Hello  FeFlowers

the conventional export format for a complete set of observation points each time (dar-file) step is not very handy when one is interested in plotting the time series of different observation points.
If the format was printed out as described further down. one would need only to read the file and could immediately plot the time series:

for heads

[table][tr][td]node  location_x location z time 1 time2 time 3 time 4 time 5 time 6  time 7...
1                x1          z1              h1      h1    ...                 
2                x2          z1              h2      h2    ...               
3                x3          z3              h3      h3    ...               
4                x4          z4              h4      h4    ...                [/table]
...
...

the same structure for vx and for vz

Is there a tool to transform the dac-files, so that the results can be visualized faster?


Thank you for any hints

Hector

Hello everybody,

we are dealing with geotecnical erosion problems and would like to identify zones of dangerous hydraulic gradients.

We need the representation of the [b]directional components hydraulic gradient[/b].
Is there any routine similar to the IfmGetResults*VelocityValue which evaluates gradient rather than velocity?

I do not know exactly how those IfmGetResults*VelocityValue routines are coded, but since the velocity corresponds to the hydraulic gradient times conductivity the implementation seems straight forward (division of velocity with conductance matrix at the element level, after that summation over all nodes and division by the number of nodes at the patch?).

Of course one can figure out a name for the "babies":

                                hydgrdx = IfmGetResultsXhydgrdValue(pDoc, i)
                                hydgrdy = IfmGetResultsYhydgrdValue(pDoc, i)
                                hydgrdz = IfmGetResultsZhydgrdValue(pDoc, i)

Has such a routine yet been developed? Any volunteers for this?

Hector Montenegro

In unsaturated flow storage is represented by the water capacity term which is essentially the derivation of the saturation–pressure relationship. A look at this functional relationship reveals, that the water capacity term can decrease strongly at high and at low saturations, depending on the soil hydraulic parameters. However I can not figure out, that the compressibility term should have such a strong influence under unsaturated flow conditions.…

Sorry, die Frage war schon mal hier und ich bin fündig geworden:

For using the FEFLOW datatools, please see tools.pdf in the /doc directory on the FEFLOW DVD.

Hi outthere!

I want to check the horizontal and vertical cross sections of the different slices in the 3D-Layer configuration \z-coordinates viewer menue, but no cross sections are drawn. Is there a bug in FF 5.3?

Regards

Hector

Hallo Feflowers,

da gibt es so einige nette Tools, wie dar2pow usw., die adas LEben vereinfachen können.
Kann mir jemand verraten, wie diese (sind das UNIX-Scripte? ) unter Windows aufgerufen werden?

Danke

Hector