mia-3deval...rmquantity(1)
π mia-3deval-transformquantity β a Gen Z field guide π
okay bestie, so this whole page is from the General Commands Manual, section 1, and the command it's all about is mia-3deval-transformquantity. Say it with me one more time: mia-3deval-transformquantity. It's a mouthful but she's worth it. π«Ά
β¨ NAME β¨
mia-3deval-transformquantity β evaluate the derivative of a transformation. that's it, that's the whole vibe.
πΈ SYNOPSIS πΈ
mia-3deval-transformquantity -o <out-file> -t <transformation> [options]
π¦ DESCRIPTION π¦
so like, mia-3deval-transformquantity gets you the derivative of a transformation that you got from image registration, evaluated at literally any positions you want in 3D. main character energy fr. π
Your position data comes in as CSV, formatted like this:
id;time;x;y;z;reserved
The output? It gets stored in a binary file with an ascii header describing what's inside. Here's an example header for you:
MIA tensorfield {
dim=3 #number of dimensions of the data
components=13 #number of components per element
component_description=vector3,scalar,matrix3x3 #interpretation of components
elements=20 #number of elements in file
interpretation=strain #interpretation of elements (strain|derivative)
style=sparse #storage style (sparse|grid)
repn=float32 #representation of values
size=1000 1000 200 #grid size of the transformation
endian=low #endianess of binary data (low|big) }
and now let's decode this header together because it's giving β¨loreβ¨:
- three-dimensional data π§
- each entry has 13 values, and those 13 values break down into a 3D vector, a scalar, and a 3x3 matrix (saved in row-major format)
- the data records represent strain tensors, and only a sparse set of points is given
- the values are single floating point (32 bit)
- the original transformation field corresponds to images of 1000x1000x200 voxels
- and the binary data is stored in low endian format
no cap, that's a whole lot of information in one little header. she ate. π
π OPTIONS π
π File-IO
-i,--in-file=(input); stringβ input point set. if you pass this, you get a sparse evaluation of the quantity. if you don't, the quantity gets evaluated for each grid point of the transformation range. your call bestie.-o,--out-file=(output, required); stringβ output strains file. format description? see above, we literally just went over it π-t,--transformation=(input, required); ioβ the transformation whose quantity is getting evaluated. for supported file types, go peek atPLUGINS:3dtransform/io(it's right down there β¬οΈ)
π Parameters
-q,--quantity=strainβ specify the quantity to be evaluated at the given points:derivativeβ evaluate the transformation derivative at the given pointsstrainβ evaluate the strain tensor at the given points
π Help & Info
-V,--verbose=warningβ verbosity of output; prints messages of the given level and higher priorities. supported priorities, starting at the lowest level, are:traceβ function call tracedebugβ debug outputinfoβ low level messagesmessageβ normal messageswarningβ warningsfailβ report test failureserrorβ report errorsfatalβ 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. (-1means automatic estimation, so like, she'll figure it out herself π«)
β PLUGINS: 3dtransform/io β
the supported file types for -t, in all their glory:
bbsβ Binary (non-portable) serialized IO of 3D transformations- recognized file extensions:
.bbs
- recognized file extensions:
datapoolβ Virtual IO to and from the internal data pool- recognized file extensions:
.@
- recognized file extensions:
vistaβ Vista storage of 3D transformations- recognized file extensions:
.v,.v3dt
- recognized file extensions:
xmlβ XML serialized IO of 3D transformations- recognized file extensions:
.x3dt
- recognized file extensions:
π₯ EXAMPLE π₯
so the derivative of the transformation change.v3df for each point given in input.csv gets evaluated and written to output.s. here's the moment, bestie:
mia-3deval-transformquantity -i input.csv -o output.s --transformation change.v3df
ngl, copy it, run it, slay. π«Ά
π AUTHOR(s) π
Gert Wollny β yes, an actual legend wrote this.
πΈ COPYRIGHT πΈ
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.
β οΈ ok real talk, "ABSOLUTELY NO WARRANTY" is in all caps for a reason β that's the legal vibe, don't skip it.
and that's the whole page, bestie!! this one's from the USER COMMANDS crew, v2.4.7, and it was living under the title mia-3deval...rmquantity(1) the whole time (yes, the manpage header really does abbreviate it like that, iconic behavior honestly π). go evaluate some derivatives. periodt. πβ¨π¦
π¦ where this page comes from
- ubuntu jammy: mia-tools 2.4.7-8ubuntu1 Β· GPL-3.0-or-later
- ubuntu resolute: mia-tools 2.4.7-18 Β· GPL-3.0-or-later
- ubuntu stonking: mia-tools 2.4.7-19build1 Β· GPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms