vztminer(1)

1VZTMINER(1)                  Dumpfile Data Mining                  VZTMINER(1)
2
3
4

NAME

6       vztminer - Data mining of VZT files
7

SYNTAX

9       vztminer [option]... [VZTFILE]
10

DESCRIPTION

12       Mines  VZT  files  for  specific data values and generates gtkwave save
13       files to stdout for future reload.
14

OPTIONS

16       -d,--dumpfile <filename>
17              Specify VZT input dumpfile.
18
19       -m,--match <value>
20              Specifies "bitwise" match data (binary, real, string)
21
22       -x,--hex <value>
23              Specifies hexadecimal match data that will automatically be con‐
24              verted to binary for searches
25
26       -n,--namesonly
27              Indicates  that  only  facnames  should  be printed in a gtkwave
28              savefile compatible format.  By doing this, the file can be used
29              to specify which traces are to be imported into gtkwave.
30
31       -c,--comprehensive
32              Indicates  that  results  are not to stop after the first match.
33              This can be used to extract  all  the  matching  values  in  the
34              trace.
35
36       -h,--help
37              Show help screen.
38

EXAMPLES

40       vztminer dumpfile.vzt --hex 20470000 -n
41
42       This attempts to match the hex value 20470000 across all facilities and
43       when the value is encountered, the facname only is printed to stdout in
44       order to generate a gtkwave compatible save file.
45

LIMITATIONS

47       vztminer  only  prints the first time a value is encountered for a spe‐
48       cific net.  This is done in order to cut down on  the  size  of  output
49       files  and to aid in following data such as addresses through a simula‐
50       tion model.  Note also that the reader  algorithm  attempts  to  recon‐
51       struct bitblasted nets back into their original vectors but this is not
52       always successful, specifically in the case where the  individual  bit‐
53       strands are dumped in non-sequential order.
54

AUTHORS

56       Anthony Bybell <bybell@nc.rr.com>
57