VMTKSURFACECLIPLOOP(1)

💖 NAME 💖

vmtksurfacecliploop — bestie, it's a vmtk script, and its whole name is literally vmtksurfacecliploop, no cap ✨

✨ DESCRIPTION ✨

Okay so picture this: it's automatic piping, right? The script vmtksurfacecliploop does its parsing-options thing like every good vmtk script does, and it's lowkey iconic about it 🎀

So what does vmtksurfacecliploop actually do? It clips the input surface using a loop. That's the vibe. That's the whole main character moment 👑

Heads up bestie — the options below are split into two little groups, and yes, -id and -handle show up in both of them. That's not a typo, that's just how it is 🙈

🌸 Input arguments 🌸

• -id Id (str,1); default=0 — the script id 💅
• -handle Self (self,1) — a handle to self, it's giving self-care fr 🪞
• -disabled Disabled (bool,1); default=0 — turn this on and it disables execution and piping 🚫
• -i Surface (vtkPolyData,1) — the input surface 🦋
• -ifile SurfaceInputFileName (str,1) — the filename for the default Surface reader 📄
• -i2 Loop (vtkPolyData,1) — the input loop 🌀
• -i2file LoopInputFileName (str,1) — the filename for the default Loop reader 📄
• -ofile SurfaceOutputFileName (str,1) — the filename for the default Surface writer ✍️

🦋 Output arguments 🦋

• -id Id (str,1); default=0 — the script id, again, she's back 💖
• -handle Self (self,1) — a handle to self, yep, also back 🪞
• -o Surface (vtkPolyData,1) — the output surface, the glow-up of your input 🌈

Okay that's literally the entire page, bestie, not me getting emotional over a manpage 😭 This was vmtksurfacecliploop version 1.5, dated April 2026 — go clip some surfaces, slay, and remember: keep every flag exactly where it is, periodt 💅✨🎀