Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

code does not run without modifications, documentation missing crucial information #2

Open
ixfd64 opened this issue Sep 12, 2024 · 0 comments

Comments

@ixfd64
Copy link

ixfd64 commented Sep 12, 2024

I'm trying to set up the project on my system. However, the code does not run without additional changes. Furthermore, there are a lot of details missing from the readme.

  1. Package installation initially failed at mpi4py-mpich due to a "No matching distribution found for mpi4py-mpich" error. I was able to resolve this by changing it to plain mpi4py in the requirements file. Also, at least on Windows, Python will still complain about missing libraries in mpi4py when the training script is run unless the user has installed MS-MPI prior to the mpi4py package. I have not checked to see if this affects other operating systems.
  2. PyTorch and torchvision are missing from the requirements file.
  3. I then got a "use_libuv was requested but PyTorch was build [sic] without libuv support" runtime error, and was only able to resolve it by downgrading PyTorch to version 2.3.0.
  4. The readme does not mention that the user has to manually change path-to-glaucoma-detection-dataset to the data set folder in the shell scripts.
  5. Python then threw an error saying that the "Distributed package doesn't have NCCL built in." I had to comment out the line dist_util.setup_dist() to proceed.
  6. I also had to comment out the wandb initialization code due to an error about invalid API keys.
  7. Python now throws a new RuntimeError because the path <data set>/train could not be found. The data set folder contains a lot of *.npz files, but it is not clear how to convert those to a train folder. Any advice would be appreciated.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant