Potential issue in case A_172_frames2
Thanks for organizing the great challenge!
Here is the screenshot of case A_172_frames2. Is this the expected image?
Thanks a lot for the feedback!
This is not expected. The original image seems to be corrupted, therefore I have deleted this .mha and corresponding frame-rate and scanned-region .json files. Let us know if there are any more issues!
Hi @elialombardo ,
Sorry for bothering you during weekend.
A_172_frames3.mha has the same issue.
Also for A_073_frames4
I found these cases when randomly open the cases. It would be great if you could check the whole dataset.
A potential way to do this efficiently:
- save the 1st frame of each case as a jpg image
- merge every 100 images as a 10x10 big image (show the image name on each thumbnail image)
Thanks for pointing this out.
I just went through all the first frames of each scan in the unlabeled cohort visually and found another six scans for which the data was corrupted. I've deleted the scans and the correpsonding jsons and updated the dataset.
Please let me know if you find any more issues!