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

How to define proton range(R80)? #570

Open
MPstudentMU opened this issue Jul 18, 2022 · 4 comments
Open

How to define proton range(R80)? #570

MPstudentMU opened this issue Jul 18, 2022 · 4 comments

Comments

@MPstudentMU
Copy link

MPstudentMU commented Jul 18, 2022

Dear all

I’m a master degree student in medical physic. I would like to define R80 in proton planning from matrad. So, I curious that can I define R80 from the dose profile? And Could you give any suggestions for validating the result?

Regards

@wahln
Copy link
Contributor

wahln commented Jul 21, 2022

What do you mean with

I would like to define R80 in proton planning from matrad?

The range is given in the base data or can be computed with the range-energy-relation? Or do you want to find it in a heterogeneous 3D dose distribution?

@MPstudentMU
Copy link
Author

Thank you for your answer, I mean I would like to find the range in heterogeneous 3D dose distribution, like in real patient data. Dose it can find from this dose profile that created from the matRad plan ?
dose profile water - box phantom
.

@wahln
Copy link
Contributor

wahln commented Aug 2, 2022

Okay, but there should be more than one range in this picture, right? Because the SOBP is composed of multiple bragg-peaks of different energies and thus different ranges. So you could detect the distal edge, i.e. using the profiles above - is that what you want?

@MPstudentMU
Copy link
Author

I greatly appreciate it. I have a small question I would want to ask you. Does this profile result from the center of the beam direction?

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

No branches or pull requests

2 participants