fix lots of typos
All checks were successful
Build Typst document / build_typst_documents (push) Successful in 1m9s
All checks were successful
Build Typst document / build_typst_documents (push) Successful in 1m9s
This commit is contained in:
@ -1,14 +1,14 @@
|
||||
= 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 or EfficientAD.
|
||||
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.
|
||||
Most of the time plenty of good samples are available and in this case PatchCore or EfficientAD should perform great.
|
||||
|
||||
The only case where Few-Shot learning could be used is in a scenarios where one wants to detect the anomaly class itself.
|
||||
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.
|
||||
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.
|
||||
@ -19,4 +19,4 @@ There might be a lack of research in the area where the classes to detect are ve
|
||||
and when building a few-shot learning algorithm tailored specifically for very similar classes this could boost the performance by a large margin.
|
||||
|
||||
It might be interesting to test the SOT method (see @SOT) with a ResNet50 feature extractor similar as proposed in this thesis but with SOT for embedding comparison.
|
||||
Moreover, TRIDENT (see @TRIDENT) could achive promising results in a anomaly detection scenario.
|
||||
Moreover, TRIDENT (see @TRIDENT) could achieve promising results in an anomaly detection scenario.
|
||||
|
Reference in New Issue
Block a user