Lossy Bidirectional Links #1192

Eric-Nitschke · 2024-11-14T12:19:21Z

Summary:

fixed an existing bug regarding bidirectional lossy links that affected hydrogen pipelines.
the fix primarily utilizes code already in use by PyPSA-Eur.

Changes:

added a function to scripts/add_extra_components.py that "splits" bidirectional links into two unidirectional links. This is based upon the similar PyPSA-Eur implementation, which is slightly more advanced to accommodate PyPSA-Eurs more advanced efficiency calculations.
added a function to scripts/solve_network.py that adds an additional constraint to the network, which ensures that both unidirectional links share the same nominal power. This is a modified version of the PyPSA-Eur function, as PyPSA-Eur uses linopy while the base PyPSA-Earth version operates on lopf.

Reason:

without this commit, lossy bidirectional links are able to "generate" power by operating at a negative power level.
this stems from the general link implementation, which applies p1 = -eta*p0 to links, regardless whether power flows from bus0 to bus1 or from bus1 to bus0.
the current hydrogen pipeline implementation adds them to the network as lossy bidirectional links and is thus able to "generate" hydrogen.
this might affect other lossy bidirectional components added by the sector network as well.

Checklist

I consent to the release of this PR's code under the AGPLv3 license and non-code contributions under CC0-1.0 and CC-BY-4.0.
I tested my contribution locally and it seems to work fine.
Code and workflow changes are sufficiently documented.
Newly introduced dependencies are added to envs/environment.yaml and doc/requirements.txt.
Changes in configuration options are added in all of config.default.yaml and config.tutorial.yaml.
Add a test config or line additions to test/ (note tests are changing the config.tutorial.yaml)
Changes in configuration options are also documented in doc/configtables/*.csv and line references are adjusted in doc/configuration.rst and doc/tutorial.rst.
A note for the release notes doc/release_notes.rst is amended in the format of previous release notes, including reference to the requested PR.

Summary: - fixed an existing bug regarding bidirectional lossy links that affected hydrogen pipelines. - the fix primarily utilizes code already in use by PyPSA-Eur. Changes: - added a function to scripts/add_extra_components.py that "splits" bidirectional links into two unidirectional links. This is based upon the similar PyPSA-Eur implementation, which is slightly more advanced to accommodate PyPSA-Eurs more advanced efficiency calculations. - added a function to scripts/solve_network.py that adds an additional constraint to the network, which ensures that both unidirectional links share the same nominal power. This is a modified version of the PyPSA-Eur function, as PyPSA-Eur uses linopy while the base PyPSA-Earth version operates on lopf. Reason: - without this commit, lossy bidirectional links are able to "generate" power by operating at a negative power level. - this stems from the general link implementation, which applies p1 = -eta*p0 to links, regardless whether power flows from bus0 to bus1 or from bus1 to bus0. - the current hydrogen pipeline implementation adds them to the network as lossy bidirectional links and is thus able to "generate" hydrogen. - this might affect other lossy bidirectional components added by the sector network as well.

for more information, see https://pre-commit.ci

davide-f · 2024-11-15T00:11:12Z

Many thanks @Eric-Nitschke :D That's a quite neat application!
Would you like to add a release note?

Changes: - add a describtion of this pull request to the release_notes.rst

Eric-Nitschke · 2024-11-18T17:14:14Z

@davide-f Thanks :)
I've added a relase note to the pull request!

- correct spelling mistakes in doc/release_notes.rst

ekatef

Hello @Eric-Nitschke, thanks a lot for investigating the issue and contributing the fix!

Have added some technical comments mainly aimed at better understanding and maintainability improvements. I recognise that the PR follows PyPSA-Eur implementation which is more or less state-of-the-art, but it would be definitely great to have deeper understanding of possible further improvements on some weak points. Your insights in this regard would be very helpful.

Personally, I think that this PR can be probably merged as-is as it feels like a much needed bug-fix. It would be great to have a review of @Eddy-JV who has been working on implementing similar solutions in PyPSA-Eur and definitely has a better overview

ekatef · 2024-12-03T10:37:04Z

README.md

-            <td align="center">
-                <a href="https://github.com/euronion">
-                    <img src="https://avatars.githubusercontent.com/u/42553970?v=4" width="100;" alt="euronion"/>
-                    <br />
-                    <sub><b>Euronion</b></sub>
-                </a>
-            </td>
-            <td align="center">
-                <a href="https://github.com/Justus-coded">
-                    <img src="https://avatars.githubusercontent.com/u/44394641?v=4" width="100;" alt="Justus-coded"/>
-                    <br />
-                    <sub><b>Justus Ilemobayo</b></sub>
-                </a>
-            </td>
-            <td align="center">
-                <a href="https://github.com/mnm-matin">
-                    <img src="https://avatars.githubusercontent.com/u/45293386?v=4" width="100;" alt="mnm-matin"/>


I guess those are changes from an automated run of github workflow? 😄 Don't think we need them in the PR. Could you please remove them?

The recent PR #1210 changes a mode of the automated updates of the contributors list to a pre-scheduled one. So we don't loose track of contributions but PRs won't have those irrelevant additions anymore.

doc/release_notes.rst

ekatef · 2024-12-03T11:55:12Z

scripts/add_extra_components.py

+
+    "Split bidirectional links into two unidirectional links to include transmission losses."


Usually, we are using """ to write docstrings

scripts/solve_network.py

Eddy-JV

Thank you @Eric-Nitschke for this very important contribution.

I took the liberty to add some comments in order to cover this PR #1192 as well as PR #1215 and Issue #1213 at once. Feel free to discuss, if you think things can be done differently. Thanks again for the great work.

Eddy-JV · 2024-12-03T13:01:14Z

README.md

-            <td align="center">
-                <a href="https://github.com/euronion">
-                    <img src="https://avatars.githubusercontent.com/u/42553970?v=4" width="100;" alt="euronion"/>
-                    <br />
-                    <sub><b>Euronion</b></sub>
-                </a>
-            </td>
-            <td align="center">
-                <a href="https://github.com/Justus-coded">
-                    <img src="https://avatars.githubusercontent.com/u/44394641?v=4" width="100;" alt="Justus-coded"/>
-                    <br />
-                    <sub><b>Justus Ilemobayo</b></sub>
-                </a>
-            </td>
-            <td align="center">
-                <a href="https://github.com/mnm-matin">
-                    <img src="https://avatars.githubusercontent.com/u/45293386?v=4" width="100;" alt="mnm-matin"/>


scripts/add_extra_components.py

scripts/solve_network.py

ekatef · 2024-12-11T12:30:00Z

Hello @Eric-Nitschke and @Eddy-JV! Great work on reviewing the PR.

@Eric-Nitschke do you need any support in revisions? If they look heavy, could it make sense to breakdown the task? That is a precious contribution, and it would be great to have it merged into the model 🙂

Eric-Nitschke · 2024-12-13T12:42:02Z

Eddy-JV · 2024-12-15T11:31:51Z

This reverts commit 1a98c9f.

* Update CI * Change contrib job weekly * Update environment: ppl and atlite * Update pinned files * Reset ci cache * Revise vresutils pinned * Add release_note (cherry picked from commit 114a953)

…onal_lossy_links

ekatef · 2024-12-28T09:49:41Z

Hello 😄
Just wanted to ask if any support may be needed 🙂

@Eric-Nitschke thanks a lot for all the responses and creating a check-list, thank you so much @Eddy-JV for the in-depth review and providing insights into the architecture 🙏🏽

I wonder what is the plan to proceed? @Eric-Nitschke I see that you have ticked the boxes but it appears that the changes have not been pushed to github. Do you experience any issues with git? [I have no ideas why but git is normally provides you with a lot of surprises when you start working in a repo] Happy to assist in resolving them if needed. Also, I see that there are some conflicts with the main. They result from come changes we introduced recently inside main and can be resolved relatively easily. Let me know if any hints on that would be helpful

@Eddy-JV on the architectural level, I understand the idea is to polish the pipelines representation to a level when the model is truly realistic. Though, I have a feeling that the work needed may be considerable. @Eric-Nitschke do you see how to proceed with the advanced implementation proposed by @Eddy-JV? May be any break-down helpful?

Major changes: - Fix bidirectional lossy links by splitting the into to links in _helpers.py - Add length based efficiency calculations in _helpers.py

Eric-Nitschke · 2025-01-02T08:32:14Z

Hey @ekatef,

I had some issues with testing the changes I made since I wasn't at my usual setup and I didn't want to merge untestes changes into the pull request. However you can find the changes I made in a sperate branch here: https://github.com/Eric-Nitschke/pypsa-earth-bidirectional_lossy_links/tree/lossy_length_based

Bug fixes: - modify the override component location provided in the Snakefile to work with the "copy-minimal" shadow directory on Windows - fix the identification of all forward links in scripts/solve_network.py

…idirectional_lossy_links" This reverts commit 45fdc2b, reversing changes made to 80aee27.

Eric-Nitschke · 2025-01-02T15:37:28Z

Hey @ekatef, hey @Eddy-JV,
I've now run some tests and merged the result with the pull request.
Using the override_components function from _helpers required some changes, as on Windows solve_networks uses a "copy-minimal" shadow repository to avoid administration issues. As a result the shadow directory does not have access to the files in the override_components file. I've resolved this by telling it explicitely where to look with "os.getcwd()" when using Windows.
Could you maybe check, if this doesn't have any negative implications on other operating systems?

Aside from this, I'll remove the merge conflicts and then everything should be good to go!

Minor changes: - move the transmission efficiency of the H2 pipelines to the one of the transmission grid, which was added with the last merge.

for more information, see https://pre-commit.ci

…onal_lossy_links

Eric-Nitschke · 2025-01-02T17:04:27Z

As I've mentioned during the discord call:
Between the creation of this pull request and now, PR #1221 added transmission efficiencies to the config for the energy distribution grid. Initially I thought we should modify the use of this in efficiency in prepare_sector_network.py to use the length based efficiency calculation introduced here as well. However, after checking now, I don't think it is nesseccary, as the energy distribution network only uses static efficiencies and not length based ones.

ekatef

Hello @Eric-Nitschke @Eddy-JV, thank you for a fantastic collaborative work!

@Eric-Nitschke I see that you have implemented the massive improvements, and they look very good to me. Have added two rather minor comments comments which relate to the integration of the contribution into the codebase. Another point is CI which is currently complaining about /data/override_component_attrs missed. Do you have any ideas how to fix that?

On the side of the domain-related functionality, @Eddy-JV could you please take a look? Given your expert knowledge on H2 systems, it would be perfect to have your review. My personal impression is that we are closing to finalise 🙂

ekatef · 2025-01-09T09:25:41Z

Snakefile

+                if os.name == "nt"
+                else "/data/override_component_attrs"
+            ),
+            # on Windows os.getcwd() is required because of the "copy-minimal" shadow directory


Just to be sure I get this point properly: is shadow directory the one which is created by the solver to store the temporary files? I wonder if this behaviour may also depend on a solver...

Regarding the files management, it has been found previously that os.getcwd( ) may lead to some troubles if pypsa-earth model is being used as snakemake submodule. In particular #1137 has fixed this replacing os.getcwd( ) by a custom directory path. May it be a way to go also in our case?

In short:
The shadow directory is a Snakemake thing and not solver related.

With the "shadow" rule Snakemake creates an isolated temporary directory, in which it runs the corresponding rule (in this case "solve_network"). With shadow: "shallow", Snakemake symlinks all top level files and directory so that all relative file paths provided will still reach the right directories. However with shadow: "copy-minimal", the inputs of the rule are copied instead of symlinked. In my tests this led to Snakemake not having access to the files within the "data/override_component_attrs" folder. My guess is, that copy minimal only copies files directly, but not the content of directories. PR #790 is the reason, why "copy-minimal" is needed on Windows.

You can check the Snakemake documentation for more details, though it is not that extensive.

However, I think I found the issue:
else "/data/override_component_attrs" should be
else "data/override_component_attrs"

Generally, itmight be nice to move away from os.getcwd() to the changes in #1137. However, I am not confident in implementing these changes myself.

@davide-f This definitely needs your attention as you already made PR #790. And @Eric-Nitschke if this approved by Davide, then probably the solution should be done for all Rules that use the solve_network.py script.

os.getcwd() must be avoided as it does not track the use of submodules and can lead to issues.
Have you tried with directory(data/...)? [although the directory command should be optional for inputs].

Moreover, not sure if copy-minimal is strictly needed here; have you tested?

@davide-f I've tried running it on Windows with "shallow" instead, which led to issues with admin rights similar to PR #790.

I've not tried directory(data/...) yet. Would that look something like this?

input: overrides=( directory("/data/override_component_attrs") if os.name == "nt" else "/data/override_component_attrs" ),

Removing the different handling (as done by @Eddy-JV) will most likely mean, that the code will not work properly on Windows since it will not find the proper files when running with "copy-minimal" (an issue that will not be solved by PR #1295).
However, I'm in favor of doing it this way, if it means that we'll merge this PR somewhat soon and create a new issue for the Windows issues.

ekatef · 2025-01-09T09:36:47Z

config.default.yaml

-    Link: [] # H2 pipeline
+    Link: [H2 pipeline] # H2 pipeline


Just for better understanding: what is a particular idea of changing the default configuration parameters?

Agree that it may it be a good idea to make sure that the improvements introduced by this PR are being tested. It can be done by adding H2 pipeline as extendable_carriers:

pypsa-earth/test/config.sector.yaml

Lines 21 to 24 in ef525ee

electricity:

extendable_carriers:

Store: []

Link: []

What do you think?

Yes testing was the main reason for adding it. I've moved it to test/config.sector.yaml.

Minor changes: - fix the input files for solve_network in the Snakefile for non-Windows operating systems. - revert the addition of "H2 Pipeline" to config.default.yaml and move it to the test/config.sector.yaml instead.

Minor changes: - fix test/config.sector.yaml by adding H2 Stores

…onal_lossy_links

Eric-Nitschke · 2025-01-13T14:49:59Z

The failed readthedocs relates to issue #1291.

Eddy-JV

@Eric-Nitschke Thank you once again for the great work. I only have few comments shown above. After that the PR can be merged without my review.

@davide-f please check the os.getcwd comment.

@davide-f @ekatef I guess PR #1172 will have to be adapted to the new contraint function added here.

Eddy-JV · 2025-01-14T14:26:24Z

Snakefile

+                if os.name == "nt"
+                else "/data/override_component_attrs"
+            ),
+            # on Windows os.getcwd() is required because of the "copy-minimal" shadow directory


@davide-f This definitely needs your attention as you already made PR #790. And @Eric-Nitschke if this approved by Davide, then probably the solution should be done for all Rules that use the solve_network.py script.

Eddy-JV · 2025-01-14T15:06:01Z

scripts/add_extra_components.py

+    lossy_bidirectional_links(n, "H2 pipeline")
+
+    # set the pipelines efficiency and the electricity required by the pipeline for compression
+    set_length_based_efficiency(n, "H2 pipeline", " H2", config)


@Eric-Nitschke please add a variable like transmission_efficiency = snakemake.params.transmission_efficiency this means cahnging this to: set_length_based_efficiency(n, "H2 pipeline", " H2", transmission_efficiency )

and in the snakefile please add to the rule add_extra_components:

params: transmission_efficiency=config["sector"]["transmission_efficiency"],

in order to trigger the rule in case the efficiencies were changed in the config file by the user.

scripts/solve_network.py

Minor changes: - add a transmission efficiency parameter to the Snakefile for add_extra_components and change the bidirectional lossy link implementation in _helpers.py to use the parameter rather than the full config as input - add the adjustment to the override component input for Windows in the Snakefile to all rules calling solve_network.py - revert the identification of backward links in solve_network.py to again accommodate the myopic naming scheme

for more information, see https://pre-commit.ci

davide-f

Hello!
I've added the comment about os.cwd; we must avoid that unfortunately.

Regarding the linopy implementation of the new constraint:

when is this PR ready?
does this contraint must be added all the time or optionally?

Ideally, we should ideally not delay further too much the merge of the linopy PR [expected basically in these days after long preparation...]

davide-f · 2025-01-14T17:36:29Z

Snakefile

+                if os.name == "nt"
+                else "/data/override_component_attrs"
+            ),
+            # on Windows os.getcwd() is required because of the "copy-minimal" shadow directory


os.getcwd() must be avoided as it does not track the use of submodules and can lead to issues.
Have you tried with directory(data/...)? [although the directory command should be optional for inputs].

Moreover, not sure if copy-minimal is strictly needed here; have you tested?

…ix: Fix admin needs for Windows pypsa-meets-earth#1295

Eric-Nitschke · 2025-01-15T12:12:50Z

@davide-f technically the constraint is only required, if at least one lossy bidirectional component is used.
However, as the code is written right now (which is mostly taken from PyPSA-Eur), the constraint checks first if it is needed and if it isn't simply returns without changing anything, so there is no harm in calling it every run.

Adapting the constraint to PR #1172 should be somewhat easy, as the PyPSA-Eur implementation already used the newer PyPSA version including linopy.
To do so, simply change

lhs = linexpr(
    (1, get_var(n, "Link", "p_nom")[backward_i].to_numpy()),
    (-1, get_var(n, "Link", "p_nom")[forward_i].to_numpy()),
)

# add the constraint to the PySPA model
define_constraints(n, lhs, "=", 0, "Link-bidirectional_sync")

to

lhs = n.model["Link-p_nom"].loc[backward_i]
rhs = n.model["Link-p_nom"].loc[forward_i]

n.model.add_constraints(lhs == rhs, name="Link-bidirectional_sync")

which is the section I changed to make it work with linopf.

Eddy-JV · 2025-01-15T12:46:51Z

Hello! I've added the comment about os.cwd; we must avoid that unfortunately.

Regarding the linopy implementation of the new constraint:

when is this PR ready?

does this contraint must be added all the time or optionally?

Ideally, we should ideally not delay further too much the merge of the linopy PR [expected basically in these days after long preparation...]

@Eric-Nitschke Thank you for swiftly addressing my comments and @davide-f Thanks for checking this up. Now that this PR is mature enough to be merged and very much needed ASAP for the Linopy adaptation, I took the liberty to change this:

            overrides=(
                os.getcwd() + "/data/override_component_attrs"
                if os.name == "nt"
                else "data/override_component_attrs"
            ),
            # on Windows os.getcwd() is required because of the "copy-minimal" shadow directory

back to

         overrides="data/override_component_attrs",

from the current PR and address it seperately in PR #1295 or another PR. Awesome work @Eric-Nitschke , I will merge now.

ekatef · 2025-01-15T15:36:43Z

@Eric-Nitschke, @Eddy-JV, @davide-f fantastic work!! 😄 Great to see the contribution completed and merged 🎉

@Eric-Nitschke if you wish to go ahead with adapting the constraint for linopy, feel free to open a PR on that 🙂

ekatef · 2025-01-16T17:53:08Z

@Eric-Nitschke just flagging that the constraint update has been implemented #1276 as it's crucial for the model update. Apologies if I have been misleading and thanks a lot for the major contribution in resolving the folder management issue for windows!

Eric-Nitschke and others added 2 commits November 14, 2024 11:54

[pre-commit.ci] auto fixes from pre-commit.com hooks

9acbfe4

for more information, see https://pre-commit.ci

Eric-Nitschke added 2 commits November 18, 2024 18:03

Update release notes

a1f91e4

Changes: - add a describtion of this pull request to the release_notes.rst

Merge remote-tracking branch 'origin/main'

31c7973

Eric-Nitschke and others added 3 commits November 22, 2024 10:33

Spelling fix

a0c0a05

- correct spelling mistakes in doc/release_notes.rst

Merge branch 'main' of github.com:pypsa-meets-earth/pypsa-earth

a2150d6

docs(contributor): contrib-readme-action has updated readme

1a98c9f

ekatef mentioned this pull request Nov 28, 2024

Hydrogen pipeline efficiency #1213

Closed

2 tasks

ekatef reviewed Dec 3, 2024

View reviewed changes

Eddy-JV requested changes Dec 3, 2024

View reviewed changes

Eric-Nitschke and others added 5 commits December 19, 2024 10:36

Revert "docs(contributor): contrib-readme-action has updated readme"

ac90aec

This reverts commit 1a98c9f.

docs(contributor): contrib-readme-action has updated readme

a3bd91d

Fix ci (pypsa-meets-earth#1210)

80aee27

* Update CI * Change contrib job weekly * Update environment: ppl and atlite * Update pinned files * Reset ci cache * Revise vresutils pinned * Add release_note (cherry picked from commit 114a953)

Merge branch 'main' of github.com:Eric-Nitschke/pypsa-earth-bidirecti…

45fdc2b

…onal_lossy_links

[email protected]:pypsa-meets-earth/pypsa-earth.git

77f557f

Fix bidirectional lossy links

e38b221

Major changes: - Fix bidirectional lossy links by splitting the into to links in _helpers.py - Add length based efficiency calculations in _helpers.py

Constraint implementation bug fixes

fefe70b

Bug fixes: - modify the override component location provided in the Snakefile to work with the "copy-minimal" shadow directory on Windows - fix the identification of all forward links in scripts/solve_network.py

Eric-Nitschke mentioned this pull request Jan 2, 2025

Lossy bidirectional links with length based efficiency Eric-Nitschke/pypsa-earth-bidirectional_lossy_links#2

Closed

Eric-Nitschke added 2 commits January 2, 2025 16:19

Revert "Merge branch 'main' of github.com:Eric-Nitschke/pypsa-earth-b…

4738a3f

…idirectional_lossy_links" This reverts commit 45fdc2b, reversing changes made to 80aee27.

Merge branch 'lossy_length_based'

e108be5

Eric-Nitschke added 2 commits January 2, 2025 17:04

Merge remote-tracking branch 'upstream/main'

9f55920

Unify transmission efficiency

2ac8db4

Minor changes: - move the transmission efficiency of the H2 pipelines to the one of the transmission grid, which was added with the last merge.

[pre-commit.ci] auto fixes from pre-commit.com hooks

02fc071

for more information, see https://pre-commit.ci

Eric-Nitschke requested a review from Eddy-JV January 2, 2025 16:12

Eric-Nitschke added 3 commits January 2, 2025 17:16

Spelling fix

9d14ac2

Merge branch 'main' of github.com:Eric-Nitschke/pypsa-earth-bidirecti…

f6aa253

…onal_lossy_links

Release notes update

ca1db0a

ekatef reviewed Jan 9, 2025

View reviewed changes

Eric-Nitschke and others added 4 commits January 13, 2025 11:36

Bugfix Snakefile for non-Windows operating systems

7c87a48

Minor changes: - fix the input files for solve_network in the Snakefile for non-Windows operating systems. - revert the addition of "H2 Pipeline" to config.default.yaml and move it to the test/config.sector.yaml instead.

Merge branch 'main' into main

4092176

Bugfix test config

fcb9911

Minor changes: - fix test/config.sector.yaml by adding H2 Stores

Merge branch 'main' of github.com:Eric-Nitschke/pypsa-earth-bidirecti…

007e427

…onal_lossy_links

Merge branch 'main' into main

b1ef404

Eddy-JV reviewed Jan 14, 2025

View reviewed changes

Eric-Nitschke and others added 2 commits January 14, 2025 17:04

[pre-commit.ci] auto fixes from pre-commit.com hooks

d84ce66

for more information, see https://pre-commit.ci

davide-f reviewed Jan 14, 2025

View reviewed changes

Eddy-JV approved these changes Jan 15, 2025

View reviewed changes

Update Snakefile: Remove os.getcwd from this PR. To be solved in Bugf…

eaba5cf

…ix: Fix admin needs for Windows pypsa-meets-earth#1295

Eddy-JV merged commit 83434a0 into pypsa-meets-earth:main Jan 15, 2025
6 checks passed

This was referenced Jan 15, 2025

Length based pipeline efficiency #1215

Closed

Linopy integration for Power and Sector-Coupled Modelling #1172

Closed

Eric-Nitschke mentioned this pull request Jan 16, 2025

Test win shadow #1299

Closed

8 tasks


		"Split bidirectional links into two unidirectional links to include transmission losses."

Lossy Bidirectional Links #1192

Lossy Bidirectional Links #1192

Conversation

Eric-Nitschke commented Nov 14, 2024 • edited Loading

Checklist

davide-f commented Nov 15, 2024

Eric-Nitschke commented Nov 18, 2024

ekatef left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Eddy-JV left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

ekatef commented Dec 11, 2024

Eric-Nitschke commented Dec 13, 2024 • edited Loading

Eddy-JV commented Dec 15, 2024

ekatef commented Dec 28, 2024

Eric-Nitschke commented Jan 2, 2025

Eric-Nitschke commented Jan 2, 2025

Eric-Nitschke commented Jan 2, 2025

ekatef left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Eric-Nitschke Jan 13, 2025 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Eric-Nitschke Jan 13, 2025 • edited Loading

Choose a reason for hiding this comment

Eric-Nitschke commented Jan 13, 2025

Eddy-JV left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

davide-f left a comment • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Eric-Nitschke commented Jan 15, 2025

Eddy-JV commented Jan 15, 2025

ekatef commented Jan 15, 2025

ekatef commented Jan 16, 2025

Eric-Nitschke commented Nov 14, 2024 •

edited

Loading

Eric-Nitschke commented Dec 13, 2024 •

edited

Loading

Eric-Nitschke Jan 13, 2025 •

edited

Loading

Eric-Nitschke Jan 13, 2025 •

edited

Loading

davide-f left a comment •

edited

Loading