New configuration option: 'per-feature-labels'

[APersonH]

I added an option 'per-feature-labels' that can either be set in the yaml files to be either true or false, but is false by default. It works by adding a 'channel' variable to the LabelRange dataclass, and then, if the option is set, adds a new column to the output csv for each channel, specifying whether this channel is anomalous. The original 'is-anomaly' is found by taking the max of all per channel labels, and is still added to the csv in both cases.

This is very useful to have when trying to do explainability studies on anomaly detection algorithms.

This is my first pull request, please let me know if anything is missing, or there is additional things I need to deliver/do :-) (Or if I've something completely stupid)

[SebastianSchmidl]

Hey @APersonH, nice idea 👍🏼 The changes look promising. Could you add tests for your new feature and also another example configuration in generation_configs?

[codecov]

Codecov Report

❌ Patch coverage is 80.00000% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.21%. Comparing base (77f22f9) to head (62fafb5).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
gutenTAG/generator/timeseries.py	60.00%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #86      +/-   ##
==========================================
- Coverage   90.28%   90.21%   -0.07%     
==========================================
  Files          53       53              
  Lines        2120     2126       +6     
==========================================
+ Hits         1914     1918       +4     
- Misses        206      208       +2     

Flag	Coverage Δ
unittests	90.21% <80.00%> (-0.07%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.