mia-2dmultiimageto3d(1)

πŸ“¦
version 2.4.7 Β· 2 versions
, in debian bookworm, ubuntu resolute, ubuntu stonking

πŸ’– mia-2dmultiimageto3d β€” bestie edition πŸ’–

okay so. this is the mia-2dmultiimageto3d page, from the General Commands Manual section, and it's honestly so much simpler than it looks. sit down, grab a strawberry πŸ“, we're doing this.


✨ NAME ✨

mia-2dmultiimageto3d β€” bestie, it takes a 2D multi-record image and turns it into a 3D image. that's it. that's the whole job. iconic behavior.


πŸ“œ SYNOPSIS πŸ“œ

mia-2dmultiimageto3d -i <in-file> -o <out-file> [options]

🌸 DESCRIPTION 🌸

okay so real talk: mia-2dmultiimageto3d is the program you use when you've got a 2D multi-image file and you need it to be a 3D image. glow-up pipeline, basically. πŸ’…


πŸŽ€ OPTIONS πŸŽ€

  • -i, --in-file=(input, required); io β€” the input images 🫢. this one is required, no skipping. for which file types are supported, go peek at PLUGINS:2dimage/io down below.
  • -o, --out-file=(output, required); io β€” the output image ✨. also required. for supported file types here, see PLUGINS:3dimage/io.

πŸ’ Help & Info

  • -V, --verbose=warning β€” controls how chatty the output is: it prints messages of the given level and higher priorities. the supported priorities, starting at the lowest level, are literally right here:
    • 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 β€” prints the copyright information πŸ“„
  • -h, --help β€” prints this help
  • -?, --usage β€” prints a short help
  • --version β€” prints the version number and dips ✌️

πŸ”₯ 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 bestie, "Maxiumum" is spelled exactly like that in the original and i am NOT about to gaslight you by fixing it 😭 also note there's no space after that comma. copied verbatim, no cap.)

πŸ¦‹ PLUGINS: 2dimage/io πŸ¦‹

  • bmp β€” BMP 2D-image input/output support. The plug-in supports reading and writing of binary images and 8-bit gray scale images. read-only support is provided for 4-bit gray scale images. The color table is ignored and the pixel values are taken as literal gray scale values.
    • Recognized file extensions: .BMP, .bmp
    • Supported element types: binary data, unsigned 8 bit
  • datapool β€” Virtual IO to and from the internal data pool
    • Recognized file extensions: .@
  • dicom β€” 2D image io for DICOM
    • Recognized file extensions: .DCM, .dcm
    • Supported element types: signed 16 bit, unsigned 16 bit
  • exr β€” a 2dimage io plugin for OpenEXR images
    • Recognized file extensions: .EXR, .exr
    • Supported element types: unsigned 32 bit, floating point 32 bit
  • jpg β€” a 2dimage io plugin for jpeg gray scale images
    • Recognized file extensions: .JPEG, .JPG, .jpeg, .jpg
    • Supported element types: unsigned 8 bit
  • png β€” a 2dimage io plugin for png images
    • Recognized file extensions: .PNG, .png
    • Supported element types: binary data, unsigned 8 bit, unsigned 16 bit
  • raw β€” RAW 2D-image output support
    • Recognized file extensions: .RAW, .raw
    • 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
  • tif β€” TIFF 2D-image input/output support
    • Recognized file extensions: .TIF, .TIFF, .tif, .tiff
    • Supported element types: binary data, unsigned 8 bit, unsigned 16 bit, unsigned 32 bit
  • vista β€” a 2dimage io plugin for vista images
    • 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

🧚 PLUGINS: 3dimage/io 🧚

  • 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 🌈

say you've got a whole series of images chillin' inside a 2D image container called multiimage2d.v and you want it to be a 3D image called image3d.v. bestie, that's literally one line:

mia-2dmultiimageto3d -i multiimage2d.v -o image3d.v

slay. πŸ‘‘


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

no warranty, fr fr β€” read the license, it's important 🫢

and that's the whole page, bestie. this one's from the USER COMMANDS section and it's v2.4.7 β€” go forth and convert, you absolute icon πŸŒŸπŸ’œ

πŸ“¦ where this page comes from