Open alessandriniluca opened 4 months ago
I have the same issue. However, I found that the given weights dont include the weights for group_converters in the model. The weights have weights for 'module.converter' but there is no module in the given model architecture.
Can you please upload the weights for the given architecture?
First of all, thank you for the work you did in the paper!
I'm sorry to bother you, but I am facing some problems that I'll explain here below
Problems during Machine setup
Unfortunately, I'm encountering some troubles in running the code (and I think some versions are missing for correct reproducibility). As suggested in your
README.md
, I am running the experiments on ubuntu. More specifically,lsb_release -a
returns:Possible error in
requirements.txt
or wrong cudaThe error I'm obtaining arises when i perform
pip install -r requirements.txt
, and it says:Steps to reproduce:
On an ubuntu distribution with cuda
12.3
, after having installed miniconda:$ git clone https://github.com/ZhouHuang23/FSPNet.git
$ conda create -n FSPNet python=3.8
$ conda activate FSPNet
$ cd FSPNet/
~/FSPNet$ pip install -r requirement.txt
Possible missing versions
The following package / libraries versions are not specified:
cuda
timm
imageio
Problems regarding results reproducibility
This problem could be due to the different versions of things I used, and I think this should be solved when the above one is solved.
Since on the server I have not enough space, I run this test on my laptop and desktop both running Arch Linux. In order to solve the above issue, I tried to change some version of python and packages.
Through conda I installed:
python=3.9
cudatoolkit-dev=11.7
(adding-c conda-forge
)Through poetry I found compatible versions for python libraries, which may differ with respect to the ones you used. The
pyproject.toml
I declared is like the following:I tried to run predictions on COD10K test set, but seem being quite different with respect to the result you obtained. I suspect that this may be a problem of packages versions, and should be solved when the above problem is solved. Issues persist both when using a GTX 1050 (laptop configuration) and RTX 4080 (Desktop configuration)
Thank you in advance for your availability