multi-vector-simulator icon indicating copy to clipboard operation
multi-vector-simulator copied to clipboard

Transformer objects describing in/out of a bus should be connected

Open smartie2076 opened this issue 6 years ago • 6 comments

Ie. the data input should be more effective in json, compared to the current

"storage_charge_controller_in": {
        "age_installed": {"value": 0.0, "unit": "year"},
        "installedCap": {"value": 0.0, "unit": "kW"},
        "capex_fix": {"value": 0.0, "unit": "currency"},
        "capex_var": {"value": 0.0, "unit": "currency/kW"},
        "efficiency": {"value": 1, "unit": "factor"},
        "label": "Charge Contoller ESS Li-Ion (charge)",
        "lifetime": {"value": 10, "unit": "year"},
        "opex_fix": {"value": 0.0, "unit": "currency/kW/year"},
        "opex_var": {"value": 0.0, "unit": "currency/kWh"},
        "outflow_direction": "ESS Li-Ion",
        "optimizeCap": true,
        "inflow_direction": "Electricity (LES)",
        "type_oemof": "transformer"
        },
    "storage_charge_controller_out": {
        "age_installed": {"value": 0.0, "unit": "year"},
        "installedCap": {"value": 0.0, "unit": "kW"},
        "capex_fix": {"value": 0.0, "unit": "currency"},
        "capex_var": {"value": 0.0, "unit": "currency/kW"},
        "efficiency": {"value": 1, "unit": "factor"},
        "label": "Charge Contoller ESS Li-Ion (discharge)",
        "lifetime": {"value": 10, "unit": "year"},
        "opex_fix": {"value": 0.0, "unit": "currency/kW/year"},
        "opex_var": {"value": 0.0, "unit": "currency/kWh"},
        "inflow_direction": "ESS Li-Ion",
        "optimizeCap": true,
        "outflow_direction": "Electricity (LES)",
        "type_oemof": "transformer"
        }

This could be done with an additional parameter "twins", which then copies the a general entry "storage_charge_controller" into "storage_charge_controller_out"/"storage_charge_controller_in".

The optimized capacities should be linked with a constraint, at least on request.

smartie2076 avatar Nov 01 '19 09:11 smartie2076

Constraint discussed in #133

smartie2076 avatar Feb 26 '20 10:02 smartie2076

@smartie2076 I moved this issue to "Late Issues" as now it's working (give higher prio to bugs and necessary enhancements)

SabineHaas avatar Jun 10 '20 10:06 SabineHaas

Hi @SabineHaas ! We can go for that for now, true. As soon as we have to optimize a bi-directional transformer though, we need to come back to this issue.

smartie2076 avatar Jun 10 '20 18:06 smartie2076

@ursulaelmir this task refers to connecting inverter+rectifier into a bi-directional inverter. Whats your prio on this?

smartie2076 avatar Jul 13 '20 12:07 smartie2076

To-dos:

  • [ ] Think of a way to define that two transformers are connected - either in constraints.csv or as an additional field in the energyConversion.csv
  • [ ] document the solution and constraint in the RTD
  • [ ] Implement the solution
  • [ ] write a pyomo constraint to facilitate the bounds in the oemof simulation
  • [ ] write a benchmark test for the function

smartie2076 avatar Nov 06 '20 23:11 smartie2076

I might have found an inbuild-functionality to connect two inverter assets: https://oemof-solph.readthedocs.io/en/latest/usage.html#adding-additional-constraints

Coupling of two variables e.g. investment variables) with a factor -> equate_variables()

Also see here and here (Code).

smartie2076 avatar Mar 29 '21 12:03 smartie2076