ITR_UI.py version 2.0 needed

[MichaelTiemannOSC]

One of the consequences of the templates-v2-scopes branch is that the tool's handling of scopes has changed. In the past, the tool required the user to stipulate for some operations (such as calculation of temperature scores) which scopes the user wanted to use for calculations. In other cases, the interface allowed the user to pick a single scope for a given operation. But in all cases, the tool never considered the possibility that a given set of scopes may or may not be available on a sector-by-sector basis, nor did it consider that the users themselves may not be aware of what scopes a given benchmark covers or does not cover on a sectoral and regional basis.

In the templates-v2-scopes branch, the tool now uses the convention that when scopes=None, it means "calculate for all scopes covered by the benchmark", which means that a list of N companies could return more than N rows of data (for OECM, a lot more). There are two cases the GUI should fundamentally handle (which may require further changes to the underlying tool code):

1. Displaying the results of the "most complete" scope calculation. In this case, when the tool returns multiple rows of scope data, the GUI will select the one row that covers the temperature score most completely. In the case of TPI benchmarks, this will typically be the combined scopes for which the benchmark is defined (Scope 1 for Electricity Utilities, Scopes 1 and 2 for Steel, Scope 3 for Autos, etc). In the case of OECM, it will be S1+S2+S3 for the normal case and S1+S2 for the "production-centric" case. All other scopes returned will not be displayed.
2. Displaying the results as a "composite". In this case, when a company's temperature score is displayed (such as when they are among the top 4 emitters in their sector), the ITR metric will be shown as a stacked chart, making it possible to see how much each scope the benchmark uses contributors to the overall ITR score. In the case of TPI benchmarks that measure only a single scope, only that scope will be displayed (with some characteristic graphical styling of each scope). In the case of OECM, Scopes 1, 2, and 3 (or Scopes 1 and 2 for production-centric) will be styled and stacked. Because the "neutral" temperature score is non-zero, some math is needed so that we don't get the nonsense that a 1.5C-aligned S1+S2+S3 is somehow +4.5C. The math is simple: if S1+S2+S3 is delta_X, then the stacking size of each is weighted as delta_X * Si / (S1+S2+S3) for i in 1, 2, 3.

[alexanu]

Hi, Michael, I will try to find time for this

[MichaelTiemannOSC]

Substantial progress has just been checked in on the template-v2-scopes branch: https://github.com/MichaelTiemannOSC/ITR/blob/template-v2-scopes/examples/ITR_UI.py