-
Notifications
You must be signed in to change notification settings - Fork 0
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
ImportError: cannot import name 'nnUNetPredictor' #4
Comments
Here's the list of packages that were installed in my venv:
|
Ahh, yes we need to pin the nnunet version. The problem is that The requirements.txt file should instead look like this:
|
Gotcha! I just tested and got this message:
Seems like I installed python with 3.8, but we'll also need to inform the users that they'll need a venv with python >=3.9 as well That's why the unrestircted req file didn't install the latest version |
Oh well, I forgot about that. As per https://pip.pypa.io/en/stable/reference/requirements-file-format/, we can specify this in the requirements.txt file using something like this:
|
I didn't know that - neat! |
Ahh, but if you do that, it'll just not install the package at all actually:
So we should stick with only setting nnunetv2>=2.2 then |
Ah damn. I'll add a note in the README that the user needs python >=3.9 then. |
Besides, that, I installed it with the new nnunetv2 condition and this error doesn't occur anymore, but now I'm encountering #5 So I'll make a PR to close this one and we can continue discussing in the next issue |
nm - I see you have https://github.com/axondeepseg/nn-axondeepseg/tree/ac/pin_nnunetv2 this branch already, so I'll let you do it! |
Closed with #6 |
OS: MacOS
venv tool: conda
I've followed all the installation instructions up to testing the segmentation command (installing both models), and when I run that command I get the following output (for both SEM and TEM images, and both UM and BF models):
Is this missing package not in the requirements.txt file? Or (more likely in my opinion) because the requirements don't have any versions in requirements.txt, and the latest nnunet software does not have that feature (or is renamed)?
nn-axondeepseg/requirements.txt
Line 1 in cf4cfa3
The text was updated successfully, but these errors were encountered: