Skip to content

Bug when using initial capacities and PeriodLife or RollingLife #53

@JulStraus

Description

@JulStraus

The changes in #49 introduced a bug that occurs when we assume a technology has an initial capacity. In this situation, the upper bound in src/model.jl#L73 is enforcing an unnecessary removal of capacity to be satisfied.

The problem is associated with the difference val_start_cap[t_inv] - val_start_cap[t_inv_prev]. While it was introduced to also allow for variations in the starting capacity, it results in this specific case in problems. A solution would be to track the change in all previous periods as well.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions