VMTKMESHDATAREADER(1)

πŸ“¦ version 1.5.0, in ubuntu stonking

πŸ’– VMTKMESHDATAREADER πŸ’–

okay bestie, this is section 1 of the manuals (User Commands, no cap), and the command itself is literally called vmtkmeshdatareader. Yes that's a mouthful. Yes it's iconic. Let's get into it 🫢


✨ NAME ✨

vmtkmeshdatareader β€” it's a vmtk script, and the script is named vmtkmeshdatareader. That's the whole name section. She said "my name is my name" πŸ’…


🌸 DESCRIPTION 🌸

So the vibe here is: automatic piping. There's automatic piping happening (vmtkmeshdatareader), and also option parsing (vmtkmeshdatareader). It's giving plumbing but make it ✨scientific✨.

What does it actually do tho? Here's the tea:

vmtkmeshdatareader : read data associated with a mesh

That's the mission statement. Read data. Attached to a mesh. Slay πŸ”₯

πŸŽ€ Input arguments πŸŽ€

the stuff you feed in, the ingredients, the little guys:

  • -id Id (str,1); default=0 β€” the script id. It's the id. Of the script. Default 0, as one does.
  • -handle Self (self,1) β€” handle to self 🫢 yes, self-love is a valid input argument, we love to see it.
  • -disabled Disabled (bool,1); default=0 β€” disable execution and piping. So if you set this, it just... doesn't. Very "not me showing up today" energy.
  • -i Mesh (vtkUnstructuredGrid,1) β€” the input mesh. THE mesh. the main character mesh πŸ‘‘
  • -ifile MeshInputFileName (str,1) β€” filename for the default Mesh reader.
  • -directory DataFileDirectory (str,1); default=. β€” directory where the data files reside. Default is just . (yep, right here, in your current folder, bestie).
  • -prefix DataFilePrefix (str,1) β€” data file name prefix β€” like foo_ for example.
  • -datafile DataFileName (str,1) β€” data file name (like foo.dat for example), excluding directory. Careful: this one overrides prefix. She's powerful. She said "I go first" πŸ’…
  • -filetype DataFileType (str,1); default=tetr.vel β€” data file name type. Your choices are: tetr.out, tetr.vel, tetr.wss, tetr.pres, tetr.ini, pointdata. Pick your fighter 🌈
  • -arrayprefix ArrayNamePrefix (str,1) β€” prefix to prepend to array names in output. A little name tag. So cute πŸŽ€
  • -tetrinfile TetrInFileName (str,1) β€” name of the tetr.in file.
  • -compressed Compressed (bool,1); default=1 β€” toggle reading gzip compressed file. Default is on, so compressed is the moment unless you say otherwise.
  • -unnormalize UnNormalize (bool,1); default=1 β€” unnormalize quantities. Note: tetr.* only. Don't try it on anything else, that's not her jurisdiction.
  • -minvarid MinVariableId (int,1) >= 0; default=-1 β€” read variables starting from the nth column. pointdata only, iykyk.
  • -maxvarid MaxVariableId (int,1) >= 0; default=-1 β€” read variables up to the nth column. Also pointdata only, obviously, keeping it symmetrical, we love a matching set πŸ¦‹
  • -ofile MeshOutputFileName (str,1) β€” filename for the default Mesh writer.

πŸ’œ Output arguments πŸ’œ

what she gives you back, the results, the payoff:

  • -id Id (str,1); default=0 β€” script id. (Yes it's here too. She contains multitudes. Both an input and an output. Literally all of us fr fr.)
  • -handle Self (self,1) β€” handle to self. (Also both. Self is eternal like that.)
  • -o Mesh (vtkUnstructuredGrid,1) β€” the output mesh!! The glow-up mesh. The before and after 🌟

okay a lil heads up bestie: -datafile fully overrides -prefix, and the -minvarid / -maxvarid / -unnormalize options only work for their specific file types (pointdata and tetr.* respectively). Read the one-liners. They're telling you something πŸ’€

and that's the page!! vmtkmeshdatareader 1.5, from April 2026. the version and the date, immortalized. periodt πŸ’–βœ¨πŸ¦‹πŸŽ€πŸ‘‘

πŸ“¦ where this page comes from