S Heermann

Are diffusion/dispersion  reversible processes?

Do you have a recommended procedure for setting up a 3D unstructured grid radiating normal to a horizontal tunnel and that can handle horizontal stratigraphy and boundary conditions at the ground surface? 
Is this feasible? 
Where do I begin?

Does FEFLOW support exporting models to .obj or .stl  file formats to use for 3D printing?  If not, could you recommend a workaround?

I am having problems importing polygons for use in creating a supermesh file.
This especially occurs for the scenario where I have carved out a hole (i.e. island) in the polygon and replaced it with a a second polygon.
(Note: in carving out the hole, the main polygon is divided into two parts, one for the perimeter and one for the hole)
I have checked to be sure all vertices are alligned.  But I still get error messages like the ones shown below.

        Warning: Polygon #7 ring 2 dropped since overlapping with polygon #7!
        Warning: Polygon #10 dropped since overlapping with polygon #7!

Do you have any suggestions to improve the work-flow processes or on the availability of specific GIS tools to create internal polygons?

So what can one do with this added capability?  Are there any ifm functions that can take a selection as an input item? 

Also, how could one extract a list of nodes or elements using the selection handling functions?

The 'What's new in FEFLOW 7?' help page refers to some new functions for selection handling (e.g. IfmGetNumberofSelections, IfmCreateSelection) but these are not listed in the IFM API Functions page.  What's up?

I have had excellent luck using the new python capabilities.  However, I cannot figure out how to get flow budget information at selected nodes.
I understand that the standard ifm procedure is a two-step process of creating a budget and a pointer to that budget and then referencing the budget at a given node.  But I don't understand how this translates into python functions.

When FEPest calls the FEFLOW kernel, are the process variables FEFLOW saved within FEFLOW after each model call, or do they remain constant during the parameter estimation process; i.e. do the initial conditions change or stay constant between Pest calls?

Importing observations from files and or cut-and-pasting them from an excel worksheet seems a bit awkward.  Two things might improve the process:

1) character spaces within the individual header items could be removed, or substituted with a "-"; e.g. Observation type -> Observation_type, Obs. point -> obsPoint, etc.  so that they do not get split into multiple columns when pasted into Excel; and

2) Have the column specifying the observation group be visible in the FEPest observations table and not just when pasted to a spreadsheet.

I recently used Python to extract parameters and create tables summarizing parameters for a range of "zones"-- it works great.  I would like to incorporate it into the parameter estimation process, but I haven't quite figured out how yet.  Any thoughts?