mia-3dimageaddattributes(1)

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

πŸ’– mia-3dimageaddattributes πŸ’–

okay so bestie, welcome to the General Commands Manual glow-up of mia-3dimageaddattributes ✨ this is the whole thing, every flag, every plugin, no cap.


🌸 NAME 🌸

mia-3dimageaddattributes β€” slaps attributes onto the meta data of a 3D image. that's the whole job. πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

mia-3dimageaddattributes -i <in-file> -o <out-file> -a <attr> [options]

✨ DESCRIPTION ✨

so basically, mia-3dimageaddattributes takes every single meta-data attribute it can find in a 2D input image and appends all of them to a 3D image. it's giving "borrow her whole personality and put it on the 3D one" 🫢

the big caveat tho: this only works if the output format actually supports such attributes. if it doesn't, welp. πŸ™ˆ

also important β€” attributes that are already present in the 3D image do not get overwritten. the 3D image keeps its originals, periodt. πŸ‘‘


πŸŽ€ OPTIONS πŸŽ€

  • -i, --in-file=(required, input); io β€” the input image(s) to be filtered. for supported file types see PLUGINS:3dimage/io
  • -o, --out-file=(output, required); io β€” the output image(s) with the added attributes. for supported file types see PLUGINS:3dimage/io
  • -a, --attr=(required, input); io β€” the 2D image providing the attributes. for supported file types see PLUGINS:2dimage/io

🫢 Help & Info 🫢

  • -V, --verbose=warning β€” how chatty the output is: it prints messages of the given level and every priority above it. 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 β€” 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).

πŸ”Œ 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 ⭐

Append the attributes found in 2d.v to 3d.v and store the result in attr3d.v

mia-3dimageaddattributes  -i 3d.v -o attr3d.v -a 2d.v

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


and that's the whole page bestie, we ate and left no crumbs πŸŽ€ this lil icon was living under USER COMMANDS, version v2.4.7, signed off as mia-3dimageaddattributes(1) β€” go forth and add those attributes, you main character πŸ¦‹βœ¨

πŸ“¦ where this page comes from