VCD2VZT(1)

💖 VCD2VZT 💖

okay so bestie, welcome to vcd2vzt — a lil filetype conversion tool from the Unix manual (section 1, iykyk) and she is literally here to turn your VCD files into VZT files. no cap. let's get into it ✨

🌸 NAME 🌸

vcd2vzt — converts VCD files to VZT files 💅

🎀 SYNTAX 🎀

vcd2vzt [option]... [VCDFILE] [VZTFILE]

so it's giving options, then your input file, then your output file. iconic behavior fr fr 🦋

✨ DESCRIPTION ✨

okay so the whole vibe: converts VCD files to VZT files. that's it, that's the job, and she does it flawlessly 💖

👑 OPTIONS 👑

• -v, --vcdname <filename> — tells her which VCD input filename you want. yes bestie, name your source 💅
• -l, --vztname <filename> — specifies the VZT output filename. the destination, the moment, the main character ✨
• -d, --depth <value> — sets the gzip compression depth, and it's gotta be in the 0..9 range. default is 4. lowkey the compression dial 🎀
• -m, --maxgranule <value> — how many granules per section, default is 8. and heads up: one granule equals 32 timesteps. yes really, that's the math 🦋
• -b, --break <value> — sets the break size (default = 0 = off). when the break size gets exceeded, the VZT dumper will dump all state information at the next convenient granule plus dictionary boundary. so it's the "oh we're breaking here" button 💀
• -z, --ziptype <value> — picks the zip type: default = 0 gzip, 1 = bzip2, 2 = lzma. this lets you override the default compression algorithm for a more effective one, at the expense of greater runtime. and ngl, important tea: bzip2 does not decompress as fast as gzip, so the viewer will be about two times slower when decompressing blocks. so like, pick your fighter 😭
• -t, --twostate — forces MVL2 twostate mode (default is MVL4). when it's enabled, the trace will only store 0/1 values for binary facilities. super useful for functional simulation, and it'll speed up dumping as well as make traces somewhat smaller. we love a win-win 🫶
• -r, --rle — uses a bitwise RLE compression on the value table. default is off. when enabled, this causes the trace data table to be stored using an alternate representation which can improve compression in many cases. the glow-up option 🌈
• -h, --help — shows the help screen. your emergency bestie when you forget everything 💖

⭐ EXAMPLES ⭐

quick note bestie: you should specify dumpfile.vcd directly, or use "-" for stdin. ok now the good stuff 👇

vcd2vzt dumpfile.vcd dumpfile.lxt --depth 9 --break 1073741824

this sets the compression level to 9 and sets the break size to 1GB. she's tuned, she's ready, she's serving 🔥

vcd2vzt dumpfile.vcd dumpfile.lxt --depth 9 --maxgranule 512

this allows more granules per section, which allows for greater compression at the expense of memory usage. more compression, more memory, the eternal tradeoff, periodt 💅

💀 LIMITATIONS 💀

okay so real talk: vcd2vzt does not store glitches, because these are coalesced together into one value change during the writing of the VZT file. so like, the tiny messy in-between moments? gone. merged. not me being emotionally devastated by a file format 😭

🧚 AUTHORS 🧚

Anthony Bybell <bybell@rocketmail.com> — the icon, the legend, the moment 💜

🌈 SEE ALSO 🌈

vzt2vcd(1) lxt2vcd(1) vcd2lxt2(1) gtkwave(1) — go read the whole friend group bestie, they're all slaying in their own way 🫶

and that's the whole page!! this one's Anthony Bybell, version 3.1.21 of the VCD2VZT(1) manual, and honestly? she ate. go convert something gorgeous, bestie 💖✨🎀🦋🌸💅