<a class="user-mention notranslate" data-hovercard-type="user" data-hover

Plotting functionality should join `historical_activity` to `ACT` about message_ix HOT 1 OPEN

glatterf42 commented on June 24, 2024

Plotting functionality should join `historical_activity` to `ACT`

from message_ix.

khaeru commented on June 24, 2024

I think we could actually make several such enhancements. For example, the default reporting config includes:

Line 64 in 7dce461

("emi", "mul", "emission_factor", "ACT"),

…but there is also a parameter:

Line 433 in 7dce461

par("historical_emission", "n type_emission type_tec type_year")

We can try to do concatenation wherever there are such pairs.

I say ‘try’ because some issues may come up:

In some cases the dimensionality of the historical_* parameter is mismatched with the product of 1+ variables and 0+ parameters to which it supposedly corresponds. This is true in the case above.
message_ix_models.report.legacy has a parameter merge_hist, which triggers concatenation of IAMC-structured time series data for pre-model periods with computed values for model periods. This points us to the possibility that a user populates both these historical time series data and the historical_* parameters with potentially different values. What should the reporting do in such cases?

from message_ix.