VMTKIMAGEFEATURECORRECTION(1)
π NAME π
vmtkimagefeaturecorrection β bestie, meet your new fave: a vmtk script called vmtkimagefeaturecorrection. π«Ά
β¨ DESCRIPTION β¨
Okay so picture this, the manual literally opens with β¨ automatic vibes β¨:
Automatic piping vmtkimagefeaturecorrection Parsing options vmtkimagefeaturecorrection
Yeah bestie, that's the whole intro it gives us, and we are not skipping it. Not a single word. π
Now the actual glow-up it does, in the manual's own words: vmtkimagefeaturecorrection</p> corrects a feature image β like, for real, it's giving "remove influence of bone and/or air from CT-based feature images." π
Skeleton where it doesn't belong? Air messing with your feature image? Not on this script's watch. It also does automatic piping and parses options, which is just its lil routine, and we respect it. π
π Input arguments π
Every single one of these, no skips, no shortcuts, periodt:
-idId(str,1);default=0β the script id, and it defaults to0like a little hello. π-handleSelf(self,1)β your handle to self. Iconic, self-love fr. πͺ-disabledDisabled(bool,1);default=0β flips execution and piping off when you set it, so it just chills instead of running. π-iImage(vtkImageData,1)β this is the input feature image, the main character of the whole operation. β¨-ifileImageInputFileName(str,1)β the filename for the default Image reader. πΈ-levelsetsLevelSets(vtkImageData,1)β the input level sets. Yes, those level sets. π¦-levelsetsfileLevelSetsInputFileName(str,1)β the filename for the default LevelSets reader. π-sigmaSigma(float,1)>= 0.0;default=1.0β a sigma, and any value has to be>= 0.0, no negatives allowed, sorry not sorry. π-scaleScaleValue(float,1)>= 0.0;default=0.02β the scale value, also gotta be>= 0.0, and it comes out the box at0.02. π-scalefrominputComputeScaleValueFromInput(bool,1);default=Trueβ computes that scale value from the input, and yeah it's on by default.True, bestie. β-negateNegateLevelSets(bool,1);default=Falseβ negates the level sets, and it defaults toFalseso nothing spicy happens unless you ask. π«-ofileImageOutputFileName(str,1)β the filename for the default Image writer, i.e. where your corrected lil masterpiece gets written. π
π Output arguments π
Yes, the same -id and -handle show up again down here. Do not come for me, that's literally what the page says, and I keep every detail, always. π
-idId(str,1);default=0β the script id again, still defaulting to0. π-handleSelf(self,1)β handle to self, back for round two. π-oImage(vtkImageData,1)β the output image. This is the corrected feature image, the moment we've all been waiting for, the finale. ππ
Heads up bestie: this page hands you raw argument lists β no extra notes, no warnings, no exit statuses, no environment variables, no SEE ALSO, and no separate OPTIONS section beyond the input and output arguments above. So that's exactly what you get. I'm not out here inventing lore. π βοΈ
And that's the whole page, start to finish, every flag intact, no notes left behind. π§ββοΈ
This was vmtkimagefeaturecorrection version 1.5, dated April 2026, and yeah β VMTKIMAGEFEATURECORRECTION(1). Slay, go correct some feature images, love u bye πβ¨ππ¦πΈ
π¦ 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