UNU-SAVE(1)

💖 UNU-SAVE 💖

okay bestie, buckle up, because this is unu-save — yes, the one from the unu crew, and the whole page is filed under UNU-SAVE(). it's giving "small tool, big main character energy" and honestly? we're obsessed. 🎀

---

✨ NAME ✨

unu-save — write nrrd with specific format, encoding, or endianness 🌸

---

🦋 SYNOPSIS 🦋

unu save -f,--format <form> [-e,--encoding <enc>] [-en,--endian <end>]
[-i,--input <nin>] [-o,--output <nout>] [-od,--ouputdata <name>]

no cap, that's the whole vibe check: -f is the only thing you gotta bring, everything else is optional. 💅

---

🌈 DESCRIPTION 🌈

so what does it do? it writes nrrd with a specific format, encoding, or endianness. literally that's the job. 🫶

and here's a lil trick that slays — pipe it into xv like this:

unu save -f pnm | xv -

that's how you view PPM- or PGM-compatible nrrds on unix. iconic behavior, honestly. ✨

EPS output? okay so it's an EPSF-3.0 file with BoundingBox and HiResBoundingBox DSC comments, and it is suitable for inclusion into other PostScript documents. and as a stand-alone file, the image is conveniently centered on an 8.5x11 inch page, with 0.5 inch margins. thoughtful! 💖

• Uses various fields in the NrrdIOState passed to nrrdSave

---

🎀 OPTIONS 🎀

• -f <form>, --format <form> — the output file format. the possibilities include:
  • "nrrd": standard nrrd format
  • "pnm": PNM image; PPM for color, PGM for grayscale
  • "text": plain ASCII text for 1-D and 2-D data
  • "vtk": VTK "STRUCTURED_POINTS" dataset
  • "png": PNG image
  • "eps": EPS file
• -e <enc>, --encoding <enc> — the encoding of data in the file. heads up bestie: not all encodings are supported in a given format. the possibilities include:
  • "raw": raw encoding
  • "ascii": print data in ascii
  • "hex": two hex digits per byte
  • "gzip", "gz": gzip compressed raw data
  • "bzip2", "bz2": bzip2 compressed raw data

so here's the tea on the compression specifiers: they may be followed by a colon ":", followed by an optional digit giving compression "level" (for gzip) or "block size" (for bzip2). and for gzip, this can be followed by an optional character for a compression strategy:

• "d": default, Huffman with string match
• "h": Huffman alone
• "f": specialized for filtered data

for example, "gz", "gz:9", "gz:9f" are all valid 🌟

• -en <end>, --endian <end> — the endianness to save data out as; "little" for Intel and friends; "big" for everyone else. defaults to the endianness of this machine 👑
• -i <nin>, --input <nin> — input nrrd
• -o <nout>, --output <nout> — output nrrd (string); default: "-" 💜
• -od <name>, --ouputdata <name> — when saving to a ".nhdr" file, this option allows you to explicitly name the data file, instead of (by default, not using this option) having it be the same filename base as the header file. (string) 🍓

---

💀 SEE ALSO 💀

• unu(1)
• http://www.trilon.com/xv/

---

okay that's the whole page, and yes, the footer at the very bottom is just UNU-SAVE() — no version, no date, no source, just the name again being dramatic. that's it, that's the whole thing. go write some nrrds bestie, i believe in you 💅✨🦋