Denim Umeshkumar Anajwala

Dear Alessandro, the patch 12 of 5.4 gives correct results, in general. If you say "slight differences" - how large are they in Degree Celsius? Kind regards Wolfram

After all it is the inlet temperature which is specified. If you need a specific heat extraction rate, there is a free IFM module (BHE-Loop) available. Please contact support@dhi-wasy.de, they can send it to you.
Kind regards
Wolfram

Dear Alessandro, you are correct, the average temperature is the outlet temperature. Do you use the most current version of FEFLOW? There was a bug related to this issue in a previous version.

Please contact support@dhi-wasy.de regarding this Exceed problem. It occurs from time to time and there is a specific procedure available to fix it.

http://feflow.info/forum/index.php/topic,770.0.html

Hello,
you have two options in the BHE dialog: either define an Input Heat Rate for which an equivalent Inlet Temperature (see bottom of the dialog) is computed; or you can insert an Inlet Temperature and calculate an equivalent Heat Input Rate.
In both cases the respective value is calculated using the reference Temperature, i.e.:

T_inlet = [Heat Input Rate] / ([Volumetric Heat Capacity] * [Flow Discharge]) + [Reference Temperature]

In case you use an Inlet Temperature equal to the Reference Temperature the Heat Input Rate is zero.

The Heat Input Rate of an BHE is different to the Heat Input Rate of a regular 4th kind heat boundary condition (BC). The real heat input (balance) of an BHE is the result of the subsequent computation while for a regular 4th  kind BC it is exactly this value.

In most cases it is a good idea to use a reference temperature which is smaller than any temperature occurring in your model. Zero can be a good choice or maybe 273.15 (absolute zero).

Actually you could use also very large numbers. However due to this (some) signs while change (i.e. for the Budget calculations) which can make understanding the results hard.

Kind regards
Wolfram

Unfortunately this is not possible yet, but it is on the 'to-do' list.

I have no experience with Dev-C++, but probably you'd have to compile the IFM project separately, and then link to the IFM library from the IFM module project. We used to do this in Visual Studio, too, but having both projects has the big advantage that Microsofts IntelliSense works fine, i.e., you get information about the arguments of all IFM functions when writing them etc.
Note that you do not have to use the full version of Visual Studio - the free Express edition is usually sufficient for IFM projects that do not need sophisticated code optimization.

Hi Kelly,
this is not yet available publicly, but we have done such kinds of things in consulting and in research projects, also focusing on parallel processing and grid/cluster computing.

Peter

The built-in version does both steady-state and transient calibration. In the latter case, it does not care how many snapshots you have in time, but of course the model has to be run for the full period for each iteration.
Alternatively, you can use PEST as a stand-alone software calling FEFLOW, of course.