Variable representation not optimal.

Open kubsztal opened this issue 6 years ago • 1 comments

Currently full signal path/name is used as a variable representation, e.g.: System1.Disco.Sensors.Accelerometer.AccX.

The standard says: "The value change dumper generates character identifier codes to represent variables. The identifier code is a code composed of the printable characters, which are in the ASCII character set from ! to ~ decimal 33 to 126)".

Using character identifier codes would be much more size efficient: merge_t1_t2.vcd with full signal names is almost 2MB. merge_t1_t2_.vcd with character identifier codes is 520kB. merge_t1_t2_.zip

Jan 07 '19 08:01 kubsztal

Thank you for logging this issue. Let's have it implemented in the next release. The current implementation was intentional. It allowed for easier vcd analysis. Anyway, vcdMaker is mature enough now to introduce the shorter identifiers.

Once again, thank you for your valuable feedback.

Jan 07 '19 21:01 WojciechRynczuk