VZTMINER(1)
β¨ VZTMINER(1) β Dumpfile Data Mining β¨
okay so bestie, welcome to vztminer, the VZT file data-mining tool, and yes this is section 1 of the manual because it's a command, not a config file or a syscall. π
Sit down, hydrate, let's get into it.
πΈ NAME πΈ
vztminer β data mining of VZT files π¦
π SYNTAX π
vztminer [option]... [VZTFILE]
π DESCRIPTION π
So basically vztminer mines VZT files looking for specific data values, and then it generates gtkwave save files and sends them straight to stdout so you can reload them later. That's the whole vibe. β¨
π OPTIONS π
-d,--dumpfile<filename>β tell it which VZT input dumpfile you wanna use, bestie. π-m,--match<value>β this one specifies a "bitwise" match for data. And the data can be binary, real, or string, so it's giving β¨versatileβ¨.-x,--hex<value>β same energy, but for hexadecimal match data. It gets automatically converted to binary for the searches, so you don't have to do it yourself. iconic. π₯-n,--namesonlyβ says only facnames should get printed, in a gtkwave savefile compatible format. Do this and the file can be used to specify which traces are to be imported into gtkwave. no cap, super handy. π-c,--comprehensiveβ this tells it not to stop after the first match. Use it to extract all the matching values in the trace. π-h,--helpβ show the help screen. π«Ά
π¦ EXAMPLES π¦
vztminer dumpfile.vzt --hex 20470000 -n
Okay so what's happening here: it attempts to match the hex value 20470000 across all facilities, and when that value gets encountered, only the facname is printed to stdout β which is exactly how you generate a gtkwave compatible save file. periodt. π
π LIMITATIONS π
Okay bestie, listen up, this part matters:
vztmineronly prints the first time a value is encountered for a specific net. It does this to cut down on the size of output files and to help you follow data like addresses through a simulation model. π- Also, heads up: the reader algorithm attempts to reconstruct bitblasted nets back into their original vectors, but this is not always successful. Specifically not when the individual bitstrands are dumped in non-sequential order. π so like, don't be surprised if it doesn't always work out.
π AUTHORS π
Anthony Bybell <bybell@rocketmail.com> β¨
β SEE ALSO β
lxt2miner(1) vzt2vcd(1) lxt2vcd(1) vcd2lxt2(1) gtkwave(1) πΈ
okay that's the whole page bestie, you ate it up π«Ά This was VZTMINER(1) from version 3.2.1, brought to you by Anthony Bybell β go forth and mine those dumpfiles πβ¨π
π¦ 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