mia-3dcomb...imageseries(1)

πŸ’– mia-3dcombine-imageseries πŸ’–

okay bestie, quick vibe check: this is the manual page for mia-3dcombine-imageseries from the General Commands Manual section. it's a whole glow-up for your image stack, and yes, it's about to eat. 🫢


✨ NAME ✨

mia-3dcombine-imageseries β€” Combine images. that's it. that's the job. πŸ’…


🌈 SYNOPSIS 🌈

mia-3dcombine-imageseries -o <out-file> [options] <PLUGINS:3dimage/io>

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea πŸ“: mia-3dcombine-imageseries takes a whole lil' squad of input images that all have the same dimensions, and it glues them into one combined output image using the operation you define for the combination. it's giving group project where everyone actually contributes. iconic. πŸ‘‘


πŸŽ€ OPTIONS πŸŽ€

  • -o, --out-file=(output, required); io β€” the output file that's gonna hold your combined image. required, bestie, don't forget it. for supported file types, go peek at PLUGINS:3dimage/io down below. πŸ’–
  • -p, --operation=mean β€” the operation applied when combining the images. pick your fighter:
    • mean β€” mean image intensities ✨
    • max β€” select max per pixel intensity πŸ”₯
    • add β€” add pixel intensities βž•
  • -r, --repn=none β€” the output pixel representation. if you don't give one, then the representation of the first input image gets used. no cap. the options are:
    • bit β€” binary data
    • sbyte β€” signed 8 bit
    • ubyte β€” unsigned 8 bit
    • sshort β€” signed 16 bit
    • ushort β€” unsigned 16 bit
    • sint β€” signed 32 bit
    • uint β€” unsigned 32 bit
    • slong β€” signed 64 bit
    • ulong β€” unsigned 64 bit
    • float β€” floating point 32 bit
    • double β€” floating point 64 bit
    • none β€” no pixel type defined

πŸ’¬ Help & Info πŸ’¬

  • -V, --verbose=warning β€” verbosity of output: it prints messages of the given level and higher priorities. the 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 πŸ“œ
  • -h, --help β€” print this help πŸ†˜
  • -?, --usage β€” print a short help
  • --version β€” print the version number and exit

βš™οΈ Processing βš™οΈ

  • --threads=-1 β€” maximum 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). let the machine cook. πŸ”₯

🧚 PLUGINS: 3dimage/io 🧚

here's the whole roster of formats that can slide in and out, bestie. each one comes with its recognized file extensions and supported element types. πŸ’œ

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 🌸

mia-3dcombine-imageseries

πŸ‘‘ 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'.


okay that's the whole thing, bestie, you're so ready πŸ’… this was the USER COMMANDS page for mia-3dcomb...imageseries(1), v2.4.7 era energy β€” go forth and combine those images, you absolute main character. πŸ¦‹βœ¨πŸŽ€