mia-3dlerp(1)

πŸ“¦
version 2.4.7 Β· 3 versions
, in ubuntu jammy, ubuntu noble

πŸ’– mia-3dlerp β€” bestie's guide to linearly combining two 3D images πŸ’–

okay so this is the manual for mia-3dlerp, a lil member of the mia command family, and it's genuinely one of the most iconic tools in the 3D image game. sit with me, grab a strawberry πŸ“, and let's get into it.


✨ NAME ✨

mia-3dlerp β€” linearly combine two 3D images. that's it. that's the whole vibe. two images walk in, one image walks out, and the math is giving middle school fractions but make it voxels. πŸ’…


🌸 SYNOPSIS 🌸

mia-3dlerp -1 <first> -2 <second> -o <out-file> -p <positions> [options]

πŸ¦‹ DESCRIPTION πŸ¦‹

mia-3dlerp merges two images by linear combination. that's literally the sentence. two pics in, one blended pic out. lowkey the whole point. ✨


πŸŽ€ OPTIONS πŸŽ€

🫢 the main character options

  • -1, --first=(required, input); io β€” the first input image. the OG. the left side of your math. For supported file types see PLUGINS:3dimage/io (scroll down bestie, the whole list is there πŸ’–)
  • -2, --second=(required, input); io β€” the second input image. the other half of the equation. For supported file types see PLUGINS:3dimage/io
  • -o, --out-file=(required, output); io β€” the linearly interpolated image, aka the glow-up result of smooshing those two together. For supported file types see PLUGINS:3dimage/io
  • -p, --positions=(required); vfloat β€” image series positions, and the order is literally (first, target, second). so you're telling it where each image sits on the timeline and which spot you want to sample. no cap. 🎯

🧚 Help & Info

  • -V, --verbose=warning β€” verbosity of output. it prints messages of the given level and higher priorities. Supported priorities, starting at the 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. the legal receipts, periodt. πŸ“œ
  • -h, --help β€” print this help
  • -?, --usage β€” print a short help. the TL;DR version bestie.
  • --version β€” print the version number and exit. hit it and dip. πŸ‘‹

πŸ”₯ 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). so like, if you put a bigger number than your actual cores, that's on you bestie 😭 let it auto-estimate with -1 and thrive.

🌈 Test

  • --selftest=(); None β€” run a self test of the program. it checks itself before it wrecks itself. πŸ’€

πŸ‘‘ PLUGINS: 3dimage/io πŸ‘‘

okay here's the full roster of file formats this thing can read and write. every single one. i'm not skipping a single extension, we're being thorough because that's the energy. ✨

  • 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

⭐ EXAMPLE ⭐

okay bestie, imagine you wanna combine inputA.v and inputB.v using position coordinates 4, 7, and 9. what that means is the output pixel values get evaluated according to:

(9-7)/(9-4) * A + (7-4)/(9-4) * B

and the result image gets written to output.v. slay. πŸ”₯

mia-3dlerp -1 inputA.v -2 inputB.v -p 4,7,9 -o output.v

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

Gert Wollny β€” the icon, the legend, the moment. πŸ‘‘


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, ABSOLUTELY NO WARRANTY means exactly what it says. no take-backs, no promises. 🫢

and that's the whole page bestie, we ate and left no crumbs. this was written up for v2.4.7 in the USER COMMANDS section β€” catch you on the next one, mwah πŸ’…πŸ’–βœ¨

πŸ“¦ where this page comes from