VCD2LXT2(1)
π NAME π
okay bestie, gather round π this one's called vcd2lxt2 β and it's a Filetype Conversion girlie, section 1 of the manual. Her whole entire job? Turning VCD files into LXT2 files. That's it. That's the vibe. β¨
π SYNTAX π
vcd2lxt2 [option]... [VCDFILE] [LXTFILE]
πΈ DESCRIPTION πΈ
Converts VCD files to LXT2 files. no cap, that's literally the whole description, she's a simple queen π
β¨ OPTIONS β¨
-v,--vcdname <filename>β tells her which VCD file to read in. that's your input, bestie π«Ά-l,--lxtname <filename>β names the LXT2 file she's gonna write out. your output π-d,--depth <value>β gzip compression depth,0..9. default is4. crank it up for more squeeze π₯-m,--maxgranule <value>β how many granules fit in each section. default is8. and just so you know, one granule is equal to 32 timsteps β-b,--break <value>β sets the break size, and the default is0, which means off. the tea here: once you go over the break size, the LXT2 dumper dumps all the state information at the next convenient granule plus dictionary boundary. yes that's a lot of state, she's being thorough π-p,--partialmode <mode>β partial zip mode.0= monolithic,1= separation. choosing1makes the LXT2 file bigger but gives you fast access for very large traces. β οΈ and heads up: the default mode is neither monolithic nor separation β partial zip is disabled out of the box. she's just like that π-c,--checkpoint <mode>β checkpoint mode.0is on, which is the default, and1is off. β οΈ this gets disabled whenever the break size is active, so don't expect both at once.-h,--helpβ shows the help screen. your bestie when you forget everything π
π EXAMPLES π
okay so real quick: you should specify dumpfile.vcd directly, or use "-" for stdin. don't overthink it π¦
vcd2lxt dumpfile.vcd dumpfile.lxt --depth 9 --break 1073741824
this sets the compression level to 9 and the break size to 1GB. big girl numbers π
vcd2lxt dumpfile.vcd dumpfile.lxt --depth 9 --maxgranule 256
this one allows more granules per section, which lets you get greater compression. more granules = more squeeze, periodt π₯
π LIMITATIONS π
vcd2lxt2 does not store glitches. nope. not even a little. because those glitches get coalesced together into one single value change while the LXT2 file is being written. so if you were hoping to see every tiny flicker β she said no π
π AUTHORS π
Anthony Bybell <bybell@rocketmail.com> β the icon behind all of this, we stan π«Ά
π§ SEE ALSO π§
lxt2vcd(1), vcd2lxt2(1), gtkwave(1) β go read those too, iykyk π
and that's a wrap, bestie π this whole page is from version 1.3.42, and it belongs to Anthony Bybell β that's the name at the bottom of the original too, so shoutout to him. go convert some files, you got this πβ¨
π¦ where this page comes from
- arch rolling: gtkwave 3.3.128-1 Β· GPL-2.0-or-later AND MIT
- debian bookworm: gtkwave 3.3.118-0.1~deb12u1
- debian trixie: gtkwave 3.3.121-1
- epel 10: gtkwave 3.3.128-1.el10_3 Β· GPL-2.0-or-later
- epel 9: gtkwave 3.3.118-1.el9 Β· GPL-2.0-or-later
- fedora 43: gtkwave 3.3.125-1.fc43 Β· GPL-2.0-or-later
- fedora 44: gtkwave 3.3.126-2.fc44 Β· GPL-2.0-or-later
- fedora 44: gtkwave 3.3.127-1.fc44 Β· GPL-2.0-or-later
- nixos 26.05: gtkwave 3.3.127
- nixpkgs unstable: gtkwave 3.3.128
- opensuse-leap 16.0: gtkwave 3.3.114-bp160.1.12 Β· GPL-2.0-or-later
- opensuse-leap 16.0: gtkwave 3.3.114-bp160.1.12 Β· GPL-2.0-or-later
- opensuse-leap 16.0: gtkwave 3.3.114-bp160.1.12 Β· GPL-2.0-or-later
- opensuse-leap 16.0: gtkwave 3.3.114-bp160.1.12 Β· GPL-2.0-or-later
- ubuntu jammy: gtkwave 3.3.104-2build1
- ubuntu noble: gtkwave 3.3.116-1build2
- ubuntu questing: gtkwave 3.3.125-1
- ubuntu resolute: gtkwave 3.3.126-1
- ubuntu stonking: gtkwave 3.3.127-1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms