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

The read function in diffdrr.data seems to have a bug. #359

Open
shenao1994 opened this issue Dec 27, 2024 · 2 comments
Open

The read function in diffdrr.data seems to have a bug. #359

shenao1994 opened this issue Dec 27, 2024 · 2 comments

Comments

@shenao1994
Copy link

shenao1994 commented Dec 27, 2024

When I was using version 0.4.2 of diffdrr, I saved the volume in the subject.

data["image"] = subject.volume.data[0].cpu().numpy().astype(np.float32)

And the oriention of the saved CT is consistent. I visualized the CT slices.

GL279_CT_ax_L6
verse008_L1
verse008_L2

But when I use diffdrr versions ≥ 0.4.4, the saved CT directions are inconsistent. As shown in the following figure.

GL279_CT_ax_L6
verse008_L1
verse008_L2

Can you help me check what the problem is ? Thank U !

@eigenvivek
Copy link
Owner

hi @shenao1994 , so just to confirm, when you use diffdrr.data.read with v0.4.2 and v0.4.4+, you get different results?

@shenao1994
Copy link
Author

hi @shenao1994 , so just to confirm, when you use diffdrr.data.read with v0.4.2 and v0.4.4+, you get different results?

Yes. Can you help me check it?

@shenao1994 shenao1994 reopened this Jan 5, 2025
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

2 participants