VMTKBRANCHCLIPPER(1)
π NAME π
So like, this is the manual page for vmtkbranchclipper β yeah, that's a whole mouthful β and it's here to tell you that vmtkbranchclipper is a vmtk script. That's the vibe. The manual's own name is VMTKBRANCHCLIPPER(1) and it lives in the User Commands section, just so you know where you are. π
β¨ DESCRIPTION β¨
Okay so boom, here's the whole tea: Automatic piping vmtkbranchclipper Parsing options vmtkbranchclipper. Yeah, that's literally what the page says, I'm not even joking, that's the script being an icon and announcing itself. π
And then the actual point of the whole thing:
vmtkbranchclipper : divide a surface in relation to its split and grouped centerlines
That's it. That's the mission. Surface goes in, surface gets chopped up according to its split + grouped centerlines. Iconic behavior honestly. π
π«Ά Input arguments:
Okay bestie, this is the long list, but it's not scary, it's just thorough. Every single one of these is here, no skipping, no cap:
-idId(str,1); default=0β script id. Yeah it's the script's little nametag. π-handleSelf(self,1)β handle to self. It's holding its own hand, cute.-disabledDisabled(bool,1); default=0β disable execution and piping. Flip this and it justβ¦ does nothing. Respect.-iSurface(vtkPolyData,1)β the surface. The main character, literally. π-ifileSurfaceInputFileName(str,1)β filename for the default Surface reader. So it knows where to read your surface from. π-centerlinesCenterlines(vtkPolyData,1)β the centerlines. The other main character. π-centerlinesfileCenterlinesInputFileName(str,1)β filename for the default Centerlines reader.-groupidsarrayGroupIdsArrayName(str,1); default=GroupIdsβ the name of the group ids array.-groupidsGroupIds(int,-1); default=[]β the group ids themselves. Empty list by default, come on, give it something. π-insideoutInsideOut(bool,1); default=0β flip it and everything's inside out, like your brain at 3am.-useradiusUseRadiusInformation(bool,1); default=1β yep, use that radius info, it's on by default, slay.-radiusarrayRadiusArrayName(str,1); default=MaximumInscribedSphereRadiusβ the radius array's name. Yes, that whole long name is the default. π-blankingarrayBlankingArrayName(str,1); default=Blankingβ the blanking array's name.-cutoffradiusfactorCutoffRadiusFactor(float,1) >= 0.0; default=1e+16β has to be>= 0.0, and defaults to an absolutely feral1e+16. She's big. π-clipvalueClipValue(float,1); default=0.0β the clip value. Zero by default, neutral queen. β¨-interactiveInteractive(bool,1); default=0β turn on interactive mode if you wanna poke at it live.-renderervmtkRenderer(vmtkRenderer,1)β external renderer. Bring your own, iykyk.-ofileSurfaceOutputFileName(str,1)β filename for the default Surface writer.-ocenterlinesfileCenterlinesOutputFileName(str,1)β filename for the default Centerlines writer.
π¦ Output arguments:
Now the part where it gives you stuff back. Not me being excited about return values but like, here we are:
-idId(str,1); default=0β script id. Yeah it's here twice, in and out, she contains multitudes.-handleSelf(self,1)β handle to self. Again. Self-love fr fr. π-oSurface(vtkPolyData,1)β boom, your surface, processed and delivered. π₯-ocenterlinesCenterlines(vtkPolyData,1)β and your centerlines too, matching set, adorable.
Heads up bestie: this page doesn't hand you extra examples, exit statuses, environment variables or SEE ALSO references β what you see up there is the whole plate, so I'm not gonna invent any at you. No fake facts on my watch. π
Okay that's the whole page, you understood all of it, I'm so proud of you. This lil manual belongs to vmtkbranchclipper version 1.5, dated April 2026 β shoutout to the version number and the date, you did amazing sweetie πβ¨π«Ά
π¦ where this page comes from
- ubuntu stonking: vmtk 1.5.0+dfsg1-1 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms