-
Notifications
You must be signed in to change notification settings - Fork 2
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
A few problems encountered while running the Docker container #1
Comments
Hi, thanks so much for the suggestions! We released a new version of the Docker image (v1.0.3). There are multiple updates hopefully can help resolve the issues you mentioned. Files under If the cohort is huge (like NLST), a good practice would be to run in batches, e.g., with size of each batch under 200, so the temp files can be cleaned up timely. The file permission problem can be solved by passing Hope these can help |
Thank you Kaiwen for reaching back! I will definitely give this a try :-) |
Hi, I tried to reproduce the inference results using the provided examples from TCIA on Windows machine. I encountered some issues when executing extract_lung_region_3D(...). The error occurs when I execute c3d via command line, but I'm not sure. Command line for executing c3d: $D:\S-EFOV_refineSPECT_BC\tools\c3d D:\TCIA_demo\Output\Temp\ct_std\COVID-19-AR-16406490.nii.gz -region 87x130x10vox 336x221x522vox -o D:\TCIA_demo\Output\Temp\ct_crop3D\COVID-19-AR-16406490.nii.gz My questions are
Thanks -----------------------------------------log info--------------------------------------------------- Vertebral level prediction Generate record (#CPU=1): 100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 4/4 [00:03<00:00, 1.10it/s] |
I am closing the older bug reports as these were missed. We are now better tracking reports across the organization. Please re-open if this continues to be a blocker. |
Dear developers,
Thank you for sharing this resource and congrats for the publication on Radiology!
I just tested the docker container you folks built and shared, and I wanted to ask if you could fix a couple of things that might make the use of the tool way easier!
The input NIfTI file(s) get deleted after the run
First of all, this was the output of the run:
As you can imagine from the last line:
The NIfTI data I ran the container on got nuked from my system. This means that, if I want to run the analysis for 10,000 patients, I would need to run the conversion from DICOM and will be able to use those NIfTI only once!
I tried to fix this problem by mounting the input directory/volume as read only, using
-v $INPUT_DIR:/Input:ro
as you normally do in Docker, but this makes the run crash:(notice the data I ran the pipeline on was the same piece of data as before, so I highly doubt this is down to something else!)
Only users with root privileges can handle the pipeline output
When running the pipeline on a Linux system, all of the output files get saved as
root
- which makes the handling of the results afterwards a bit sloppy. This is a well documented issue with Docker on Linux (in order to avoid this, you would need to build the container specifying the user id and group id). The way you could solve this is changing the file permissions inside the container (of whatever gets exported by the pipeline, basically the python equivalent tochmod 777
).Temp folder
Last but not least, I couldn't help but notice a pretty size-y
Temp
folder is exported with every run: is this intended to be exported, or...?I would really like to use and cite this tool for some of my research projects, so it would be amazing if you could look into this 🙃
Thank you for your time,
Dennis.
The text was updated successfully, but these errors were encountered: