fix: Compare impacts by subimpacts and run the comparison during export

[ccomb]

🔧 Problem

The current comparison graphs don't display useful informations, the impacts seem the same across all sub-impacts

The comparison is a separate command and is not always launched during export. It is not included in the npm commands and may end up being abandonned.

🍰 Solution

• Refactor the export to also run the comparison graphs
• Fix the graphs to display sub-impacts
• use only normalization in comparison graphs

🏝️ How to test

Run the export (make export / npm run export:all) and check there are comparison graphs.
Check that the export still run if simapro is not available.

[paulboosz]

How can I check with simapro unavailable ?

[ccomb]

How can I check with simapro unavailable ?

You connect to the simapro machine and stop the API then relaunch an export.
You should get n output like:

2025-02-13T15:37:49.764259+0100 INFO 51/86: getting impacts from Brightway for: electricity, medium voltage//[ET] market for electricity, medium voltage
2025-02-13T15:37:50.183820+0100 INFO 52/86: getting impacts from SimaPro for: electricity, medium voltage//[KH] market for electricity, medium voltage
2025-02-13T15:37:52.201775+0100 WARNING SimaPro did not answer! Is it started?
2025-02-13T15:37:52.202202+0100 WARNING SimaPro FAILED: {}

[paulboosz]

LGTM :)

[vjousse]

I think we should use functions when we can to avoid code duplication. And what about adding an option to generate the graphs or to disable their generation?

[ccomb]

And what about adding an option to generate the graphs or to disable their generation?

Good idea, I've added an option to an internal function, and exported this option to the output process. So now the plot are generated when running for instance npm run export:textile -- --plot