VMTKSURFACEBOOLEANOPERATION(1)

πŸ“¦ version 1.5.0, in ubuntu stonking

πŸ’– NAME πŸ’–

vmtksurfacebooleanoperation β€” bestie, it's a vmtk script, and yes the script is literally just called vmtksurfacebooleanoperation, we're keeping it πŸ’…


✨ DESCRIPTION ✨

okay so listen. vmtksurfacebooleanoperation does automatic piping, and it does it so well. Not to be that girl but the vibes here are: the script parses your options, sets up the piping, and handles all the vmtksurfacebooleanoperation business for you. no cap. 🫢

here's the whole deal, in one breath:

vmtksurfacebooleanoperation : perform a boolean operation between two

  • surfaces

fr fr, that's the entire assignment. two surfaces walk in, one surface walks out. main character energy πŸ‘‘


🧚 Input arguments:

  • -id Id (str,1); default=0 β€” the script id, iykyk ✨
  • -handle Self (self,1) β€” handle to self, it's giving very self-aware of it tbh πŸͺž
  • -disabled Disabled (bool,1); default=0 β€” flip this and you disable execution and piping. like, it just stops doing the thing. lowkey useful, highkey chaotic πŸ™ˆ
  • -i Surface (vtkPolyData,1) β€” the input surface. this is surface number one, the moment πŸ’–
  • -ifile SurfaceInputFileName (str,1) β€” filename for the default Surface reader πŸ“–
  • -i2 Surface2 (vtkPolyData,1) β€” the second input surface. yes bestie, you need two, it's a two surface kind of operation πŸ¦‹
  • -i2file Surface2InputFileName (str,1) β€” filename for the default Surface2 reader πŸ“–
  • -tolerance Tolerance (float,1) >= 0.0; default=1e-06 β€” the tolerance for considering two points coincident. so like, how close do two points gotta be before we're like "okay same point, periodt"? that's this number. and it's gotta be >= 0.0, no negatives, we don't do that here βœ‹
  • -operation Operation (str,1) in ['union', 'intersection', 'difference']; default=union β€” the boolean operation to be performed. union, intersection, or difference, pick your fighter 🌈
  • -method Method (str,1) in ['default', 'loop']; default=default β€” the method used for the boolean operation πŸ”₯
  • -ofile SurfaceOutputFileName (str,1) β€” filename for the default Surface writer ✍️

πŸŽ€ Output arguments:

  • -id Id (str,1); default=0 β€” the script id (yes again, she contains multitudes)
  • -handle Self (self,1) β€” handle to self (also again, obsessed with the consistency)
  • -o Surface (vtkPolyData,1) β€” the output surface. THE moment. the glow-up. the one that gets written out πŸ’–βœ¨
ngl bestie, if you're piping these scripts together, remember -id, -handle and -disabled show up in both the input and output lists, and that's not a typo, that's just how the piping works. 🫢

that's the whole page, and you ate it πŸ“

sign-off time: this was vmtksurfacebooleanoperation, version 1.5, dated April 2026, and the manual page header/footer situation was literally just the title and the version doing a little mirror thing on either end. slay. πŸ’œ

πŸ“¦ where this page comes from