VMTKSURFACECAPPER(1)
π VMTKSURFACECAPPER π
okay bestie so this is a User Commands situation, it's the manual for vmtksurfacecapper β a vmtk script, and honestly? she's iconic. β¨
π NAME π
vmtksurfacecapper β literally just a vmtk script called vmtksurfacecapper, no cap.
πΈ DESCRIPTION πΈ
Automatic piping. vmtksurfacecapper is out here parsing options, and vmtksurfacecapper is the moment. periodt.
vmtksurfacecapper : add caps to the holes of a surface, assigning an id to each cap for easy specification of boundary conditions. π«Ά
β¨ input arguments β¨ (yes she gets her own section)
-idId (str,1); default=0β your script id, bestie.-handleSelf (self,1) β handle to self. main character energy fr.-disabledDisabled (bool,1); default=0β disable execution and piping. like, going ghost mode.-iSurface (vtkPolyData,1) β the input surface. the whole vibe she's working with.-ifileSurfaceInputFileName (str,1) β filename for the default Surface reader.-methodMethod (str,1) in['simple', 'centerpoint', 'smooth', 'annular', 'concaveannular']; default=simpleβ the capping method. five options, five aesthetics, pick your fighter π-triangleTriangleOutput (bool,1); default=1β toggle triangulation of the output.-entityidsarrayCellEntityIdsArrayName (str,1); default=CellEntityIdsβ name of the array where the id of the caps have to be stored.-entityidoffsetCellEntityIdOffset (int,1) >=0; default=1β offset for entity ids.-constraintConstraintFactor (float,1); default=1.0β amount of influence of the shape of the surface near the boundary on the shape of the cap ("smooth" method only).-ringsNumberOfRings (int,1) >=0; default=8β number of rings composing the cap ("smooth" method only).-interactiveInteractive (bool,1); default=1β no description in the original, she just is. π¦-renderervmtkRenderer (vmtkRenderer,1) β external renderer.-ofileSurfaceOutputFileName (str,1) β filename for the default Surface writer.
π output arguments π (she ALSO gets her own section)
-idId (str,1); default=0β script id, again. screaming, crying, but make it symmetrical.-handleSelf (self,1) β handle to self. yes she's here too. π-oSurface (vtkPolyData,1) β the output surface. the glow-up. π₯-entityidsarrayCellEntityIdsArrayName (str,1); default=CellEntityIdsβ name of the array where the id of the caps are stored (notice: are stored now, not have to be stored β the glow-up is real).
π real talk:-id,-handleand-entityidsarrayeach show up in BOTH the input and the output lists. that's not a typo, that's just the lore. don't come for me.
π the sign-off π
that's the whole page bestie β no more, no less, every single flag accounted for, not one skipped, because we don't do that here. π
this lil masterpiece is vmtksurfacecapper 1.5, dated April 2026 β footnotes never looked so good. go cap some holes, you got this π
β¨ππΈπ¦
π¦ where this page comes from
- ubuntu stonking: vmtk 1.5.0+dfsg1-1 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms