VMTKSURFACECOMPARE(1)
π NAME π
okay hi bestie, welcome to vmtksurfacecompare β she's a vmtk script (you know, manual section 1, User Commands energy) and she is exactly what her name says on the tin. π¦
πΈ DESCRIPTION πΈ
So the whole vibe here is: vmtksurfacecompare compares a surface against a baseline. That's it. That's the job. β¨
Not me reading the first two lines of the original: "Automatic pipingvmtksurfacecompareParsing optionsvmtksurfacecompare" π yeah girl, that's the machinery doing its thing β the automatic piping and the option parsing, lowkey just how every one of these scripts rolls up its sleeves before it even gets to your actual question.
And the actual question is:
vmtksurfacecompare : compares a surface against a baseline π
Periodt. Here's how you talk to her. π
π Input arguments π
these are the things you feed her, in order of appearance, no skips:
-idId (str,1); default=0β the script id. it's the lil name tag she wears. π·οΈ-handleSelf (self,1) β handle to self. she's holding her own hand, iconic, we love self-love. π«Ά-disabledDisabled (bool,1); default=0β set this and she justβ¦ doesn't run. execution off, piping off, she's on do-not-disturb. π΄-iSurface (vtkPolyData,1) β the input surface. the main character of the whole operation. π-ifileSurfaceInputFileName (str,1) β filename for the default Surface reader. like, "hey girl go read this file for me." π-rReferenceSurface (vtkPolyData,1) β the input surface. this is your baseline, the one she's comparing against. the reference. the standard. the ex you keep measuring yourself to, but, like, scientifically. π-rfileReferenceSurfaceInputFileName (str,1) β filename for the default ReferenceSurface reader. same deal, but for the baseline file. π-methodMethod (str,1) in['addpointarray', 'addcellarray', 'projection', 'distance']β the method of the test. pick your fighter. π₯-arrayArrayName (str,1) β name of the array. gotta name your array bestie, it's not gonna name itself. π·οΈβ¨-toleranceTolerance (float,1); default=1e-08β tolerance for numerical comparisons. she is strict. one part in a hundred million and she'll notice. ngk she's giving precision. π¬-ofileResultDataOutputFileName (str,1) β filename for the default ResultData writer. where the receipts get written down. π§Ύ
β¨ Output arguments β¨
what she hands back to you when she's done:
-idId (str,1); default=0β the script id, again, same lil name tag. π·οΈ-handleSelf (self,1) β handle to self, again. still holding her own hand. we respect it. π«Ά-resultResult (bool,1) β Output boolean stating if surfaces are equal or not. the verdict!!TrueorFalse, iconic either way, no cap. βοΈ-oResultData (vtkPolyData,1) β the output surface. π-logResultLog (str,1) β the Result Log. the group chat screenshot of the whole operation, so to speak. ποΈ
π fr fr, don't sleep on-toleranceβ default is1e-08and she means it. numerical comparisons get picky down there.
π SEE ALSO
(nothing listed, bestie β the original page doesn't reference any other manuals, so no further reading recs, sorry not sorry π)
that's the whole page, slay. π this was vmtksurfacecompare, vmtk script version 1.5, from April 2026 β user commands, manual section 1, and she ate π
ππ¦ sending you off with love, go compare some surfaces bestie π«Άβ¨
π¦ 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