Denim Umeshkumar Anajwala

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]

The help system should already contain the new functions.

Hi Blair,

There's a very simple option for this - without any GUI programming on your side. The IFM function IfmEditProperties (available since FEFLOW 6.2) provides the functionality to bring up a Qt dialog for IFM data input from within FEFLOW. The dialog is customizable, and it supports lots of data types (integers, doubles, enumerations, strings, pathes, time, selection from a list of all time series in FEFLOW, selection from all nodal or elemental user distributions). Please have a look at the description in the FEFLOW help system.

There is also a (very simple) test example in the FEFLOW SDK data (C:\Users\Public\Documents\WASY FEFLOW 6.2\sdk\ifm\samples\simul\ifm_prop).

Good luck - and don't hesitate to ask if you struggle with the functionality!
Peter

There's a step-by-step description of the entire demo exercise in Installation Guide and Demonstration Exercise on http://www.feflow.com/manuals.html.

Hi Michael,

1st kind BCs are set as 'hydraulic head' in FEFLOW which means that - in your simple case - you set the elevation (ASL) of the groundwater table.

For soil temperature you should set the fixed T at the inflow boundary. If you do not set an initial temperature, you'd have to run the model until it shows a steady temperature distribution. So it might be more convenient to set the initials, too.

BC values can be visualized in two ways: Either you activate the value display in the View Components panel, or you use the Mesh Inspector. For learning such basic functionality, it might be good to go through the FEFLOW demonstration exercise once.

Good luck!
Peter

Sorry to open up an old thread once again, but the original question is still unanswered.
We've now started to take up the Python topic again. Please contact us if you're interested in beta-testing the current status of the FEFLOW-Python interface.

The max option turns the (internally set) well bc into a hydraulic-head bc if the head exceeds the maximum. So if your head would be above 0.5m, the well would be replaced by a head bc of 0.5m. If your well is meant to start pumping at head values of higher than 0.5m, then 0.5 will have to be set as the min constraint.
Please note: At levels below 0.5m the will will NOT be turned off, but converted into a head bc. If factors other than the well cause the lowering of the water table, the well may even start infiltrating water to keep up the 0.5m level.

In a Free and Moveable setup, FEFLOW keeps two sets of elevation: the original and the moved ones. Without having checked, I'd think that IfmSetZ will work on the reference elevations.

Jerome,
The trick is in the brackets used in my example above Head(0) refers to the hydraulic head at the node with the index 0. As the nodes are numbered slice by slice and with the same order on all slices, you can access the node exactly one slice below by taking the number of the current node and adding the number of nodes per slice. Head(Idx[sub]n[/sub]+No[sup]slice[/sup][sub]n[/sub]) then refers to the head one slice below. You will find the node index Idx[sub]n[/sub] and the number of nodes per slice No[sup]slice[/sup][sub]n[/sub] in the list of available parameters on the right.

Good luck!
Peter