VMTKSURFACETONUMPY(1)

πŸ“¦ version 1.5.0, in ubuntu stonking

πŸ’– VMTKSURFACETONUMPY πŸ’–

okay bestie, welcome to vmtksurfacetonumpy, section 1 of the User Commands manual, and honestly? it's giving glow up for your meshes. no cap.


✨ NAME ✨

vmtksurfacetonumpy β€” it's a vmtk script, and the script's whole name is vmtksurfacetonumpy. that's it, that's the name. iconic. πŸ‘‘


πŸŽ€ DESCRIPTION πŸŽ€

Automatic piping vmtkSurfaceToNumpy Parsing options vmtkSurfaceToNumpy 🌈

So like, here's the vibe: vmtkSurfaceToNumpy takes a VTK triangulated surface vtkPolyData file β€” and lowkey, that file can optionally carry point data scalar arrays, we love a bonus feature β€” and it hands you back a nested python dictionary. πŸ“¦

And inside that dictionary? numpy arrays, obviously. Specifically arrays that specify:

  • vertex points ✨
  • associated scalar data πŸ’…
  • cell data that yields triangle connectivity πŸ”Ί

yeah. it converts, it pipes, it serves. main character energy fr fr.


🌸 Input arguments:

  • -id Id (str,1); default=0 β€” the script id
  • -handle Self (self,1) β€” handle to self, it's giving self-awareness πŸͺž
  • -disabled Disabled (bool,1); default=0 β€” turns off execution and piping, like a little off switch 🚫
  • -i Surface (vtkPolyData,1) β€” the input surface, the moment, the ✨material✨
  • -ifile SurfaceInputFileName (str,1) β€” the filename for the default Surface reader πŸ“–
  • -celltopoint ConvertCellToPoint (bool,1); default=0 β€” converts cell data into point data, a lil transformation arc πŸ¦‹
  • -ofile ArrayDictOutputFileName (str,1) β€” the filename for the default ArrayDict writer ✍️

🌟 Output arguments:

  • -id Id (str,1); default=0 β€” the script id (yes, again, it's in both lists, we don't make the rules, we just ship them) πŸ’–
  • -handle Self (self,1) β€” handle to self, back for round two 🫢
  • -o ArrayDict (dict,1) β€” the output dictionary!! the prize!! the whole point!! 🎁
heads up bestie: -id and -handle show up under both Input arguments and Output arguments. that's not me being messy, that's literally the page. also each of the input/output argument lines in the original got split across lines by the formatter β€” the option, its type annotation and its description all belong together, so that's how I paired them up. πŸ’€

and that's the whole entire page, no skips, no cuts. this beautiful thing is vmtksurfacetonumpy version 1.5, dated April 2026, and it ate. periodt. πŸ’…πŸŽ€πŸ¦‹

bye bestie, go convert some surfaces πŸ’–βœ¨

πŸ“¦ where this page comes from