VMTKPYTHONSCRIPT(1)

πŸ“¦ version 1.5.0, in ubuntu stonking

✨ NAME ✨

vmtkpythonscript β€” the vmtk script called vmtkpythonscript πŸ’…

okay so listen bestie, this is the manual page for vmtkpythonscript, a User Command from the vmtk family. yes it's giving "another vmtk script", but it's literally the one that runs your Python script, so it's kind of the main character. πŸ’–


πŸ¦‹ DESCRIPTION πŸ¦‹

Automatic piping vmtkpythonscript ✨ Parsing options vmtkpythonscript ✨

that's the whole vibe: this thing autopipes itself around and parses its own options like it's no big deal. no cap.

vmtkpythonscript : execute a python script contained in a file 🐍

like. you hand it a file with Python in it, and it runs it. that's the whole plot. periodt.


🌸 Input arguments 🌸

these are the things you feed it, bestie. one by one, no skipping. πŸ‘‘

  • -id, Id (str,1); default=0 β€” the script id 🏷️
  • -handle, Self (self,1) β€” handle to self 🫢
  • -disabled, Disabled (bool,1); default=0 β€” disable execution and piping πŸ™ˆ (yeah, turn it on to turn it off, iykyk)
  • -image, Image (vtkImageData,1) β€” the input image πŸ–ΌοΈ
  • -imagefile, ImageInputFileName (str,1) β€” filename for the default Image reader πŸ“‚
  • -image2, Image2 (vtkImageData,1) β€” the second input image πŸ–ΌοΈβœ¨
  • -image2file, Image2InputFileName (str,1) β€” filename for the default Image2 reader πŸ“‚
  • -surface, Surface (vtkPolyData,1) β€” the input surface 🌊
  • -surfacefile, SurfaceInputFileName (str,1) β€” filename for the default Surface reader πŸ“‚
  • -surface2, Surface2 (vtkPolyData,1) β€” the second input surface 🌊✨
  • -surface2file, Surface2InputFileName (str,1) β€” filename for the default Surface2 reader πŸ“‚
  • -mesh, Mesh (vtkUnstructuredGrid,1) β€” the input mesh πŸ•ΈοΈ
  • -meshfile, MeshInputFileName (str,1) β€” filename for the default Mesh reader πŸ“‚
  • -mesh2, Mesh2 (vtkUnstructuredGrid,1) β€” the second input mesh πŸ•ΈοΈβœ¨
  • -mesh2file, Mesh2InputFileName (str,1) β€” filename for the default Mesh2 reader πŸ“‚
  • -scriptfile, PythonScriptFileName (str,1) β€” the name of the file were the Python script resides πŸ“œ (yes, "were". the original said "were". we are not fixing it. that's canon. πŸŽ€)
  • -oimagefile, ImageOutputFileName (str,1) β€” filename for the default Image writer πŸ’Ύ
  • -osurfacefile, SurfaceOutputFileName (str,1) β€” filename for the default Surface writer πŸ’Ύ
  • -omeshfile, MeshOutputFileName (str,1) β€” filename for the default Mesh writer πŸ’Ύ

πŸ’œ Output arguments πŸ’œ

and these are the things it hands back to you, slay. πŸ‘‘

  • -id, Id (str,1); default=0 β€” the script id 🏷️
  • -handle, Self (self,1) β€” handle to self 🫢
  • -oimage, Image (vtkImageData,1) β€” the output image πŸ–ΌοΈπŸ’–
  • -osurface, Surface (vtkPolyData,1) β€” the output surface πŸŒŠπŸ’–
  • -omesh, Mesh (vtkUnstructuredGrid,1) β€” the output mesh πŸ•ΈοΈπŸ’–

bestie reminder: -id and -handle show up twice, once in the input list and once in the output list, with the exact same descriptions. that's not a glitch, that's just how the pipe do. πŸ”₯

k that's the whole page πŸŽ€ every last flag, default, type and filename is right there, no details ghosted, fr fr. this was vmtkpythonscript version 1.5, dated April 2026 β€” written up as a User Command entry, and ngl she ate. πŸ’…βœ¨πŸ¦‹πŸ‘‘

πŸ“¦ where this page comes from