USAGE:(1)

πŸ“¦
version 0.3 Β· 2 versions
, in fedora 43

πŸ’… USAGE:(1) β€” the manual page, but make it make sense

okay bestie, welcome to USAGE:(1) ✨ this is the manual page for usage: tff_convert_tractogram and honestly? it's giving "converter that just works." sit down, grab a strawberry πŸ“, and let's get into it.


🌸 NAME 🌸

usage: β€” manual page for usage: tff_convert_tractogram [-h] [--reference REFERENCE] πŸŽ€

that's it. that's the name. the manpage said "my name is my whole command line" and honestly? iconic.


πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's the whole invocation, exactly as the page lays it out:

usage: tff_convert_tractogram [-h] [--reference REFERENCE]
       [--positions_dtype {float16,float32,float64}]
       [--offsets_dtype {uint32,uint64}] [-f] IN_TRACTOGRAM
       OUT_TRACTOGRAM

so what does it DO? it converts '.tck', '.trk', '.fib', '.vtk', '.trx' and 'dpy' files using the updated file format standard. glow up for your tractograms, periodt πŸ’…

⚠️ heads up bestie: a TCK file ALWAYS needs a reference file, a NIFTI, for conversion. no reference, no conversion. that's just the rules 😭

and plot twist for the lore girlies: the FIB file format is in fact a VTK, and MITK Diffusion supports it. so it's giving VTK wearing a FIB costume 🧚


πŸŽ€ positional arguments πŸŽ€

these two are mandatory, no skips:

  • IN_TRACTOGRAM β€” Tractogram filename. Format must be one of trk, tck, vtk, fib, dpy, trx. this is the one you're converting FROM, the before pic πŸ“Έ
  • OUT_TRACTOGRAM β€” Output filename. Format must be one of trk, tck, vtk, fib, dpy, trx. the after pic. main character energy ✨

πŸ‘‘ options πŸ‘‘

  • -h, --help β€” show this help message and exit. the "bestie explain" button 🫢
  • --reference REFERENCE β€” Reference anatomy for tck/vtk/fib/dpy file support (.nii or .nii.gz). it's the anatomy bestie that tags along so those formats can do their thing πŸ’œ
  • -f β€” Force overwriting of the output files. when you're done being polite to your old output files πŸ’€

🌈 Data type options 🌈

this is where you pick your ✨ precision aesthetic ✨, specifically for trx:

  • --positions_dtype {float16,float32,float64} β€” Specify the datatype for positions for trx. default is [float32]
  • --offsets_dtype {uint32,uint64} β€” Specify the datatype for offsets for trx. default is [uint64]

and then the page just... drops this fragment again, so here it is, verbatim, because we do not gatekeep:

[--positions_dtype {float16,float32,float64}]
       [--offsets_dtype {uint32,uint64}] [-f] IN_TRACTOGRAM
       OUT_TRACTOGRAM

🚨 the vibe check that fails 🚨

if you forget your positionals, the universe (well, argparse) hits you with:

tff_convert_tractogram: error: the following arguments are required: IN_TRACTOGRAM, OUT_TRACTOGRAM

no cap, IN_TRACTOGRAM and OUT_TRACTOGRAM are required. the program will simply not be doing it without them πŸ™ˆ


okay that's the whole page, you ate it, i'm obsessed πŸ’–

cute little sign-off from the footer, because it deserves its moment: this page signs itself usage: tff_convert_tractogram... and it's dated September 2025 ⭐ so yeah β€” genned in September 2025, still slaying. bye bestie, go convert something πŸ¦‹πŸ’…

πŸ“¦ where this page comes from