FSTMINER(1)
π fstminer β okay bestie, let's go mining π
So like, this is fstminer from the Dumpfile Data Mining corner of the manual-verse, and its NAME section literally calls it fst2miner β yes, two different names, iconic behavior, we don't question it, we just vibe. Its whole deal: data mining of FST files. π¦
β¨ SYNTAX β¨
fstminer [option]... [FSTFILE]
That's it. That's the whole shape of it. Options, then maybe a file. π
πΈ DESCRIPTION πΈ
Okay so here's the tea: fstminer mines FST files for specific data values π₯ and then it generates gtkwave save files straight to stdout, so you can reload all that goodness later. It's giving "find the thing, write the receipt, come back to it whenever." π
π OPTIONS π
-d,--dumpfile<filename> β bestie, this is where you tell it which FST input dumpfile to read. π-m,--match<value> β here's where you drop the "bitwise" match data you want to hunt for. And when we say data, we mean it: binary, real, or string, all welcome. π-x,--hex<value> β same energy as--matchbut you're handing it hexadecimal match data, which it will auto-convert to binary for the search. No manual conversion labor required, we love a self-sufficient icon. β¨-n,--namesonlyβ this one says: print only facnames, in a gtkwave savefile compatible format. Why would you want that? Because then the file doubles as a shopping list of which traces you wanna import into gtkwave. Efficiency queen. π-c,--comprehensiveβ this says do NOT stop after the first match, keep going. Use it when you want to extract all the matching values in the trace. Go off, collect everything. π-h,--helpβ shows the help screen. The classic. The reliable. π«Ά
π EXAMPLES π
fstminer dumpfile.fst --hex 20470000 -n
So what's happening here: it tries to match the hex value 20470000 across all facilities, and the moment that value shows up, only the facname gets printed to stdout β specifically so you end up with a gtkwave compatible save file. Chef's kiss, exactly as intended. ππ
π LIMITATIONS π
Real talk, no cap: fstminer only prints the first time a value is encountered for a specific net. That's not a bug, it's a choice β it keeps the output files from getting thicc and it helps you actually follow data like addresses as they travel through a simulation model. So if you were expecting every single occurrence, this is your heads-up. π
π AUTHORS π
Anthony Bybell <bybell@rocketmail.com> β the legend themselves. π
π¦ SEE ALSO π¦
vztminer(1) lxt2miner(1) fst2vcd(1) vcd2fst(1) gtkwave(1)
Like, the whole friend group. Go say hi. β
Sign-off time, bestie: this lil masterpiece was brought to you by Anthony Bybell, version 3.3.38 of the FSTMINER(1) manual β and yeah, the original footer dates it and versions it, so here we are, mwah, go mine some data, periodt. π
β¨
π¦ 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 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