Peter Schätzl Grundwassermodellierer

Yes, you can move maps in the View Components panel. I think by default they are shown in the order they have in the Maps panel which also can be changed by simply dragging maps or folders around.

With respect to the selection, you can set marker points for TetGen (one for each lithology, just anywhere within the volume. I've never done the transition from Leapfrog to FEFLOW unstructured myself, but I can imagine that Leapfrog is not able to export the lithologies as non-manifold geometry, i. e. without overlaps and intersections. This, however, is a condition for the TetGen algorithm to work (FEFLOW only does very simple corrections like dropping duplicate triangles before handing over to TetGen).

You can get the heat flow by using the subdomain rate budget panel (using a domain of interest an a masking domain if you need heat flow through a plane, for example).

You can do that by using the Period Budget panel and the 'Export' option therein.

1) You apply the temp BC to the bottom node of the MLW (FEFLOW internally sets the well BC at the bottom node, with a discrete feature above)
2) For OpenLoop Design, the help says what I've put below; OpenLoop I do not have (as I'm no longer with DHI), and I don't recall exactly what it needs (though I coded it a long time ago...):

"3. A nodal distribution in User Data with the name 'OpenLoop' is created to identify participating nodes.In that reference distribution, all nodes belonging to a specific group (injection and extraction nodes) are assigned the same integer value. All other nodes should have values less than or equal to 0. In case of using multilayer wells, only the bottom nodes of the multilayer wells should be included in the distribution. Be careful with mesh refinement: In case of refining the mesh after assigning the power function number, the data interpolation will lead to a number of nodes with non-zero values around the wells, too.

4. A second nodal distribution in User Data with the name 'OpenLoopPortion' is to be created to define the portions of injection/extraction on the nodes belonging to a system. The integer reference value represents the number of the time-series to be used as the portion function for the well at this location. The same time-series ID may be used for more than one well. The values in the time series are expected to be between 0 and 1, and typically would add up to 1 when summing over all extraction or injection nodes of a system (unless water is discharged elsewhere). All other nodes are to be given zero or negative values. "

Hello,

One option for this is the application of gaps in the time series. When there is a gap, no temperature BC will be set. The advantage of the plug-in is that it determines the injection period on its own and thus you do not need to prepare a time series with gaps for the temperature BC. There are different OpenLoop plug-ins: The one called OpenLoop Design that comes with FEFLOW nowadays does much more than what I said (or rather: something different). It can use minimum and maximum injection temperatures, and based on the energy demand of the building it will modulate the flow through the system and give a message when the demand cannot be fulfilled. There's another one called OpenLoop (or maybe SimpleOpenLoop) which takes the extraction temperature, adds a differential (defined in a time series) and uses the result as injection temperature. Each of the plug-ins has a help file that can be accessed via the help entry in the context menu of the plug-in in the corresponding panel. There you can see why it doesn't come up in your case.

I think I'd use polygons for this, splitting the polygon for the diaphragm wall into smaller pieces by using the 'split polygons' tool (once again here, I'd first split them roughly at the right place, then move the node by using F2).

To set nodes at a certain distance, you can have vertices on a line (either imported or set in FEFLOW by clicking on the line  - the trick is then using F2 to fix the coordinates). The danger of your method only using F2 is that FEFLOW might not always recognize that the coordinates you set are exactly on the existing line, thus not subdividing this line and subsequently ending up with a vertex very close to the line. Gridbuilder is in general less tolerant of such conditions than Triangle. Advancing front will not help you as it does not use the lines and points you put at all (only polygons).

The difference is the following:
Internal transfer is the heat flow calculated across the boundaries of the DOI.
Change in storage is the change in the energy content of the volmume within the DOI or related the the selected nodes. So when you have heat leaving the DOI (assuming no sources or sinks in the DOI), there is an INPUT to the model from storage (as the volume cools down it kind of transfers its stored heat to the groundwater)

As you get the zones as volumetric zones, you can use FEFLOW to convert selections in between elements, nodes and faces. By intersecting the selections for different zones you can then get the interfaces for the geometry type you need.