This PR introduces a fresh approach to the preprocessing to improve readability and usability of the code. It takes some ideas for postprocessing developed in oemof_heat.
Here is an overview of the quantities that should be computed by postprocessing with some notes on what steps are necessary.
[x] summed flows
temporal sum of flows
[x] summed flows of a subset (e.g. renewables)
temporal sum of flows and technological or sectoral subset sum
[x] storage losses
difference of temporal sum of flows in and flows out of storage.
[x] transmission losses
differene of temporal sum of flow in and flow out of link
[x] capacity
params.nominal_value or for facades the capacity attribute
[x] capacity invest
results scalars invest
[x] storage_capacity
params storage capacity or for facades the storage capacity attribute
[ ] marginal_cost
map marginal cost to the right flow, then multiply by temporal sum
[ ] carrier_cost
map carrier cost to the right flow, then multiply by temporal sum
[ ] emissions
emissions can be set to a flow of the ES. Then, take it from the params and multiply by the flow
could also introduce Commodities and set emissions and emission costs on them
But you may want to attribute emissions to the technology, which you couldn't in that way.
[ ] emission cost
emissions times spec_emissions_cost
This PR introduces a fresh approach to the preprocessing to improve readability and usability of the code. It takes some ideas for postprocessing developed in oemof_heat.
Here is an overview of the quantities that should be computed by postprocessing with some notes on what steps are necessary.