diff --git a/docs/manual/loadflow_configuration.md b/docs/manual/loadflow_configuration.md index e0dbd302ef2f3ff587f472bdc86953eb0f305882..ff7e0ab77d3decaa5d321b02431e72567e8858b3 100644 --- a/docs/manual/loadflow_configuration.md +++ b/docs/manual/loadflow_configuration.md @@ -37,7 +37,7 @@ with the following input parameters: | lp_inputcolumn | Name of the column in the input file that contains the heat load data | - | string | Heat load data in unit kW; Optional; only used if `lp_type` is FROMFILE | | lp_smoothing | Type of smoothing applied to the load data | — | string | Options: D (daily), M (monthly), Y (yearly). Optional; only used if `lp_type` is FROMFILE | | lp_scale | Scaling factor applied to the load values | — | scalar | Scaling factor for the load profile. Optional; only used if `lp_type` is FROMFILE | -| lp_minscaleflow | Minimum scaling factor for flow | - | scalar | To avoid very lowe flowrates affecting numerical performance. Optional; only used if `lp_type` is FROMFILE or VARIABLE | +| lp_minscaleflow | Minimum scaling factor for flow rate | - | scalar | To avoid very lowe flowrates affecting numerical performance. Optional; only used if `lp_type` is FROMFILE or VARIABLE | | lp_minQ | Minimum heat demand (absolute) | - | scalar | Below lo_minQ the heat demand is set to 0 to avoid numerical performance issues. Optional; only used if `lp_type` is FROMFILE | | lp_peak | Peak heat load | W | scalar | Optional; only used if `lp_type` is VARIABLE | | lp_base | Base heat load | W | scalar | Optional; only used if `lp_type` is VARIABLE | @@ -101,11 +101,15 @@ represents the dwelling equivalent (DE) of power. I.e. the heat load is increase > **_NOTE:_** To apply a smoothing factor to the pre-defined heat load or flow rate profile, a column named "local_time" is required > in the input CSV file, that includes the timestamps for the data column. -For a pre-defined heat load profile or a variable heat load following a cosine pattern, the flow rate in the main model -configuration (`m_flow`) is automatically scaled such that the ratio of the -required pumping power to the generated power (or the COP of the -fluid circulation pump) is constant. Here, `m_flow` defines the maximum value in the scaled flow rate profile. To ensure numerical -stability, also the minimum allowed scaling factor for the flow rate is defined in `lp_minscaleflow`. +For a predefined or analytically generated heat load profile (e.g., cosine-based), the flow rate is scaled proportionally +to the instantaneous heat load. The parameter `m_flow` represents the maximum flow rate, which is reached when the absolute +heat load is at its peak. + +At each time step, the flow rate is computed by normalizing the absolute heat load with respect to its maximum value and +multiplying it by `m_flow`. This results in a flow rate profile that follows the magnitude of the load. + +To avoid unrealistically low or zero flow rates, a minimum scaling factor is enforced via `lp_minscaleflow`. As a result, +the flow rate never drops below `lp_minscaleflow * m_flow`. > Heat load profiles can represent heating, cooling, or variable operation modes. diff --git a/pyproject.toml b/pyproject.toml index 9eb18e2a3e47d93b881786a4e6d05ed157da4fc3..b586f5378bd377cd3773f662f80b133afb4ba369 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta" [project] name = "geoloop" -version = "1.0.6" +version = "1.0.7" description = "This is a Python package for simulation of (deep) vertical Borehole Heat Exchanger (BHE) systems" authors = [ { name = "Zanne Korevaar", email = "zanne.korevaar@tno.nl" },