dirfile2ascii(1)

💖 dirfile2ascii — the GETDATA girlies' fave lil converter 💖

okay bestie, welcome to the dirfile2ascii(1) page, part of the GETDATA manual. she's the one who takes your dirfile database vectors and turns them into plain ASCII text so you can actually look at them. no cap, she's iconic.

---

✨ NAME ✨

dirfile2ascii — output dirfile database vectors as ASCII text

---

🌸 SYNOPSIS 🌸

dirfile2ascii [ OPTION ]... DIRFILE [ [ -a | -A | -e | -E | -F | -g | -G
       | -o | -i | -u | -x | -X ] FIELD ]...

---

🦋 DESCRIPTION 🦋

So the vibe is: she fetches data from a dirfile(5) database — that's the one you name as DIRFILE — and writes it out as ASCII to standard output. ✨ You can throw any number of vector FIELDs at her. Each field you specify gets printed in its own separate column. Slay.

Mandatory arguments to long options are mandatory for short options too. (yes queen, that's just how it is.)

💅 the options 💅

• -d, --delimeter=delim — separate columns by delim. (Default: a single space.) yes, it's spelled delimeter. we don't make the rules. 🙈
• -f, --first-frame=first_frame-last_frame — read from frame first_frame to frame last_frame, and yes, that range is inclusive.
• -f, --first-frame=first_frame:nframes — this is literally just shorthand, equivalent to --first-frame=first_frame --num-frames=nframes.
• -f, --first-frame=first_frame — if first_frame >= 0, start reading at frame first_frame. If first_frame is -1 and you also said --num-frames=nframes, she reads the last nframes frames. And if you don't specify --first-frame at all? reading starts at frame zero, no drama.
• -n, --num-frames=nframes — read at most nframes frames. If you don't specify it, or if nframes = 0, she reads all frames to the end-of-field. all of them. go off. 🔥
• -p, --precision=format — use format to format the output. format may contain any of the flag characters, a field width, and/or a precision as specified in printf(3). It may not contain a length modifier. (rude, but okay.)
• -q, --quiet — don't write diagnostic messages on standard error. (This is the default behaviour.) so it's the chill, no-commentary mode, which is already the vibe by default.
• -s, --skip=frame_skip — if frame_skip > 0, output only one sample for every frame_skip frames.
• -v, --verbose — write diagnostic messages on standard error. she's gonna talk. 🗣️
• -z, --fill=STRING — Fill columns which go past the end of their corresponding field with the string STRING. The default behaviour is to fill columns with floating-point conversions with NaN and columns with integer conversion with 0, which mirrors what occurs when an attempt is made to print data from before the start of a field. (Note: the default behaviour cannot be reproduced with this option, since STRING is applied to all columns, regardless of conversion type.) okay so heads up, that note is real and you can't fake the default with this flag. periodt.

🎀 the field conversions 🎀

In addition to all of the above, each FIELD argument may be preceded by a short option, one of: -a, -A, -e, -E, -F, -g, -G, -i, -o, -u, -x, -X, indicating the conversion to be used. See printf(3) for the meaning of these conversion specifiers. The output flags, width, and precision may be specified by using --precision. If no conversion specifier is given, %f is used. (default queen behaviour.)

and now the read-type tea, listen closely:

• For conversion specifiers %a, %A, %e, %E, %f, %F, %g, %G, data is read from the dirfile as double precision floats.
• For conversion specifier %i, data is read as 64-bit signed integers.
• For conversion specifiers %o, %u, %x, %X, data is read as 64-bit unsigned integers.

---

💀 LIMITATIONS 💀

No native support for printing complex data is provided. 😭 She does not do complex, she does not know her. This may be worked around by using dirfile(5) representation suffixes. For example, the command

dirfile2ascii DIRFILE FIELD.r FIELD.i

will print the real and imaginary parts of the complex valued field FIELD in the first and second columns, respectively. see? workaround ate. 💅

---

👑 AUTHOR 👑

dirfile2ascii was written by Matthew Truch and D. V. Wiebe.

---

🙈 REPORTING BUGS 🙈

Please send reports of bugs to getdata-devel@lists.sourceforge.net

The GetData home page: <http://getdata.sourceforge.net/>

---

🎀 COPYRIGHT 🎀

Copyright © 2010 Matthew Truch.

dirfile2ascii is licenced under the GNU LPGL version 2.1 or later.

This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.

fr fr, no warranty. she's free and she's yours to remix, but she comes as-is. 💜

---

🌈 SEE ALSO 🌈

defile(1), dirfile(5), printf(3)

---

okay that's the whole page bestie, you're basically a dirfile2ascii expert now 🫶 this was Version 0.8.0, dated 21 February 2012, and that's the whole dirfile2ascii(1) situation. mwah. 💖✨