Line | |
---|
1 | |
---|
2 | read_order - Read and reorder variable order from a file. |
---|
3 | _________________________________________________________________ |
---|
4 | |
---|
5 | read_order [-h] [-v] [<file>] |
---|
6 | |
---|
7 | This command reads variable order from a file and reorder variable order |
---|
8 | according to the order. This command can be used any time after static_order |
---|
9 | command. However, the users should notice that there is a possibility to get |
---|
10 | BDD blowups during this command. |
---|
11 | |
---|
12 | Command options: |
---|
13 | |
---|
14 | -h |
---|
15 | Print the command usage. |
---|
16 | |
---|
17 | -g <group> |
---|
18 | Specify whether to group present and next state variables or not. |
---|
19 | |
---|
20 | 0: Do not group. |
---|
21 | |
---|
22 | 1: Do group (default). |
---|
23 | |
---|
24 | -v |
---|
25 | Print debug information. |
---|
26 | |
---|
27 | <file> |
---|
28 | A file containing names of network nodes, used to specify a variable |
---|
29 | ordering. The name of a node is the full hierarchical path name, |
---|
30 | starting from the current hierarchical node. A node should appear at |
---|
31 | most once in the file. Each node name should appear at the beginning |
---|
32 | of a new line, with no white space preceeding it. The end of a node |
---|
33 | name is marked by white space, and any other text on the rest of the |
---|
34 | line is ignored. Any line starting with "#" or white space is |
---|
35 | ignored. See write_order for a sample file. Note that the variable |
---|
36 | ordering cannot be specified at the bit-level; it can only be |
---|
37 | specified at the multi-valued variable level. |
---|
38 | _________________________________________________________________ |
---|
39 | |
---|
40 | Last updated on 20100410 00h02 |
---|
Note: See
TracBrowser
for help on using the repository browser.