VMTKBOUNDARYREFERENCESYSTEMS(1)
π NAME π
vmtkboundaryreferencesystems β ok bestie this is a vmtk script, and its whole name is literally vmtkboundaryreferencesystems, no notes β¨
πΈ DESCRIPTION πΈ
So. Automatic piping, vmtkboundaryreferencesystems, parsing options, vmtkboundaryreferencesystems. That's the whole vibe of the pipeline, no cap π
Now the actual tea, vmtkboundaryreferencesystems computes the reference systems relative to each open boundary of a model π¦ A super typical glow-up use for this is specifying boundary conditions for CFD simulations, periodt. The reference systems get handed to you both as origin and normal, and as origin plus a first point that defines the x axis together with the origin, plus a second point that defines the xy plane together with the former two β¨
π«Ά Input arguments π«Ά
-idId (str,1); default=0β the script id, iconic-handleSelf (self,1) β handle to self, she's holding her own hand π«Ά-disabledDisabled (bool,1); default=0β disable execution and piping, in case you need her to sit down and chill-iSurface (vtkPolyData,1) β the input surface, the main character of this whole operation π-ifileSurfaceInputFileName (str,1) β filename for the default Surface reader-boundaryradiusarrayBoundaryRadiusArrayName (str,1); default=BoundaryRadiusβ name of the array where the mean radius of each boundary has to be stored-boundarynormalsarrayBoundaryNormalsArrayName (str,1); default=BoundaryNormalsβ name of the array where outward pointing normals to each boundary have to be stored-point1arrayPoint1ArrayName (str,1); default=Point1β name of the array where the coordinates of a point of each boundary have to be stored-point2arrayPoint2ArrayName (str,1); default=Point2β name of the array where the coordinates of a second point of each boundary have to be stored-ofileReferenceSystemsOutputFileName (str,1) β filename for the default ReferenceSystems writer
π Output arguments π
-idId (str,1); default=0β the script id, she's back and she's still iconic-handleSelf (self,1) β handle to self, again, self-love fr fr π-oReferenceSystems (vtkPolyData,1) β the output reference systems, given as points coinciding with the origins β-boundaryradiusarrayBoundaryRadiusArrayName (str,1); default=BoundaryRadiusβ name of the array where the mean radius of each boundary has to be stored-boundarynormalsarrayBoundaryNormalsArrayName (str,1); default=BoundaryNormalsβ name of the array where outward pointing normals to each boundary are stored-point1arrayPoint1ArrayName (str,1); default=Point1β name of the array where the coordinates of a point of each boundary are stored-point2arrayPoint2ArrayName (str,1); default=Point2β name of the array where the coordinates of a second point of each boundary are stored
lowkey obsessed with how the input versions say stuff "has to be stored" and the output versions just say it "are stored" β character development, honestly ππ
And that's the whole page, bestie π«Ά this was vmtkboundaryreferencesystems version 1.5, dated April 2026 β mwah, go forth and slay your boundary conditions π
β¨π
π¦ 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