VMTKMESHBOUNDARYINSPECTOR(1)

💖 NAME 💖

vmtkmeshboundaryinspector — bestie, it's a vmtk script, and its whole government name is also vmtkmeshboundaryinspector. Iconic of it, honestly.

✨ DESCRIPTION ✨

okay so. Automatic piping, yes bestie, vmtkmeshboundaryinspector has it. Parsing options? Also yes, vmtkmeshboundaryinspector is out here parsing options like it's nothing, because that is literally the vibe of this whole script. The way that it just… does both. Obsessed.

And here's the main character energy part: vmtkmeshboundaryinspector displays a 3D render of the mesh, with individual boundary groups colored and labeled. Like, each boundary group gets its own lil outfit (a color) and its own lil nametag (a label). You just get to look at them. Fr fr, it's a little fashion show for your boundaries. 👑

🎀 Input arguments 🎀

these are the ones you feed in, the givers, the main characters of the input department:

• -id Id (str,1); default=0 — this is the script id, bestie. It defaults to 0, because of course it does.
• -handle Self (self,1) — the handle to self. It's giving self-awareness. It's giving knowing who it is.
• -disabled Disabled (bool,1); default=0 — a bool that disables execution and piping. Default is 0, i.e. not disabled, i.e. we're running, we're doing the thing. 🏃‍♀️
• -i Mesh (vtkUnstructuredGrid,1) — THE input mesh. The star. Your unstructured grid, right here, hand it over. 💖
• -ifile MeshInputFileName (str,1) — filename for the default Mesh reader. Use this when you want the default reader to go fetch your mesh by name.
• -entityidsarray CellEntityIdsArrayName (str,1); default=CellEntityIds — the name of that array. The default is literally CellEntityIds, no notes.
• -volumeid VolumeCellEntityId (int,1); default=0 — the volume cell entity id. Default 0.
• -wallid WallCellEntityId (int,1); default=1 — the wall cell entity id. Default 1. One off from volume, that's just how they are. ✨
• -renderer vmtkRenderer (vmtkRenderer,1) — an external renderer, if you already got one sitting there. Sharing is caring. 🫶
• -ofile ReferenceSystemsOutputFileName (str,1) — filename for the default ReferenceSystems writer, i.e. where the default writer is gonna dump your stuff.

🌸 Output arguments 🌸

and these are the ones it hands back to you, the receivers, the little gifts:

• -id Id (str,1); default=0 — the script id again, still 0 by default. Consistency queen.
• -handle Self (self,1) — the handle to self again. Still aware of itself. Still thriving.
• -o ReferenceSystems (vtkPolyData,1) — THE output, bestie. It's a vtkPolyData containing the output reference systems, and it comes with boundary information. That's the whole point of the little fashion show. That's the tea. 🍓

ngl, this one's a look-at-it script, not a change-it script. You give it a mesh, it renders your boundary groups all color-coded and labeled, and everyone stays in their lane. Periodt. 💅

and that's the whole page, mwah. 🧚 this was vmtkmeshboundaryinspector version 1.5, from April 2026 — no cap, that's the source and date, love u, bye 💜🦋