VMTKBRANCHPATCHING(1)

πŸ“¦ version 1.5.0, in ubuntu stonking

πŸ’– NAME πŸ’–

ok so bestie, meet vmtkbranchpatching β€” it's the vmtk script called vmtkbranchpatching, and the fancy manual-page name for all of this is VMTKBRANCHPATCHING(1). 🫢 She's a Unix User Command and she's here to slice and dice your surface, periodt.


✨ DESCRIPTION ✨

Automatic piping, babe. vmtkbranchpatching parses options like it was born to do it β€” vmtkbranchpatching said "parsing options" and then ate. πŸ’…

vmtkbranchpatching : cut a set of contiguous rectangular regions on a surface that follow iso-contours in the StretchedMapping and AngularMetric arrays.

That's the whole vibe. Rectangular regions, contiguous, following iso-contours, living their best life along the StretchedMapping and AngularMetric arrays. Iconic honestly. 🌸

πŸŽ€ Input arguments πŸŽ€

grab your lil notebook, here's every single one, no skipping, fr fr:

  • -id Id (str,1); default=0: script id
  • -handle Self (self,1): handle to self
  • -disabled Disabled (bool,1); default=0: disable execution and piping
  • -i Surface (vtkPolyData,1)
  • -ifile SurfaceInputFileName (str,1): filename for the default Surface reader
  • -patchsize PatchSize (float,2) >= 0.0; default=[0.0, 0.0]
  • -longitudinalpatchsize LongitudinalPatchSize (float,1) >= 0.0; default=1.0
  • -circularpatches CircularNumberOfPatches (int,1) >= 0; default=1
  • -circularpatching CircularPatching (bool,1); default=1
  • -connectivity UseConnectivity (bool,1); default=1
  • -groupidsarray GroupIdsArrayName (str,1); default=GroupIds
  • -longitudinalmappingarray LongitudinalMappingArrayName (str,1); default=AbscissaMetric
  • -circularmappingarray CircularMappingArrayName (str,1); default=AngularMetric
  • -longitudinalpatchnumberarray LongitudinalPatchNumberArrayName (str,1); default=Slab
  • -circularpatchnumberarray CircularPatchNumberArrayName (str,1); default=Sector
  • -patchareaarray PatchAreaArrayName (str,1); default=PatchArea
  • -ofile SurfaceOutputFileName (str,1): filename for the default Surface writer
  • -patcheddatafile PatchedDataOutputFileName (str,1): filename for the default PatchedData writer

πŸ¦‹ Output arguments πŸ¦‹

and the stuff she hands back to you, equally complete, equally slay:

  • -id Id (str,1); default=0: script id
  • -handle Self (self,1): handle to self
  • -o Surface (vtkPolyData,1)
  • -patcheddata PatchedData (vtkImageData,1)
  • -patchsize PatchSize (float,2); default=[0.0, 0.0]
  • -longitudinalpatchnumberarray LongitudinalPatchNumberArrayName (str,1); default=Slab
  • -circularpatchnumberarray CircularPatchNumberArrayName (str,1); default=Sector
  • -patchareaarray PatchAreaArrayName (str,1); default=PatchArea

πŸ’€ tiny warning bestie: -patchsize and -longitudinalpatchsize are the ones wearing the >= 0.0 badge in the input list β€” keep them non-negative, okay? And -circularpatches is rocking >= 0. Don't fight the constraints, they're doing their job. πŸ”₯

and that's the whole page β€” every flag, every default, every type, all accounted for. we ate and left no crumbs. πŸ‘‘


mwah, kisses, that's a wrap β€” this was vmtkbranchpatching 1.5, dated April 2026, coming at you straight from the VMTKBRANCHPATCHING(1) user-commands manual. love u, bye πŸŽ€βœ¨

πŸ“¦ where this page comes from