kernel of DigitalSubtractionAngiographyVesselPath.ipynb dies for different path points

[IsabellaPa]

Hello,
I was playing around with the DigitalSubtractionAngiographyVesselPath.ipynb example and noticed that if I change the path file to other points, a lot of times the kernel dies at the last view function (view(dsa, geometries=path, ui_collapsed=True)).
When I use my own image, which is smaller, I am completely unable to find a combination of points that works.
I moved the code to VS Code in hope that I would get an error message but the script just stops executing in the view function after the viewer is initialized.

Here are some examples of paths that failed for me:
Path: [394.00, 203.00] [0.00, 0.00]
Path: [394.00, 203.00] [1.00, 20.00]
Path: [394.00, 203.00] [001.00, 020.00]
Path: [94.00, 203.00] [60.00, 230.00] [250.00, 190.00]
Path: [204.00, 23.00] [120.00, 80.00] [273.00, 19.00] [94.00, 173.00] [394.00, 121.00] [403.00, 237.00]

Apparently the view function is not the problem but the value for path.GetVertexList().Size() is 0 for the paths.

The original path in the example works fine, so I don't think that it is a setup problem.
Can I debug this somehow, are there restrictions for possible points or is this a bug?

Cheers :)

[aylward]

Hi,

Sorry that you're having troubles, and sorry for the delay in responding.

I think the problem may be that some of your paths are not supported by the speed image. For example, in the image [0,0] is far into the background, instead of being part of a vessel connected to the vessel point [394,203]. Similarly, points [1,20] and [250,190] are in the background.

I just tested with a new path file with the line
Path: [394.00, 203.00] [379.00, 233.00]
and it works as expected.

The first point is the x,y coordinate of the starting point. The last point is the x,y coordinate of the end point. Any points in between are intermediate points that should be used to help guide / disambiguate the path that connects the start end end points. The path that connects all of these points must be connected by non-zero pixels in the speed image. If there is no "easy" path between the points that follows non-zero speed pixels, it will (appropriately) fail and return a 0 length (0 size) path as the solution for connecting those points.

Hope this helps.