-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Regarding the quality issues of the DRR image. #344
Comments
Hi @linquanxu, a few things I would try:
Hope that helps, let me know if you have further questions! |
Hi, @eigenvivek,
How should I set the parameters to make the generated DRR image as close as possible to the real X-ray image? Should I fully follow the parameters of the real X-ray equipment in this case? |
Yes, follow the parameters of the real X-ray for your DRR.
Real X-rays are very large, and rendering a DRR that big will likely use more memory than you have on your GPU. To overcome this, you can downsample the detector ( |
Thank you for your help, I'll try again. |
Hi, I hope this worked out for you! Although this issue is closed, I wanted to share my experience in case others come across this in the future. I faced the same problem where the X-rays appeared extremely low-quality and blurry. Instead of adjusting the spacing, I found that modifying the bone_intensity_multiplier during subject reading significantly improved the image detail. Specifically, using a multiplier of 5–10 resulted in much clearer X-rays. Here’s how I applied this in my case: |
Dear author,
I used this code to generate DRR images, but I found that the generated DRR image is very different from the real X-ray image. The generated DRR image is very blurry, while the real X-ray image is much clearer. Could you please help me understand what might be causing this issue? Below are the generated images and the code.
Additionally, in the DRR image, the area I marked in red appears abnormal. What could be causing this issue?
Lastly, I have attached the real X-ray image below:

The text was updated successfully, but these errors were encountered: