Commit 61bcb0f1 authored by Topi Rasku's avatar Topi Rasku
Browse files

Commenting out a couple *v_startup* and *v_shutdown* limits due to them being...

Commenting out a couple *v_startup* and *v_shutdown* limits due to them being extremely slow, and not strictly necessary.

The removed limits only aim to ensure that no startup and shutdown is performed if the unit online variable horizon doesn't extend far enough to cover the consequences. This is already ill-adviced, but should'nt have a significant impact on the model anyhow.
parent e48ff153
......@@ -245,6 +245,10 @@ v_shutdown.up(unit, sft(s, f, t))${uft_online(unit, f, t)
= p_unit(unit, 'unitCount')
;
// !!! NOTE !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
// The following limits are extremely slow, and shouldn't strictly be required.
// Commenting them out for now at least.
$ontext
// Cannot start a unit if the time when the unit would become online is outside
// the horizon when the unit has an online variable
v_startup.up(unitStarttype(unit, starttype), sft(s, f, t))${ uft_online(unit, f, t)
......@@ -259,7 +263,7 @@ v_shutdown.up(unit, sft(s, f, t))${uft_online(unit, f, t)
and not sum(t_active(t_)${ord(t) = ord(t_) + dt_toShutdown(unit,t_)}, uft_online(unit, f, t_))
}
= 0;
$offtext
//These might speed up, but they should be applied only to the new part of the horizon (should be explored)
*v_startup.l(unitStarttype(unit, starttype), f, t)${uft_online(unit, f, t) and not unit_investLP(unit) } = 0;
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment