Imbalance in graph values RS_serbia due to decimal rounding issue

[kndehaan]

When exporting the RS_serbia dataset from ETLocal to ETSource, the parent shares of the following edges are determined through sparse graph queries:

• industry_final_demand_for_metal_network_gas-industry_final_demand_for_metal_aluminium_network_gas@network_gas
• industry_final_demand_for_metal_network_gas-industry_final_demand_for_metal_steel_network_gas@network_gas

The determined values are however not in balance:

industry_final_demand_for_metal_network_gas-industry_final_demand_for_metal_aluminium_network_gas@network_gas:
  parent_share: 0.11863428388165434
industry_final_demand_for_metal_network_gas-industry_final_demand_for_metal_steel_network_gas@network_gas:
  parent_share: 0.8813657161183456

Summed value = 0.99999999999999994

The first calculated parent share is rounded to 17 decimals, the second to 16 decimals. It's not clear to me why the second one is rounded to one less decimal. For now, we've manually corrected the second one to 17 decimals (changed to 0.88136571611834566), so that the shares add up to 1.0. Otherwise, the dataset won't load.

But every time the dataset is exported to ETSource, we need to be aware that this value is not changed back. We cannot do a quick fix in the dataset values since these shares are calculated based on EB values.

Next steps
I see some questions / follow up steps:

• Why does the second parent share round to less decimals? This seems to cause the imbalance
• Improve rounding of decimals method, less decimals would be preferred and in a way that the imbalance would not occur
• Alternatively, could we change the sparse graph queries to ensure that the values are balanced?

[kaskranenburgQ]

While exporting the 2023 datasets from ETLocal to ETSource this same occured for the following datasets:

• PV_27_noord_holland
• GM0794_helmond
• ES16_noord_holland_zuid
• ES30_zuid_limburg
• ES28_west_brabant

[kndehaan]

It seems that this is becomin a bigger issue now, since we'll encounter this issue everytime we want to export datasets. I put this up the dev sprint board and will add this to the agenda of the M&D meeting. Notifying @mabijkerk and @noracato

[kndehaan]

Look together with @noracato at this issue, find out where this problem occurs. Suggestions: consider DIVIDE(), alter SGQ 1- shares, etc.