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

Catphan CTP404 slice thickness #368

Open
jmbm94 opened this issue Apr 14, 2021 · 2 comments
Open

Catphan CTP404 slice thickness #368

jmbm94 opened this issue Apr 14, 2021 · 2 comments

Comments

@jmbm94
Copy link

jmbm94 commented Apr 14, 2021

Hi,
I've a problem with the parameter, slice thickness, in Catphan600's analysis. The correct value should be double of the value that I obtain.
I suposse that the problem is in the function:
' def meas_slice_thickness(self):
return np.mean(sorted(roi.wire_fwhmself.mm_per_pixel0.42 for roi in self.thickness_rois.values()))/(1+2*self.pad)'

Thanks!

@jrkerns
Copy link
Owner

jrkerns commented Apr 14, 2021

Hi jmbm94,
Can you provide a little more information? Have you tried in another QA program? What are the actual values? If you know the correct value then it sounds like you don't need any measurements; you can simply double the value pylinac provides.

@jmbm94
Copy link
Author

jmbm94 commented Apr 15, 2021

Yes, I do. I tried it with AutoQA Lite and this parameter is introduced in CT by me, so I know the actual value.
It's a bit strange because, using the same protocol and phantom but different acquisitions, the result sometimes is evaluated correctly but other times gives a wrong value. The different acquisition were performed without changing the phantom position.
Sorry about the previous post, when I said 'The correct value should be double of the value that I obtain', it was wrong. I have performed more acquisitions and the measurement of the slice thickness is not always the half value of the nominal value.

jrkerns added a commit that referenced this issue Apr 8, 2024
RAM-3475 Add bb shift vector for multi-met

Approved-by: Randy Taylor
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants