You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, there are different code paths for upfront invest and multi-period invest, we should make upfront invest a special case of the multi-period invest, where only one investment period exists. To do so, there are several steps:
Some thoughts about this (partly from discussion with @jokochems):
VDI2067 lists capital-related costs, demand-related costs, and operation-related costs (plus other costs).
In solph, the ep_costs of an investment translate to the capital-related costs. The other costs are not so easy to distinguish: Both demand-related costs and operation-related costs can be attributed to flows (or, esp. storage content).
Still, to keep at least the CAPEX distinct, it might make sense having "fixed costs" as operation-related costs that cannot be avoided once an investment has been made.
We could drop the fixed costs (again) an just have energy-related costs (€/kWh/a) and capacity related costs (€/kW/a).
The current multi-period optimisation allows to have gaps between the displayed periods, but does not care about transitions. This particularly means that e.g. a battery storage might be emptied in the end of 2020 as recharging is cheap in 2030 (the next period). There are ways to tackle this, but for the moment I'd just assume continuous time.
As the TIMESTEPS and TIMEPOINTS are unique, it is possible to completely drop the period index and instead map from the main index to the period.
The mapping might happen globally (global periods), similar to the way it is done right now.
Or every investment can get a point in time as a local parameter.
Currently, there are different code paths for upfront invest and multi-period invest, we should make upfront invest a special case of the multi-period invest, where only one investment period exists. To do so, there are several steps:
The text was updated successfully, but these errors were encountered: