Display *availability* in merit order graph?

[Richard-Deuchler]

When testing the merit order, I am often lured into thinking that the installed capacity of wind is always available. For coal it might be fair to assume that the installed capacity is always ready to contribute to production, but this is clearly not the case for wind/solar.

In order to understand this, one needs to look at the full load hours in the merit order table. Even then it might be unclear to the user, whether the full load hours are limited because of availability constraints or because of the "shape of demand/supply curves".

Maybe, we can add the availability to the merit order graph / mouseover?

[ChaelKruip]

I think it is not a bad idea. Not very urgent though. @AlexanderWirtz what do you think?

[AlexanderWirtz]

Awesome idea. No idea how hard it is to implement. not urgent

[ChaelKruip]

I don't think this is urgent but I think it is easy right @paozac ?

Assigning this to @paozac

[pzac]

Well this requires creating 15 extra gqueries... Otherwise I can change the chart and just use a single nested gquery, like this one:

https://github.com/quintel/etsource/blob/master/gqueries/output_elements/dashboard/dashboard_profitability.gql

The new gquery should return capacity, operating costs and the new availability. The good thing about this approach is that the chart would just need a single gquery (instead of 30 or 45); the bad thing is that such a query would be very specific and not recyclable, since it would return a hash rather than a scalar value. Let me know what you prefer.

[ChaelKruip]

I prefer separate queries for the moment. These are 'single-purpose' and 'recyclable'. We have several charts with many more queries so, the 'number of queries argument' is not very strong in my opinion.

@dennisschoenmakers what do you think?

[dennisquintel]

@dennisschoenmakers what do you think?

I think you can make this decision. :smile: It's all good to me.

[ChaelKruip]

Ok, @paozac can you make this happen?

[pzac]

Done with https://github.com/quintel/etmodel/commit/acef459b8d6b04af9aead0c03b45c69cfd967771 and https://github.com/quintel/etsource/commit/037ab06b4524091c31ec83d4f343336ab3c80465

[Richard-Deuchler]

it works like a charm. Unfortunately, it does not display the information that I hoped for. The current implementation does not tell me that wind is an unreliable resource. Its availability is almost the same as for every other participant (in fact, even higher than nuclear). @ChaelKruip , could you make a decision on what to display here? "Maximum" full load hours? A load factor? capacity factor ?

[ChaelKruip]

Changed queries to calculate load factor (full_load_hours/8760) instead of availability with this commit. Changed the chart with this commit.