From 54fac89ca62809f6693560f433d9edd5b1ce979f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Patrik=20Sch=C3=B6nfeldt?= Date: Mon, 23 Oct 2023 09:24:42 +0200 Subject: [PATCH] Speak of time steps in minimum "time" constraints The constraints are actually defined in time steps. (The documentation asked for integers before, so it could be seen from the context.) --- src/oemof/solph/_options.py | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/src/oemof/solph/_options.py b/src/oemof/solph/_options.py index 42bf15885..b57c153d6 100644 --- a/src/oemof/solph/_options.py +++ b/src/oemof/solph/_options.py @@ -185,13 +185,13 @@ class NonConvex: inactivity_costs : numeric (iterable or scalar) Costs associated with not operating the flow. minimum_uptime : numeric (1 or positive integer) - Minimum time that a flow must be greater then its minimum flow after - startup. Be aware that minimum up and downtimes can contradict each - other and may lead to infeasible problems. + Minimum number of time steps that a flow must be greater then its + minimum flow after startup. Be aware that minimum up and downtimes + can contradict each other and may lead to infeasible problems. minimum_downtime : numeric (1 or positive integer) - Minimum time a flow is forced to zero after shutting down. - Be aware that minimum up and downtimes can contradict each - other and may to infeasible problems. + Minimum number of time steps a flow is forced to zero after + shutting down. Be aware that minimum up and downtimes can + contradict each other and may to infeasible problems. maximum_startups : numeric (0 or positive integer) Maximum number of start-ups in the optimization timeframe. maximum_shutdowns : numeric (0 or positive integer)