Anomalib CLI Improvements - Update metrics and create post_processing section in the config file

[samet-akcay]

Description

• Update metrics and create post_processing section in the config file
• Fixes Anomalib CLI Improvements - Update metrics and create post_processing section in the config file. #384

Changes

• Bug fix (non-breaking change which fixes an issue)
• Refactor (non-breaking change which refactors the code base)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist

• My code follows the pre-commit style and check guidelines of this project.
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing tests pass locally with my changes

[ashwinvaidya17]

Looks good to me. Maybe later we can look into setting up these values without using a callback.

[djdameln]

Maybe later we can look into setting up these values without using a callback.

Yeah. I'm a bit concerned about adding too many ConfigurationCallbacks, because I feel this is not in line with the intended use of PL's Callback class. But at this point I also don't have a better design in mind that would work with the CLI. So for now we could keep it this way.

[djdameln]

We could consider replacing this parameter with a selectable called thresholding_method with the options fixed and adaptive. This might be a bit less confusing (for the unknowing reader, adaptive_threshold could sound like it holds a threshold value). Later we could extend it with synthetic option.

[samet-akcay]

I was also having a similar idea in my mind. I was not quite sure how exactly to address fixed image and pixel thresholds though

[djdameln]

It would be the equivalent of adaptive_threshold: false in the current implementation

[samet-akcay]

yeah, but let's say we set thresholding_method to fixed. We would still need to set fixed_image_threshold and fixed_pixel_threshold, right?

[djdameln]

yeah, but I don't see any problems with that. If users want to use a fixed threshold then they will have to provide a value for that. If they don't know which value to provide then they should just use the adaptive threshold.

[samet-akcay]

Yeah. I'm a bit concerned about adding too many ConfigurationCallbacks, because I feel this is not in line with the intended use of PL's Callback class. But at this point I also don't have a better design in mind that would work with the CLI. So for now we could keep it this way.

This is the phase-2 of this cli refactoring. It requires some additional extensions to the lightning cli