-
Notifications
You must be signed in to change notification settings - Fork 15
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
Error running nnunet conda env #380
Comments
I'm also not sure what's going on, but with #381 we should once again be able to use the container dependencies without conda. Trying that out now to see how it goes.. |
One thing to try is to make a conda env based on the exact nnunet version we are using in the container. It is here: https://github.com/yinglilu/nnUNet/tree/inference_on_cpu_v1.6.6 If we can get that working, then can we at least have a starting point to see what changes break things.. |
Unfortunately that also didn't work; I ended up with the same error. I've put v1.6.6 on khanlab if you want to check it out. |
Ah - based on the error message it looks like it is using the latest version of pytorch, which is probably causing problems. If you pin the major packages (torch, numpy) based on https://github.com/khanlab/hippunfold_deps/blob/main/pyproject.toml it should hopefully fix the issue.. |
note you probably don't need an archaic version of torch -- since 2.6 was released last month I am thinking that is what broke it, so maybe <2.6 will work.. |
Right, it was complaining about using pytorch 2.6+... I'll try that, thanks @akhanf! |
Unfortunately, the error still persists even after pinning major packages and using an older version of pytorch. This is a snippet from the meta.yaml file:
Will keep you updated! |
Did you try with the version numbers pinned in hippunfold_deps too? (thats with a pretty old version of torch)
…________________________________
From: Dhananjhay Bansal (Djay) ***@***.***>
Sent: February 27, 2025 12:24 PM
To: khanlab/hippunfold ***@***.***>
Cc: Ali Khan ***@***.***>; Mention ***@***.***>
Subject: Re: [khanlab/hippunfold] Error running nnunet conda env (Issue #380)
Unfortunately, the error still persists even after pinning major packages and using an older version of pytorch. This is a snippet from the meta.yaml file:
requirements:
host:
- python
- pip
run:
- python
- pytorch <2.6.0
- tqdm
- dicom2nifti
- scikit-image >=0.14
- medpy
- scipy==1.7.1
- batchgenerators==0.21
- numpy==1.21.2
- scikit-learn
- simpleitk==2.0.2
- pandas >=1.2.0,<=1.3.0
- requests
- nibabel >=3.2.1
- tifffile
- matplotlib==3.4.2
Will keep you updated!
—
Reply to this email directly, view it on GitHub<#380 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACXV2XOSP7GUIEKAYN75XU32R5C4RAVCNFSM6AAAAABXZQAYSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBYGYZDKNJSGU>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
[Dhananjhay]Dhananjhay left a comment (khanlab/hippunfold#380)<#380 (comment)>
Unfortunately, the error still persists even after pinning major packages and using an older version of pytorch. This is a snippet from the meta.yaml file:
requirements:
host:
- python
- pip
run:
- python
- pytorch <2.6.0
- tqdm
- dicom2nifti
- scikit-image >=0.14
- medpy
- scipy==1.7.1
- batchgenerators==0.21
- numpy==1.21.2
- scikit-learn
- simpleitk==2.0.2
- pandas >=1.2.0,<=1.3.0
- requests
- nibabel >=3.2.1
- tifffile
- matplotlib==3.4.2
Will keep you updated!
—
Reply to this email directly, view it on GitHub<#380 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACXV2XOSP7GUIEKAYN75XU32R5C4RAVCNFSM6AAAAABXZQAYSKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBYGYZDKNJSGU>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
I'm running wet run tests on lowresMRI data pulled from OSF and it keeps failing at rule
run_inference
.The command I'm running is
Error output on the terminal:
And this is what the log file says:
I'm skeptical this has something to do with nnunet conda env because there haven't been any changes to the config file and we have had run successful wet run tests using
--use-conda
flag.The text was updated successfully, but these errors were encountered: