Denim Umeshkumar Anajwala

This topic has been moved to [url=http://forum.mikebydhi.com/index.php?board=3.0]FEFLOW[/url].

[iurl]http://forum.mikebydhi.com/index.php?topic=2127.0[/iurl]

There's currently no such plug-in I know of. It's a problem that, of course, can be solved by plug-in programming. Another solution - depending on the exact circumstances - could be to connect the seepage nodes by discrete features and then connect their lowest point to the infiltration point by an arbitrary discrete feature. This would only work, however, if infiltration is gravity-based.

found it:

tools --> units --> time [d] for x-axis
                    --> Concentration [mg/l] for y-axis

Hi there,
in mass transport, how can I change the unit of the axes in the "local concentration history"-chart? I want to have [mg/l] and [d] and don't find a option to change them.

Thx!

Hi there,

a simple question:
If I have a background concentration set to 5 mg/l in my model area, so also all b.c. got 5 mg/l,
how can I tell Feflow to give the rain (inflow on top) the same concentration? Or also inflow from bottom? Can I give both inflows (bottm and top) a different value, bottom for example 10 mg/l? Where do I set those in Feflow? Reference co?

Thanks!

Have you checked the setting for Minimal Slice Distance in the Editor Settings of the Problem Settings dialog? The distance defined there will determine when the verification dialog will appear. This is to make sure that the verification does not only check for intersection, but also for very small distances. If - for example - a distance of 0.01 m is set there, and you set a distance of 0.01 m, it may happen that the dialog comes up due to to internal rounding/variable conversion that makes 0.01 m into something that could be just a little bit larger than 0.01 m.

Version 6.0 of FEFLOW was somewhat 'in between' the Classic and the new Standard interfaces. This means that the new GUI did not contain the full functionality that was available in the classic interface. The observation point groups were added to the new GUI later on, and of course they are now available. If you have the means, I'd recommend updating at some time to be able to use all the improvements made since.

In Phreatic mode, FEFLOW (since version 4.x if I recall correctly) applies recharge to the top nodes (ground surface). So recharge has to pass the pseudo-unsat zone before reaching the water table. For details, you can also have a look at the corresponding explanation in the User Manual.

Depending on the relation between infiltrated water and lateral groundwater flow, in such a 2D model a temperature bc might lead to an overestimated impact of the temperature of the infiltrating water (all water passing these nodes will get this temperature). The only possible alternative is then the use of heat-source boundary conditions, calculating the source in advance. Please note that for this option you will need to use the divergence form of the heat-transport equation, so that the  heat-source BCs describe the total heat flow, not only the dispersive/diffusive part of it.

Hi.

Thanks a lot, this is exactly what I was looking for. I modified a little the code to read string variables (input2) and store them outside the OnEditDocument callback for later use in another callback

[color=blue]// Callbacks
/* Global variables to store data from OnEditDocument callback and use them later */
double global_input_1;  
char* global_input_2;

void CPlug_In1::OnEditDocument (IfmDocument pDoc, Widget wParent)
{
double input1 = global_input_1; // User input variable 1 initialization: DOUBLE TYPE
char* input2= global_input_2 ; // User input variable 2 initialization STRING TYPE

IfmProperty props[] = {
{"Parameter 1 (double)", IfmPROP_DOUBLE, &input1 ,NULL, "This field captures a DOUBLE  variable" },
{"Parameter 2 (string)",IfmPROP_STRING, &input2, NULL, "This field (and only) captures a STRING variable" },
};

IfmEditProperties (pDoc, "Properties of Parameters 1 & 2 in User Plugin", "My parameters: ", props, 2); // Last number is amount of input values.

global_input_1 = input1; // Taking the values from variables in this callback to
global_input_2 = input2; // use them in another callback
}[/color]