Document anomaly detection pipeline architecture #474
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JohT
force-pushed
the
feature/document-anomaly-detection-architecture
branch
6 times, most recently
from
33bfb39 to
76e751b
Compare
JohT
force-pushed
the
feature/document-anomaly-detection-architecture
branch
from
76e751b to
a53aa52
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🚀 Feature
Add pipeline architecture overview to Markdown summary report: The report now includes an appendix section with a visualization of the anomaly detection pipeline architecture.
Add anomaly detector input feature visualization: Adds a 2D scatter plot that projects the Isolation Forest model's input features into two dimensions and highlights detected anomalies in red — so you can "see what the anomaly detector sees."
📖 Documentation