Daniel, Thanks for the links. Unfortunately, the Slicer module just finds the centerline, but doesn't seem to do anything else other than create a Slicer object from the polydata.
I'm able to extract the centerline using vtkvmtkPolyDataCenterlines, can extract the branches using vtkvmtkCenterlineBranchExtractor, and even clip the surface using vtkvmtkPolyDataCenterlineGroupsClipper -- these all work as advertised, and I'm able to get the results to display inside my VTK view. What I'm having trouble now is taking the output of vtkvmtkCenterlineBranchExtractor and finding which of the branches are connected to each other. I can find each vtkPolyLine object that represents each part of the branch, but it seems to me that vtkvmtkCenterlineUtilities::FindAdjacentCenterlineGroupIds(..) is giving the wrong results. Thanks again, Simon Wilson (ps sorry for the original double-post) On 23/05/2011, at 11:43 PM, Daniel Haehn wrote: > Hi Simon, > > you should take a look at > > http://www.vmtk.org/Main/VmtkIn3DSlicer > http://www.slicer.org/slicerWiki/index.php/Modules:VMTKCenterlines > > This is a GUI for the Centerlines Computation as a 3D Slicer module. > It is all open source so you could easily get inspired on how to get > the centerlines tree: > http://www.nitrc.org/plugins/scmsvn/viewcvs.php/VMTKCenterlines/?root=slicervmtklvlst > > Cheers, > Daniel > > On Mon, May 23, 2011 at 2:32 AM, Simon Wilson <s.wils...@uq.edu.au> wrote: >> Hi all, >> >> I've just started working with VMTK again after a long hiatus, and have >> started integrating the C++ classes into an application. My goal is to >> obtain the centreline topology, so that I can build a UI around this to >> allow for interactive segmentation. >> >> I found the method >> vtkvmtkCenterlineUtilities::FindAdjacentCenterlineGroupIds(...), which I >> thought would give me the full connected tree, but it doesn't seem to work >> that way. >> >> I have a simple structure of a single vessel that branches into two smaller >> vessels in a Y-shape. From this, vtkvmtkCenterlineBranchExtractor finds a >> total of 6 segments, but after calling FindAdjacentCenterlineGroupIds(), two >> of these branches are "orphaned" -- they have no upstream and no downstream >> groups. These both correspond to two parts of one branch, distal to the >> bifurcation. >> >> The other oddity I've noticed is that, from the group that has the >> bifurcation in it (1 upstream, 2 downstream groups), the branch which has >> the two orphaned segments attaches another copy of the proximal part instead >> of the orphaned branches. I've noticed there are methods within >> vtkvmtkCenterlineUtilities for "unique" group IDs, but I've yet to try this >> out. >> >> In short, how should I go about constructing the topology of the centerline? >> Ideally, I just need 3 segments (the common proximal part, and the two >> distal branches from the bifurcation), though I can deal with additional >> "inter-bifurcation" parts if there's no other way. >> >> Thanks, >> >> Simon Wilson >> ------------------------------------------------------------------------------ >> What Every C/C++ and Fortran developer Should Know! >> Read this article and learn how Intel has extended the reach of its >> next-generation tools to help Windows* and Linux* C/C++ and Fortran >> developers boost performance applications - including clusters. >> http://p.sf.net/sfu/intel-dev2devmay >> _______________________________________________ >> vmtk-users mailing list >> vmtk-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/vmtk-users >> ------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 _______________________________________________ vmtk-users mailing list vmtk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vmtk-users
