VMTKMESHBRANCHCLIPPER(1)
π VMTKMESHBRANCHCLIPPER π
okay bestie, welcome to vmtkmeshbranchclipper, a vmtk script (manual section 1, user commands, she's that girl) β¨
πΈ NAME πΈ
vmtkmeshbranchclipper β it's a vmtk script, and it's literally called vmtkmeshbranchclipper. iconic naming, no notes π
β¨ DESCRIPTION β¨
So here's the vibe: vmtkmeshbranchclipper does automatic piping and option parsing, which is giving very much "just works, bestie" energy. π«Ά
And here's what she actually does, fr fr:
vmtkmeshbranchclipper : interactively clip a mesh based on proximity to a split and grouped centerline π¦
Lowkey obsessed with that. Okay, now the part you actually came for.
π Input arguments
-idId (str,1); default=0 β script id. it's her little name tag π-handleSelf (self,1) β handle to self. yes she has a handle, she's holding herself together (relatable) π«Ά-disabledDisabled (bool,1); default=0 β disable execution and piping. flip this and she's on strike π-iMesh (vtkUnstructuredGrid,1) β the input mesh, as avtkUnstructuredGrid-ifileMeshInputFileName (str,1) β filename for the default Mesh reader π-centerlinesCenterlines (vtkPolyData,1) β the input centerlines, as avtkPolyData-centerlinesfileCenterlinesInputFileName (str,1) β filename for the default Centerlines reader π-groupidsarrayGroupIdsArrayName (str,1); default=GroupIdsβ name of the array holding the group ids-groupidsGroupIds (int,-1); default=[]β the group ids themselves. an actual empty list, she contains multitudes-insideoutInsideOut (bool,1); default=0 β flip the inside/outside situation π-useradiusUseRadiusInformation (bool,1); default=1 β use the radius info. on by default, she's thorough-radiusarrayRadiusArrayName (str,1); default=MaximumInscribedSphereRadiusβ the name of the radius array-blankingarrayBlankingArrayName (str,1); default=Blankingβ the name of the blanking array-cutoffradiusfactorCutoffRadiusFactor (float,1) >= 0.0; default=1e+16β the cutoff radius factor. must be>= 0.0, and the default is a whole1e+16, which is basically "no cutoff, don't worry about it" π-clipvalueClipValue (float,1); default=0.0 β the clip value-interactiveInteractive (bool,1); default=0 β interactive mode. it's in the name of the script, but the default is0, so she's off unless you say so π-renderervmtkRenderer (vmtkRenderer,1) β external renderer, if you've got one lying around π¨-ofileMeshOutputFileName (str,1) β filename for the default Mesh writer βοΈ-ocenterlinesfileCenterlinesOutputFileName (str,1) β filename for the default Centerlines writer βοΈ
π Output arguments
-idId (str,1); default=0 β script id, again, because she knows you love redundancy π-handleSelf (self,1) β handle to self, again π«Ά-oMesh (vtkUnstructuredGrid,1) β the output mesh, as avtkUnstructuredGrid-ocenterlinesCenterlines (vtkPolyData,1) β the output centerlines, as avtkPolyData
note: the input args and output args both list-idand-handle, and that's fr fr how the page says it. don't come for me, I'm just the messenger π
π SEE ALSO π
there isn't one, bestie. she stands alone. main character energy only π
that's the whole page, no cap. this was vmtkmeshbranchclipper version 1.5, April 2026, straight from the VMTKMESHBRANCHCLIPPER(1) manual page footer β she ate and left no crumbs πβ¨ bye bestie, go clip something π
π¦ 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