fix: extra functionality not called

[lkstrp]

• Works with just moving the file to the pypsa-eur placeholder. Not sure why it was setup like this in the first place

Checklist

• Workflow with target rule ariadne_all completes without errors
• The latest main has been merged into the PR

[github-actions]

Validator Report

I am the Validator. Download all artifacts here.
I'll be back and edit this comment for each new commit.

❗ Run failed!

Download 'logs' artifact to see more details.

• main failed in: export_ariadne_variables
• fix-extra-funcs passed! ✅

Model Metrics

Benchmarks

Comparing fix-extra-funcs (2e0fc1e) with main (3fa5c3f).
Branch is 2 commits ahead and 1 commits behind.
Last updated on 2025-01-09 10:36:42 CET.

[toniseibold]

In general it works and is looking good. It is also nice to include it with the infrastructure already provided by pypsa-eur.
However, what doesn't quite sit right with me is placing the custom_extra_functionality script into the data folder. The data folder in my opinion is for universal files that are used as input only.
The custom_extra_functionality is changing the optimization problem profoundly so I would like to see it somewhere in ./scripts/...
@lindnemi / @fneum what is your opinion on this? Is that something you'd like to see and if so only for pypsa-de or even pypsa-eur?

[lkstrp]

I couldn't agree more.

We can just move the file and change the path in the default config for pypsa-de:

pypsa-de/config/config.default.yaml

Line 912 in c1e59d1

custom_extra_functionality: "../data/custom_extra_functionality.py"

In Eur it is probably meant as a "data file" for users who do not touch any code and just add custom functionality with some changes in the config. It still doesn't make sense for this to be tracked by git. But this is a pypsa-eur problem. The data folder also needs a general clean up over there.

For DE I would just move the file back to scripts and change the default config.