VMTKMESHCLIPPER(1)

πŸ“¦ version 1.5.0, in ubuntu stonking

πŸ’– VMTKMESHCLIPPER πŸ’–

okay so bestie, welcome to vmtkmeshclipper β€” it's a vmtk script and it lives in the User Commands section, and honestly? it's giving "cut a mesh with a box, but make it interactive." πŸŽ€


✨ NAME ✨

vmtkmeshclipper β€” literally a vmtk script called vmtkmeshclipper, no notes. πŸ’…


🌸 DESCRIPTION 🌸

Automatic piping. vmtkmeshclipper parses all your options, and like… that's the whole gig. ✨

vmtkmeshclipper : interactively clip a mesh with a box πŸ”₯

🧚 Input arguments 🧚

  • -id Id (str,1); default=0 β€” the script id. that's it, that's the vibe.
  • -handle Self (self,1) β€” a handle to self. yes queen, know thyself πŸ’…
  • -disabled Disabled (bool,1); default=0 β€” turns off execution and piping at the same time. one switch, two consequences, iconic.
  • -i Mesh (vtkUnstructuredGrid,1) β€” the input mesh. the main character of this whole operation, fr.
  • -ifile MeshInputFileName (str,1) β€” filename for the default Mesh reader, so it knows where to read from.
  • -insideout InsideOut (bool,1); default=0 β€” toggles switching the output and clipped surfaces. swap 'em around, why not πŸ¦‹
  • -interactive Interactive (bool,1); default=1 β€” toggles clipping with a widget vs. clipping with a pre-defined scalar field. two paths, one flag.
  • -array ClipArrayName (str,1); default=None β€” the name of the array to clip with when you're doing non-interactive clipping.
  • -value ClipValue (float,1); default=0.0 β€” the scalar value where the clipping happens, in the non-interactive case.
  • -renderer vmtkRenderer (vmtkRenderer,1) β€” an external renderer, for when you've got your own.
  • -ofile MeshOutputFileName (str,1) β€” filename for the default Mesh writer.
  • -osurfacefile SurfaceOutputFileName (str,1) β€” filename for the default Surface writer.
  • -oclippedfile ClippedMeshOutputFileName (str,1) β€” filename for the default ClippedMesh writer.

🫢 Output arguments 🫢

  • -id Id (str,1); default=0 β€” the script id again. yes, it shows up in both lists. let it live 😭
  • -handle Self (self,1) β€” handle to self again. same energy.
  • -o Mesh (vtkUnstructuredGrid,1) β€” the output mesh πŸ’–
  • -osurface Surface (vtkPolyData,1) β€” the output surface corresponding to the cut βœ‚οΈ
  • -oclipped ClippedMesh (vtkUnstructuredGrid,1) β€” the clipped mesh πŸ‘‘
ngl bestie, three outputs means three files if you want 'em β€” -ofile, -osurfacefile and -oclippedfile are right there. no cap.

and that's the whole page, short and slay 🌈

this lil cutie is vmtkmeshclipper version 1.5, dated April 2026, and it rolled in as part of the User Commands crew. love that for us πŸ’œβœ‚οΈπŸ’–

πŸ“¦ where this page comes from