Skip to content
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

Segmentation Testing #8

Open
liyihao76 opened this issue Apr 17, 2024 · 4 comments
Open

Segmentation Testing #8

liyihao76 opened this issue Apr 17, 2024 · 4 comments

Comments

@liyihao76
Copy link

Hello and thank you for your excellent work. I downloaded and installed the code and tried to follow the process of the demo (default parameters) for bone segmentation inference, but the result is not very satisfactory.
I tested our model using the datasets : SK10(https://ski10.grand-challenge.org/) and SPIDER (https://spider.grand-challenge.org/data/).
I tested 2D slice auto-segmentation and 3D full volume auto-segmentation respectively, but it doesn't seem to work very well. Especially for 3D segmentation, the inference results do not see a continuous structure.
Do I need any other configurations to achieve the desired segmentation results? For example, data preprocessing, inference parameter settings (lower and upper percentile), better checkpoints, manual prompts?

微信图片_20240417144707

微信图片_20240417144748

@Guhanxue
Copy link

Hi, do you mind providing me your MRI sequence information, and sending me an example for each exam if possible that i could do a troubleshooting with you?

@Guhanxue
Copy link

BTW, just through a quick look. I guess the issue might be your data was preprocessed volumes which is not under a meaningful clinical orientation. (such as the x,y,z axis are transposed during dataset sharing.)
For example, A real sagittal view spine usually in:
image, where the spine is vertical in the red window in 3D slicer. I am not sure how much it influence the results, but maybe there is one reason.

@dyollb
Copy link

dyollb commented Jun 2, 2024

I am getting similar (or worse) 3D results for T1 abdominal and head scans and T2 head scans. Is there any pre-processing that I should do to make it work better? e.g.

  • intensity normalization?
  • resampling (expected resolution in mm)?
  • image data orientation (e.g. RAS)?
  • smoothing?

I tested with

  • the amos22 abdominal (ribs+vertebrae) MRI (subject 0579) and
  • IXI head MRI data (subject 025), and both T1 and T2 were acquired using a 1.5T scanner.
    I did n4 bias correction but no other pre-processing.

@Nilser3
Copy link

Nilser3 commented Jun 27, 2024

Hello!

I have similar results

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants