DDS behaves differently when run twice with -trick

[GoogleCodeExporter]

Run test case dds-bug.tcl:

   deal -x bin/unit.tcl tests/dds-bug.tcl

Original issue reported on code.google.com by thomasoa on 28 Dec 2010 at 3:54

[GoogleCodeExporter]

So, I had dds call DumpInput and the only difference between the two calls is 
that the first uses mode=0, which should initialize the processing the first 
time.

This means that the problem is inside the DDS code, rather than in the code 
which calls it, I think.

Original comment by thomasoa on 28 Dec 2010 at 5:33

• Added labels: Component-DDS

[GoogleCodeExporter]

Ran several simulations to see the conditions under which this occurs.  Nothing 
clear yet, unfortunately.

Workaround is to force an extra call to DDS the very first time you call it.

Original comment by thomasoa on 28 Dec 2010 at 6:28

[GoogleCodeExporter]

Workaround:

   Add a dummy call to the dds command to lib/features.tcl:

     dds -diagram {{A - - -} {K - - -} {Q - - -} {J - - -}} south

Original comment by thomasoa on 28 Dec 2010 at 7:10

[GoogleCodeExporter]

Original comment by thomasoa on 28 Dec 2010 at 7:19

• Added labels: Milestone-3.1.10, OpSys-All

[GoogleCodeExporter]

So, apparently using mode=0 is the problem - should use mode=1 or mode=2.

Original comment by thomasoa on 28 Dec 2010 at 8:13