For the whole LES, the demand for heat and the different forms of supply need to be shown per time-step

[ChaelKruip]

A chart similar to gas and electricity would be nice. A stack of production combined with a line for demand would be very useful here:

The main categories would be:

• Demand (total demand)
• Production:
  • Heat network (excess heat)
  • Heat network (dispatchable)
  • Decentral production

The decentral production would include all technologies in the households. If possible it would be nice to differentiate between those as well.

[grdw]

I have some questions. How would somebody be able to view these charts? Just by clicking on and end-point? Or is this not connected to an end-point at all and does this need to be on a different page?

Also how are we able to fetch these numbers?

It sounds like the heat demand is one GQL in ETEngine, for production there's some possible extra calculation needed or? (@antw )

[antw]

I'll wait for @ChaelKruip to clarify, but at the moment I don't think there is enough data available to the front-end to be able to make this chart possible. The network calculation is going to have to do more book-keeping to properly record exactly which producers were running when, and how much energy was output.

I'd like to know the answers to @grdw's questions too

[ChaelKruip]

Or is this not connected to an end-point at all and does this need to be on a different page?

Yes. Just like with the gas 'tab', I'd like to have a tab with heat demand/production overview for the whole LES.

The network calculation is going to have to do more book-keeping to properly record exactly which producers were running when, and how much energy was output.

I think we would like to have access to the following curves:

• total space heating demand (adding all scaled profiles for space heating)
• total hot water demand (adding all scaled profiles for space heating)
• the net load of the buffers (can be positive or negative)
• the production of heat by decentralised technologies (heat pumps, combi boilers etc.)
• the production of heat by the must-run part of the heat network
• the production of heat by the dispatchable part of the heat network
• the deficit of heat (if buffers + production does not match demand)

[ChaelKruip]

I present to you probably the ugliest mock-up chart ever: I hope a few things are clear from it though:

• Demand = positive load and stacked
• Supply = negative load and also stacked
• The mismatch between supply and demand is drawn as a production deficit
• Buffers can have positive and negative loads depending on the moment
• We show this in a weekly time-frame

[antw]

I'll work on getting this data out of the network calculation. I'll aim to expose it via a Rails action which responds with JSON something like:

{
    "demand": {
      "hot_water": [1, 2, 3, ..., 672],
      "space_heating": [1, 2, 3, ..., 672]
    }
    "supply": {
      "must_run": [1, 2, 3, ..., 672],
      "dispatchable": [1, 2, 3, ..., 672],
      // local = from endpoints, aka "decentral"
      "local": [1, 2, 3, ..., 672]
    }
    // positive = charging, negative = discharging
    "buffer_load": [1, 2, -3, -4, ..., 672]
}

I think that covers all the bases...

[ChaelKruip]

I think that covers all the bases...

Sounds good!

Thinking about it a bit more, I think it would be great if we could show the sources of the heat network separately if possible:

• central heat network (must-run)
• central heat network (dipatchable)
• heat network (geothermal)
• heat network (gas CHP)
• heat network (biogas CHP)
• heat network (biomass CHP)

[antw]

Thinking about it a bit more, I think it would be great if we could show the sources of the heat network separately if possible:

In which case, instead of must_run and dispatchable "supply" series', we can separate out each technology.

{
    "demand": {
      // maybe these should be buffer_water_heating and buffer_space_heating?
      "water_heating": [1, 2, 3, ..., 672],
      "space_heating": [1, 2, 3, ..., 672]
    }
    "supply": {
      // we can show which are must-run and which are dispatchable using the
      // the legend, labels, and chart colours
      "heat_source_1": [1, 2, 3, ..., 672],
      "heat_source_2": [1, 2, 3, ..., 672],
      "heat_source_3": [1, 2, 3, ..., 672],

      // local = from endpoints, aka "decentral"
      "local": [1, 2, 3, ..., 672]
    }
    // positive = charging, negative = discharging
    "buffer": [1, 2, -3, -4, ..., 672]
}

[ChaelKruip]

Closing as this chart has been merged. Some improvements are listed in https://github.com/quintel/etmoses/issues/1161