You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original request by Matteo Ravasi as discussed on scipy-dev mailing list:
Hi Sebastian,
I also looked into your package, ans I agree it would be a very nice
addition to scipy.
Just one question: in tomography it is common to know the start and
end points of a ray and they may lie somewhere inside the grid extent.
In your library I seem to be able to only have rays that cross
straight through the grid as they can only be parametrized by only
their support and angle. While this parametrization can be inferred
from start-end point, being able to have rays within (but not all the
way through the grid) would definitely make your routine more general
and applicable to various problems - then more suited to scipy.
Am I missing anything? Or do you think this feature could be easily
added without changing the current code base too much?
Thank you!
The text was updated successfully, but these errors were encountered:
you got it right. There is no start-point, and end-point in ray_voxel_overlap. I would have to write a unit-test to figure out if one has control over the start-point using the support-vector, but I did not implement the concept of an end-point. So this is a feature-request. I will put in on git-hub.
These are 8 floats in total.
start-point = support-vector + start-parameter * direction-vector
end-point = support-vector + end-parameter * direction-vector
Possible defaults might be
start-parameter = -inf,
end-parameter = +inf
Now it should behave as before.
Advantage: Not much change in interface.
Proposal 2
start-vector,
end-vector,
Only 6 floats in total.
User might have to separate the start-vector and end-vector manually in order to approximate an infinite ray in case the user does not want start-points, and end-points.
Original request by Matteo Ravasi as discussed on scipy-dev mailing list:
The text was updated successfully, but these errors were encountered: