-
Notifications
You must be signed in to change notification settings - Fork 532
nipype issues with calling dcm2nii #3302
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
Comments
I have the same issue and error,windows socket error. How to solve ? |
Hi, the problem is that we don't support Windows (this is issue #3277). We'd be happy to accept a patch from someone with a Windows machine. You can also try using the Windows Subsystem for Linux (WSL), but I don't have any experience there. |
it will be a weekend project for me when I get around to it after work. |
Thank you for getting back on this issue. @Gresliebear That would be great. Please do keep me posted. |
Hi. Is there any news on the compatibility of dcm2niix for windows? The socket error still persists for me. |
I have recently come into possession of a Windows machine, so when I have the opportunity, I can try to debug this. Making nipype Windows compatible will be a major effort, though. Have you looked into Pydra? Or using the WSL? |
any luck ? it seems there are more users hitting this: https://neurostars.org/t/dcm2niix-error-using-heudiconv/26759 |
nipype noob here thank you for developing this software packages its very help but I am running to into simply problem by reading in a source_dir PAT001 containing 201 dcm files convert into nii file for developing pipeline for a deeplearning model
OSError: [WinError 10038] An operation was attempted on something that is not a socket
Summary
from nipype.interfaces.dcm2nii import Dcm2nii
Actual behavior
I am pretty sure dcm2nii code is running because it generates a bunch of .nii files

Expected behavior
Script/Workflow details
taking 200 DICOM files into a single nii file
Platform details:
Windows 10 VScode python 3.7
Execution environment
Choose one
The text was updated successfully, but these errors were encountered: