feat: check objective in test routines

[FabianHofmann]

Option to counter-check the objective value against expected value. With this check, we make sure that no strong deviations from the expected objective are introduced. In case the objective varies stronger than the allowed tolerance, but for a good reason (new tech/tech costs), the expected value has to be updated manually.

Changes proposed in this Pull Request

Checklist

• I tested my contribution locally and it works as intended.
• Code and workflow changes are sufficiently documented.
• Changed dependencies are added to envs/environment.yaml.
• Changes in configuration options are added in config/config.default.yaml.
• Changes in configuration options are documented in doc/configtables/*.csv.
• Sources of newly added data are documented in doc/data_sources.rst.
• A release note doc/release_notes.rst is added.

[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.

• master failed in: no_logs_found
• test-objective failed in: no_logs_found

Model Metrics

Benchmarks

Comparing test-objective (adfe791) with master (bd5e36c).
Branch is 5 commits ahead and 0 commits behind.
Last updated on 2025-01-16 19:42:26 CET.

[fneum]

Good utility!

[lkstrp]

Would this have catched the linopy bug? I guess no since the test configs are to small?

[FabianHofmann]

Would this have catched the linopy bug? I guess no since the test configs are to small?

I think so yes! the exclusion of balance contraints which happened was altering the optimization quite significantly.