-
Notifications
You must be signed in to change notification settings - Fork 37
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
Data preprocessing for CHAOS dataset can break. #3
Comments
I agree that this can cause an issue. Thank you for pointing it out. I will update the code. In our experiments, it didn't cause any problems. If it did, we would have noticed it since we save image volumes and ground truth volumes in the experiments. |
Great, thank you! |
So, the solution to this problem is still not updated in the code. Can you post the exact code for your solution? I also encountered this problem |
Sure, I changed it to
at L104, and
at L152. This sorts the images by name, which puts them in the correct order. |
I run the code but meet the error:No such file or directory: '/content/drive/My Drive/voxel2mesh/Chaos/Train_Sets/DICOM_anon' . I checked the path but found that the correct format of path should be like "voxel2mesh/Chaos/Train_Sets/CT(or MR)/1(or 2,3,4...)/DICOM_anon" .Have you ever met the same error?Do you have any suggestion to deal with this error? |
First, thanks a lot for releasing the code!
During preprocessing of the CHAOS dataset, the xy-slices may get loaded out-of-order since
os.listdir
does not necessarily sort the file names. Specifically, L104 and L152 indata/chaos.py
:voxel2mesh/data/chaos.py
Line 104 in 050a851
voxel2mesh/data/chaos.py
Line 152 in 050a851
This messes up the data since the xy-slices are then in the wrong order. Calling
sorted
onimages_path
seems to fix it.The text was updated successfully, but these errors were encountered: