VMTKSURFACEAPPEND(1)

okay so bestie, welcome to VMTKSURFACEAPPEND(1) ✨ — it's a User Commands manual page, and it's giving pipeline girlie, surface merger, no merges though 🦋 so let's get into it, no cap.

🎀 NAME 🎀

vmtksurfaceappend — it's the vmtk script vmtksurfaceappend. short, sweet, iconic, she said what she said 💅

💅 DESCRIPTION 💅

first things first: this page is auto-generated realness — automatic piping for vmtksurfaceappend, and parsing options for vmtksurfaceappend. that's the boilerplate doing its little warm-up before the main event 🌸

so what does she actually do? vmtksurfaceappend : append two surfaces into a single vtkPolyData. two surfaces in, one vtkPolyData out, main character energy fr fr 👑

⚠️ the way that this matters: the script does not merge coincident points. bestie do NOT come for her about duplicate points, she told you upfront. consider using vmtksurfacetriangle for this. that's the girl for point-merging, iykyk 😭

📥 Input arguments:

• -id Id (str,1); default=0 — the script id 🆔
• -handle Self (self,1) — handle to self, she's holding her own hand, self-care 💖
• -disabled Disabled (bool,1); default=0 — disable execution and piping. like putting her on do-not-disturb 🙈
• -i Surface (vtkPolyData,1) — the input surface 💠
• -ifile SurfaceInputFileName (str,1) — filename for the default Surface reader 📂
• -i2 Surface2 (vtkPolyData,1) — the second input surface, yes she takes two, it's giving duo 💠💠
• -i2file Surface2InputFileName (str,1) — filename for the default Surface2 reader 📂
• -ofile SurfaceOutputFileName (str,1) — filename for the default Surface writer ✍️

📤 Output arguments:

• -id Id (str,1); default=0 — the script id 🆔
• -handle Self (self,1) — handle to self 🫶
• -o Surface (vtkPolyData,1) — the output surface, the final look, the glow-up 🌈⭐

and that's the whole vibe check bestie, you ate it up 🍓 this was vmtksurfaceappend version 1.5, dated April 2026 — go merge some surfaces, or rather, go append them and remember she does not merge coincident points 😌💜