Closed GreatScherzo closed 3 years ago
Hey. Thanks for your report and detailed description, and sorry for the rather late response. We were able to locate the problem and I've just pushed a commit that should fix it. Note that this required to deactivate enlarging the MVTec-AD dataset, which we initially did to speed up the data loading process. This should not impact the performance, but you need ten times as many epochs as reported in the paper. I adjusted the default parameters, so you don't need to worry about that.
Thanks to @tkollmer for helping me to test this on Windows.
Thank you very much taking your time. Unfortunately, I'm still experiencing the same bug. Currently debugging for the underlying problem, will post an update if I find more about this
So apparently the bug occurs if you used Python 3.8 instead of 3.6.
When I was following the steps in installing fcdd, pip gives out an error saying that "it could not find a version that satisfies the requirement for torch==1.4.0" within fcdd, which is kind of ambiguous. I then tried installing torch 1.4.0 using conda, which tells me clearly that the current python version isn't compatible with torch 1.4. I then downgraded python, installed torch 1.4 through conda, and tried using the fcdd-windows of the previous version, and sure enough, the bug that you mentioned above #7 did occur. I then tried it with the patched version, and it worked fine.
Cheers!
🐛Bug
Traceback
Expected Behaviour
Was expecting for it to sample the MVTec Dataset without any problems
Environment
PyTorch Version: 1.4.0 Is Cuda Available?: Yes
OS: Windows 10 Pro
Python version: 3.8
CUDA runtime version: 10.2.141 GPU models and configuration: GPU 0: NVIDIA Quadro P1000 Nvidia driver version: 442.50
Additional Context
Thank you very much for taking time in assessing this issue :)
Edit
Sorry, i forgot to mention, i had problems with installing pytorch for the environment, then i went to install it by direct linking to the builds