Running the evaluation code
Hmz30265 opened this issue · 4 comments
Hello authors, thank you for the contribution.
I am currently making a simple simulation of the evaluation code so I could understand how the evaluation process is working. Right now, I have created couple dummy points and I can get IoUs and IoU matches. When I tried to run this code :
shapo/utils/nocs_eval_utils.py
Line 538 in 7496327
It gives me this error message:
I don't know how you do you explain this problem. Could you help me with that? For your information, my two parameters look like this:
Please let me know if you could help me with that. I am looking forward to hearing back from you. Thank you!
Thanks, @MattMiaozhuangHe for your interest in our work. I would suggest you go through this issue in our accompanying repo, CenterSnap where evaluation is discussed in detail. I would try to take a pre-trained checkpoint and produce outputs and feed that into the function to get a better sense of evaluation. Dummy variables might not work and could have their own problems like class mismatch etc.
Regarding the other issue, I would manually install torch 1.7.1+cu101 from here in your notebook and install the rest of the dependencies using requirements.txt
You might have to comment out that line which installs pytorch in the requirements.txt and point the notebook to install requirements.txt from the local repo.
Hope it helps!
Thank you for answering my questions @zubair-irshad , I have successfully download torch1.7.1+cu101 and that error message does not show again. However, I believe a bigger problem is that the Colab only support Python 3.10.
And it can't be fallback to earlier version of Python, which is in the required in this notebook:
ERROR: Ignored the following versions that require a different python version: 1.6.2 Requires-Python >=3.7,<3.10; 1.6.3 Requires-Python >=3.7,<3.10; 1.7.0 Requires-Python >=3.7,<3.10; 1.7.1 Requires-Python >=3.7,<3.10
Is there anyway I can fix this problem? Looking forward to hearing back from you!
Apologies for a delayed response as we were busy on our end with other code releases/paper deadlines. Were you able to solve this issue. Does adding python==3.9 in the requirements.txt make it work for you?