Skip to content

Conversation

@casperthuis
Copy link

@casperthuis casperthuis commented Dec 19, 2025

πŸ“ Description

✨ Changes

Select what type of change your PR is:

  • πŸš€ New feature (non-breaking change which adds functionality)
  • 🐞 Bug fix (non-breaking change which fixes an issue)
  • πŸ”„ Refactor (non-breaking change which refactors the code base)
  • ⚑ Performance improvements
  • 🎨 Style changes (code style/formatting)
  • πŸ§ͺ Tests (adding/modifying tests)
  • πŸ“š Documentation update
  • πŸ“¦ Build system changes
  • 🚧 CI/CD configuration
  • πŸ”§ Chore (general maintenance)
  • πŸ”’ Security update
  • πŸ’₯ Breaking change (fix or feature that would cause existing functionality to not work as expected)

βœ… Checklist

Before you submit your pull request, please make sure you have completed the following steps:

  • πŸ“š I have made the necessary updates to the documentation (if applicable).
  • πŸ§ͺ I have written tests that support my changes and prove that my fix is effective or my feature works (if applicable).
  • 🏷️ My PR title follows conventional commit format.

@casperthuis casperthuis changed the title docs(docs): <description> [optional body] [optional footer] docs(benchmarking): Updating outdated doc string benchmarking pipeline [optional body] [optional footer] Dec 19, 2025
@casperthuis casperthuis changed the title docs(benchmarking): Updating outdated doc string benchmarking pipeline [optional body] [optional footer] docs(benchmarking): Updating outdated doc string benchmarking pipeline Dec 19, 2025
Example:
>>> from anomalib.pipelines import Benchmark
>>> from anomalib.data import MVTecAD
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can only see the deleted lines. Maybe you forgot to commit the new example.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

πŸ“š BenchMark Pipeline

2 participants