VMTKSURFACECLIPPER(1)
π NAME π
okay so bestie, meet vmtksurfaceclipper β the vmtk script vmtksurfaceclipper. that's it, that's the name, we're starting strong π«Ά
β¨ DESCRIPTION β¨
Automatic piping vmtksurfaceclipper. Parsing options vmtksurfaceclipper. (yes, that's literally what it does under the hood, it's giving very "the code explains itself" energy π)
vmtksurfaceclipper β interactively clip a surface with a box. iconic behavior honestly π
π₯ Input arguments π
-idId (str,1); default=0β script id, it's the little name tag your script wears β¨-handleSelf (self,1) β handle to self, aka a lil handshake back to the object itself π«Ά-disabledDisabled (bool,1); default=0β disable execution and piping. flip it and the whole thing justβ¦ doesn't π-iSurface (vtkPolyData,1) β the input surface, the main character of this whole operation π-ifileSurfaceInputFileName (str,1) β filename for the default Surface reader, so it knows where to look π-typeWidgetType (str,1) in['box', 'sphere']; default=boxβ type of widget used for clipping. box or sphere, pick your fighter π₯-transformTransform (vtkTransform,1) β the widget transform, useful in case of piping of multiple clipping scripts. lowkey the MVP when you're chaining stuff π₯-cleanoutputCleanOutput (bool,1); default=1β toggle cleaning the unused points. bye bye stray points, no crumbs left π§Ήβ¨-insideoutInsideOut (bool,1); default=0β toggle switching output and clipped surfaces, it flips the whole vibe upside down π-interactiveInteractive (bool,1); default=1β toggle clipping with a widget or with a pre-defined scalar field. widget mode vs scalar mode, choose your destiny π-arrayClipArrayName (str,1); default=Noneβ name of the array with which to clip in case of non-interactive clipping π-valueClipValue (float,1); default=0.0β scalar value at which to perform clipping in case of non-interactive clipping π―-renderervmtkRenderer (vmtkRenderer,1) β external renderer, for when you already have one and don't need a new one, we love a reuse moment β»οΈ-ofileSurfaceOutputFileName (str,1) β filename for the default Surface writer πΎ-oclippedfileClippedSurfaceOutputFileName (str,1) β filename for the default ClippedSurface writer βοΈ-ocutlinesfileCutLinesOutputFileName (str,1) β filename for the default CutLines writer π
no cap, that's every single input flag. count them. all sixteen. i checked twice bestie π«‘
π€ Output arguments π
-idId (str,1); default=0β script id, same lil name tag energy β¨-handleSelf (self,1) β handle to self π«Ά-oSurface (vtkPolyData,1) β the output surface, freshly clipped and gorgeous πΈ-oclippedClippedSurface (vtkPolyData,1) β the clipped surface, the part that got yeeted off βοΈ-ocutlinesCutLines (vtkPolyData,1) β the cutlines, the lil scar where the cut happened π-otransformTransform (vtkTransform,1) β the output widget transform, so you can carry that placement onward π₯
fr fr that's the whole page, nothing skipped, nothing invented, facts fully intact π§
this was vmtksurfaceclipper version 1.5 from April 2026, floating around in the User Commands section of the manual. periodt. πβ¨π
π¦ 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