Collective Issue for Time-Slice Implementation

[Wegatriespython]

What is this about?

The exact level of support for the time-slice implementation is unclear at the moment.

For examples issue #191 is still open. #348 could be related as well.

Not yet filing as bug as its ambiguous whether this is user error. In either case would be helpful to note till more clarity is reached.

At present there is at least one issue :

Before timeslicing:
Parent: output(time="year") -> creates ACT(parent, year)
Addon: output(time="year") -> creates ACT(addon, year)
addon_conversion(time="year") = 1.0
Constraint: ACT(addon, year) <= 1.0 * ACT(parent, year) =>Works

After timeslicing parent:
Parent: output(time="h1"), output(time="h2") -> creates ACT(parent, h1), ACT(parent, h2)
Parent: NO output(time="year") -> NO ACT(parent, year)
Addon: output(time="year") -> creates ACT(addon, year)
addon_conversion(time="year") = 1.0
Constraint: ACT(addon, year) <= 1.0 * sum(ACT(parent, year) where map_tec_act exists)
<= 1.0 * 0 (empty sum)
<= 0
Demand forces ACT(addon, year) > 0 → INFEASIBLE