Costs data export should be restructured

[mabijkerk]

PR https://github.com/quintel/etengine/pull/1323 fixed erroneous results in the costs data export (which is generated with this serializer). The fixes in the PR ensured that the results from the data export aligned with the results shown in the costs charts in the ETM frontend.

The PR included a minor improvement in the structure of the export. The structure is still rather unclear, so further improvements should be made:

• [ ] enhancement - The "Total ex ccs (Euro)" column is not intuitive: it contains group and subgroup totals, but sometimes specific queries are included as well, for example in gas_network_total_costs. Preferably the data export would be structured in a way that facilitates easy replication of the costs charts in the ETM frontend through pivot tables
• [ ] necessary to fix - The "Total ex ccs (Euro)" column is not actually entirely without CCS: the rows for costs_co2 include all CCS costs from the other groups in the "Total ex ccs (Euro)" column. These are the costs that are shown in the rows "CAPEX ccs (Euro)" and "OPEX ccs (Euro)". For all other rows in "Total ex ccs (Euro)", these CCS costs are indeed excluded.
• [ ] enhancement - Some subgroups only have subgroup totals and no specific rows, for example the costs_carriers
• [ ] enhancement - Some subgroups only have specific rows and no subgroup totals, for example the costs_infrastructure
• [ ] enhancement - A short guide for interpretation of the data export would be useful to add to the ETM frontend slide
• [ ] enhancement - The subgroup storage is not intuitive: it does not include p2p, even though p2p is a form of storage
• [ ] enhancement - Add present year costs to data export

Notifying @DorinevanderVlies in case I've missed additional potential improvements.

[mabijkerk]

For reference, see this mapping of the II3050 European governance scenario: Kosten - mapping van export naar grafieken (II3050 EUR).xlsx

[github-actions[bot]]

This issue has had no activity for 60 days and will be closed in 7 days. Removing the "Stale" label or posting a comment will prevent it from being closed automatically. You can also add the "Pinned" label to ensure it isn't marked as stale in the future.

[github-actions[bot]]

This issue has had no activity for 60 days and will be closed in 7 days. Removing the "Stale" label or posting a comment will prevent it from being closed automatically. You can also add the "Pinned" label to ensure it isn't marked as stale in the future.

[mabijkerk]

@KoenvanB can this issue be closed?

[KoenvanB]

Yes, it can be closed. The costs download has undergone a complete overhaul during the pilot for FIT project, so most improvement suggestions have become moot.