VMTKSURFACEVIEWER(1)
π VMTKSURFACEVIEWER β the vmtksurfaceviewer(1) manual, but make it make sense β¨
okay bestie, buckle up π«Ά this is the User Commands page for vmtksurfaceviewer, a vmtk script. yes it's a manpage. no it does not have to be boring. let's go π
πΈ NAME πΈ
vmtksurfaceviewer β the vmtk script literally called vmtksurfaceviewer π
π¦ DESCRIPTION π¦
so like. automatic piping, vmtksurfaceviewer, parsing options, vmtksurfaceviewer. that's the whole energy of what's happening under the hood π
vmtksurfaceviewer : display a surface β¨ β that's the mission, that's the vibe, that's the whole point.
π Input arguments: π
the stuff you hand it going in, no cap:
-idId (str,1); default=0β the script id. every girl needs an id π-handleSelf (self,1) β handle to self. self-care, literally π«Ά-disabledDisabled (bool,1); default=0β disable execution and piping. it's giving "not today" π-iSurface (vtkPolyData,1) β the input surface. the main character π-ifileSurfaceInputFileName (str,1) β filename for the default Surface reader-renderervmtkRenderer (vmtkRenderer,1) β external renderer. bringing your own, iconic π-displayDisplay (bool,1); default=1β toggle rendering. on by default, as it should be π-representationRepresentation (str,1) in['surface', 'wireframe', 'edges']; default=surfaceβ change surface representation. three lewks, pick your fave β¨-opacityOpacity (float,1) >=0.0and <=1.0; default=1.0β object opacity in the scene. stay in range bestie, don't be extra πΈ-arrayArrayName (str,1) β name of the array where the scalars to be displayed are stored-scalarrangeScalarRange (float,2); default=[0.0, 0.0]β range of the scalar map-colormapColorMap (str,1) in['rainbow', 'blackbody', 'cooltowarm', 'grayscale']; default=cooltowarmβ choose the color map. rainbow era, blackbody era, cooltowarm era, grayscale era β all valid π-numberofcolorsNumberOfColors (int,1); default=256β number of colors in the color map-legendLegend (bool,1); default=0β toggle scalar bar-flatFlatInterpolation (bool,1); default=0β toggle flat or shaded surface display-celldataDisplayCellData (bool,1); default=0β toggle display of point or cell data-displaytagDisplayTag (bool,1); default=Falseβ toggle rendering of tag-regiontagarrayRegionTagArrayName (str,1); default=RegionTagArrayβ name of the array where the tags to be displayed are stored-colorColor (float,3); default=[-1.0, -1.0, -1.0]β RGB color of the object in the scene π¨-linewidthLineWidth (int,1) >=0.0; default=1β width of line objects in the scene-legendtitleLegendTitle (str,1) β title of the scalar bar-ofileSurfaceOutputFileName (str,1) β filename for the default Surface writer
π§ Output arguments: π§
the stuff it hands back. the receipts π:
-idId (str,1); default=0β script id (yes, again. it's in both lists. we don't make the rules)-handleSelf (self,1) β handle to self (also in both. balanced, as all things should be β)-oSurface (vtkPolyData,1) β the output surface-oactorActor (vtkActor,1) β the output actor
lowkey reminder bestie: booleans want0/1, but<pink>-displaytag</pink>and friends are documented with defaults likeFalse, and we are quoting them exactly as written. no editing the facts, only editing the vibe π
and that's the whole page, you ate that π this was vmtksurfaceviewer 1.5, dated April 2026 β periodt πβ¨π¦
π¦ 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