fix stuff from prof
Some checks failed
Build Typst document / build_typst_documents (push) Failing after 1m39s

This commit is contained in:
2025-02-04 20:07:59 +01:00
parent 7681b4afce
commit c8ac00571b
6 changed files with 27 additions and 27 deletions

View File

@ -1,7 +1,7 @@
= Conclusion and Outlook <sectionconclusionandoutlook>
== Conclusion
In conclusion one can say that Few-Shot learning is not the best choice for anomaly detection tasks.
It is hugely outperformed by state of the art algorithms like PatchCore or EfficientAD.
It is hugely outperformed by state of the art algorithms like PatchCore@patchcorepaper or EfficientAD@efficientADpaper.
The only benefit of Few-Shot learning is that it can be used in environments where only a limited number of good samples are available.
But this should not be the case in most scenarios.
Most of the time plenty of good samples are available and in this case PatchCore or EfficientAD should perform great.
@ -10,8 +10,8 @@ The only case where Few-Shot learning could be used is in a scenarios where one
PatchCore and EfficientAD can only detect if an anomaly is present or not but not what type of anomaly it actually is.
So chaining a Few-Shot learner after PatchCore or EfficientAD could be a good idea to use the best of both worlds.
In most of the tests P>M>F performed the best.
But also the simple ResNet50 method performed better than expected in most cases and can be considered if the computational resources are limited and if a simple architecture is enough.
In most of the tests P>M>F@pmfpaper performed the best.
But also the simple ResNet50@resnet method performed better than expected in most cases and can be considered if the computational resources are limited and if a simple architecture is enough.
== Outlook
In the future, when new Few-Shot learning methods evolve, it could be interesting to test again how they perform in anomaly detection tasks.