VMTKBRANCHSECTIONS(1)

💖 NAME 💖

vmtkbranchsections — the vmtk script literally named vmtkbranchsections. One (1) manual page, filed under User Commands, and yes bestie we are reading it together, grabbing a lil snack first 🍓

✨ DESCRIPTION ✨

Okay so here's the auto-generated opener, exactly as the script spits it out, no notes: "Automatic piping vmtkbranchsections Parsing options vmtkbranchsections" — that's the piping-and-parsing boilerplate, it's giving robot voice, we respect it 💀

Now the real tea: vmtkbranchsections : compute geometric properties of branch sections located a fixed number of spheres away from each bifurcation. The script takes in input the surface and the relative centerlines, both already split into branches — like, that part is not optional, they come pre-split, okay? 🦋

🎀 Input arguments 🎀

• -id — Id (str,1); default=0: the script id. every script has one, it's their lil name tag 🪪
• -handle — Self (self,1): handle to self. it's the handle to self, iykyk
• -disabled — Disabled (bool,1); default=0: set this and execution and piping are just… off. nothing runs. silence 💀
• -i — Surface (vtkPolyData,1): your input surface — and it must already be split into branches, we said what we said
• -ifile — SurfaceInputFileName (str,1): the filename for the default Surface reader
• -centerlines — Centerlines (vtkPolyData,1): the input centerlines — also already split into branches ✨
• -centerlinesfile — CenterlinesInputFileName (str,1): the filename for the default Centerlines reader
• -distancespheres — NumberOfDistanceSpheres (int,1) >= 0; default=1: how far away from the bifurcation the sections get taken, measured in number of inscribed spheres, where each sphere touches the center of the previous one 🫧 obsessed with the geometry of it tbh
• -reverse — ReverseDirection (bool,1); default=0: toggle it and sections start generating from the end of the branches instead of the start. lil direction flip 🔁
• -radiusarray — RadiusArrayName (str,1); default=MaximumInscribedSphereRadius: the array where the centerline radius is stored
• -groupidsarray — GroupIdsArrayName (str,1); default=GroupIds: the array where centerline group ids are stored
• -centerlineidsarray — CenterlineIdsArrayName (str,1); default=CenterlineIds: the array where centerline ids are stored
• -tractidsarray — TractIdsArrayName (str,1); default=TractIds: the array where centerline tract ids are stored
• -blankingarray — BlankingArrayName (str,1); default=Blanking: the array where the centerline blanking information about branches is stored
• -branchsectiongroupids — BranchSectionGroupIdsArrayName (str,1); default=BranchSectionGroupIds: the array where the group id that each section belongs to has to be stored
• -branchsectionarea — BranchSectionAreaArrayName (str,1); default=BranchSectionArea: the array where the area of bifurcation sections has to be stored
• -branchsectionminsize — BranchSectionMinSizeArrayName (str,1); default=BranchSectionMinSize: the array where the minimum diameter of each section has to be stored
• -branchsectionmaxsize — BranchSectionMaxSizeArrayName (str,1); default=BranchSectionMaxSize: the array where the maximum diameter of each bifurcation section has to be stored
• -branchsectionshape — BranchSectionShapeArrayName (str,1); default=BranchSectionShape: the array where the shape index has to be stored — and the shape index is, and I quote, the ratio between minimum and maximum diameter, of each bifurcation section 📐
• -branchsectionclosed — BranchSectionClosedArrayName (str,1); default=BranchSectionClosed: the array containing 1 if a section is closed and 0 otherwise. binary icon behavior
• -branchsectiondistancespheres — BranchSectionDistanceSpheresArrayName (str,1); default=BranchSectionDistanceSpheres: the array containing the number of distance spheres the section is taken at
• -ofile — BranchSectionsOutputFileName (str,1): the filename for the default BranchSections writer

🌈 Output arguments 🌈

• -id — Id (str,1); default=0: script id. yes again. it comes in and it goes out 🪪
• -handle — Self (self,1): handle to self. also again. consistency queen 👑
• -o — BranchSections (vtkPolyData,1): the output sections, bestie, the whole point, the main character 🎀
• -branchsectiongroupids — BranchSectionGroupIdsArrayName (str,1); default=BranchSectionGroupIds: the array where the group id to which each section belongs are stored
• -branchsectionarea — BranchSectionAreaArrayName (str,1); default=BranchSectionArea: the array where the area of bifurcation sections are stored
• -branchsectionminsize — BranchSectionMinSizeArrayName (str,1); default=BranchSectionMinSize: the array where the minimum diameter of each section are stored
• -branchsectionmaxsize — BranchSectionMaxSizeArrayName (str,1); default=BranchSectionMaxSize: the array where the minimum diameter of each bifurcation section has to be stored (yes, the docs say minimum here in the output list, we are simply reporting what it says, don't shoot the messenger 🙈)
• -branchsectionshape — BranchSectionShapeArrayName (str,1); default=BranchSectionShape: the array where the shape index — that's the ratio between minimum and maximum diameter — of each bifurcation section are stored
• -branchsectionclosed — BranchSectionClosedArrayName (str,1); default=BranchSectionClosed: the array containing 1 if a section is closed and 0 otherwise
• -branchsectiondistancespheres — BranchSectionDistanceSpheresArrayName (str,1); default=BranchSectionDistanceSpheres: the array containing the number of distance spheres the section is taken at

💡 tiny heads-up bestie: a bunch of these names appear once in Input arguments and again in Output arguments. Same flags, same defaults — that's just how the page lists them. Don't @ me, @ the manpage.

and that's the whole page, we ate, no crumbs left 🌸

sign-off: this was vmtkbranchsections version 1.5, fresh out of April 2026 💅 slay, go split some branches (remember: already split 😭), periodt 🫶