mia-3dfield2norm(1)

πŸ“¦
version 2.4.7 Β· 2 versions
, in debian bookworm, ubuntu jammy, ubuntu noble

πŸ’– mia-3dfield2norm β€” the manual, but make it make sense πŸ’–

okay so bestie, gather round, because this is mia-3dfield2norm(1) from the General Commands Manual and it is genuinely so much simpler than it looks. she's a little utility, she does one job, and she does it flawlessly. no cap. ✨


✨ NAME ✨

mia-3dfield2norm β€” Evaluate the norm image of a 3D vector field. that's it. that's the whole vibe. πŸ¦‹


🌸 SYNOPSIS 🌸

mia-3dfield2norm -i <in-vectorfield> -o <out-image> [options]

like, you give her a vector field, you tell her where to put the output image, and everything else is optional. main character energy honestly. πŸ‘‘


πŸ’… DESCRIPTION πŸ’…

so mia-3dfield2norm takes a 3d vector field and converts it into an image of its voxel-wise norm. every voxel in, one norm value out. it's giving "glow up but make it math". literally the most straightforward transformation and I'm obsessed with her for it. πŸŽ€


πŸ”₯ OPTIONS πŸ”₯

  • -i, --in-vectorfield=(input, required); io β€” the input vector field. this one is required, she will not run without it, periodt. for supported file types see PLUGINS:3dvf/io down below bestie πŸ’œ
  • -o, --out-image=(required, output); io β€” the output image comprising the per voxel norm of each image. also required. for supported file types see PLUGINS:3dimage/io, also down below 🌈

🌟 Help & Info 🌟

  • -V, --verbose=warning β€” verbosity of output, print messages of given level and higher priorities. supported priorities starting at lowest level are:
    • trace β€” Function call trace
    • debug β€” Debug output
    • info β€” Low level messages
    • message β€” Normal messages
    • warning β€” Warnings
    • fail β€” Report test failures
    • error β€” Report errors
    • fatal β€” Report only fatal errors
  • --copyright β€” print copyright information πŸ“œ
  • -h, --help β€” print this help 🫢
  • -?, --usage β€” print a short help
  • --version β€” print the version number and exit

🧚 Processing 🧚

  • --threads=-1 β€” Maxiumum number of threads to use for processing, This number should be lower or equal to the number of logical processor cores in the machine. (-1: automatic estimation). yes the original says "Maxiumum", I'm not fixing her typo, she's iconic 😭

πŸ–ΌοΈ PLUGINS: 3dimage/io πŸ–ΌοΈ

these are all the formats she can write your output image to. slay.

  • analyze β€” Analyze 7.5 image
    • Recognized file extensions: .HDR, .hdr
    • Supported element types:
      • unsigned 8 bit, signed 16 bit, signed 32 bit, floating point 32 bit, floating point 64 bit
  • datapool β€” Virtual IO to and from the internal data pool
    • Recognized file extensions: .@
  • dicom β€” Dicom image series as 3D
    • Recognized file extensions: .DCM, .dcm
    • Supported element types:
      • signed 16 bit, unsigned 16 bit
  • hdf5 β€” HDF5 3D image IO
    • Recognized file extensions: .H5, .h5
    • Supported element types:
      • binary data, signed 8 bit, unsigned 8 bit, signed 16 bit, unsigned 16 bit, signed 32 bit, unsigned 32 bit, signed 64 bit, unsigned 64 bit, floating point 32 bit, floating point 64 bit
  • inria β€” INRIA image
    • Recognized file extensions: .INR, .inr
    • Supported element types:
      • signed 8 bit, unsigned 8 bit, signed 16 bit, unsigned 16 bit, signed 32 bit, unsigned 32 bit, floating point 32 bit, floating point 64 bit
  • mhd β€” MetaIO 3D image IO using the VTK implementation (experimental).
    • Recognized file extensions: .MHA, .MHD, .mha, .mhd
    • Supported element types:
      • signed 8 bit, unsigned 8 bit, signed 16 bit, unsigned 16 bit, signed 32 bit, unsigned 32 bit, floating point 32 bit, floating point 64 bit
  • nifti β€” NIFTI-1 3D image IO. The orientation is transformed in the same way like it is done with 'dicomtonifti --no-reorder' from the vtk-dicom package.
    • Recognized file extensions: .NII, .nii
    • Supported element types:
      • signed 8 bit, unsigned 8 bit, signed 16 bit, unsigned 16 bit, signed 32 bit, unsigned 32 bit, signed 64 bit, unsigned 64 bit, floating point 32 bit, floating point 64 bit
  • vff β€” VFF Sun raster format
    • Recognized file extensions: .VFF, .vff
    • Supported element types:
      • unsigned 8 bit, signed 16 bit
  • vista β€” Vista 3D
    • Recognized file extensions: .-, .V, .VISTA, .v, .vista
    • Supported element types:
      • binary data, signed 8 bit, unsigned 8 bit, signed 16 bit, unsigned 16 bit, signed 32 bit, unsigned 32 bit, floating point 32 bit, floating point 64 bit
  • vti β€” 3D image VTK-XML in- and output (experimental).
    • Recognized file extensions: .VTI, .vti
    • Supported element types:
      • signed 8 bit, unsigned 8 bit, signed 16 bit, unsigned 16 bit, signed 32 bit, unsigned 32 bit, floating point 32 bit, floating point 64 bit
  • vtk β€” 3D VTK image legacy in- and output (experimental).
    • Recognized file extensions: .VTK, .VTKIMAGE, .vtk, .vtkimage
    • Supported element types:
      • signed 8 bit, unsigned 8 bit, signed 16 bit, unsigned 16 bit, signed 32 bit, unsigned 32 bit, floating point 32 bit, floating point 64 bit

πŸ¦‹ PLUGINS: 3dvf/io πŸ¦‹

and these are the formats your input vector field can be. the more you know πŸ’«

  • cvista β€” obsolete 3d vector field io plugin for range compressend vista (saving not supported)
    • Recognized file extensions: .CVF, .cvf
    • Supported element types:
      • floating point 32 bit
  • datapool β€” Virtual IO to and from the internal data pool
    • Recognized file extensions: .@
  • vista β€” a 3d vector field io plugin for vista
    • Recognized file extensions: .V, .VF, .v, .vf
    • Supported element types:
      • floating point 32 bit
  • vtk β€” 3D Vector field in- and output (experimental). No attributes are stored or read.
    • Recognized file extensions: .VTK, .VTKVF, .vtk, .vtkvf
    • Supported element types:
      • floating point 32 bit

πŸ“ EXAMPLE πŸ“

Evaluate the norm image norm.v from a vector field field.v.

mia-3dfield2norm -i field.v -o norm.v

see? told you she was easy. ate and left no crumbs. πŸ’…


πŸ’œ AUTHOR(s) πŸ’œ

Gert Wollny


This software is Copyright (c) 1999‐2015 Leipzig, Germany and Madrid, Spain. It comes with ABSOLUTELY NO WARRANTY and you may redistribute it under the terms of the GNU GENERAL PUBLIC LICENSE Version 3 (or later). For more information run the program with the option '--copyright'.

fr fr read that again: ABSOLUTELY NO WARRANTY. she's free, she's open source, she's not liable for anything. 🫢

and that's the whole page bestie!! πŸ’– this was USER COMMANDS, version v2.4.7, and yeah, that's the mia-3dfield2norm(1) manual β€” go evaluate some norms, you've got this βœ¨πŸŽ€πŸŒˆ

πŸ“¦ where this page comes from