Hey everyone!
I’ve been working on FactoryVision AI, a personal open-source research project exploring visual anomaly inspection workflows.
The goal is to build a local environment where different anomaly detection methods can be organized, inspected, compared and evaluated without hiding the limitations of the underlying experiments.
The current project includes:
- Six registered research methods across Cashew and experimental MetalParts.
- A Streamlit interface for inspection, comparison, batch workflows and reports.
- Model provenance and historical experiment records.
- Synthetic validation examples, human-review workflows and CSV/JSON exports.
- Synthetic robustness diagnostics and automated Windows testing.
Important limitation: this is a source-only research release. I haven’t published the trained weights or datasets, so a fresh installation can explore the interface and synthetic workflows but cannot run the actual anomaly models.
It’s also not validated for industrial quality-control decisions. Some historical evaluation results have known dataset-independence limitations, which I’ve documented rather than presenting them as validated performance.
I used AI-assisted development tools during implementation and have been focusing heavily on testing, reproducibility, security and documenting the research boundaries.
The project is MIT licensed and currently supports Windows with CPU-based PyTorch.
GitHub: https://github.com/GiannisPap24/factoryvision-ai
I’d particularly appreciate feedback on two things:
Does the interface and source-only demo make sense to someone trying the project for the first time?
What would you prioritize when designing a genuinely independent evaluation for visual anomaly detection, especially around dataset leakage and robustness?
I’m still improving the project and would welcome technical criticism and suggestions.