Hello,
I am currently evaluating your project as part of my Bachelors thesis. I think I might have found an error in the XML output of poseidon.
My parameters:
poseidon -m GRASP -p bitorus5x5.xml -t 60 -d -b 0 -s ./out.xml -a
I am using the provided bitorus architecture.
The output caused my parsing program to crash repeatedly so I decided to inspect the output manually.
The bug seems to be caused by unfinished overlap optimization.
In the shortened output below there should be a connection between (0,0) and (0,4).
It begins in timeslot 28 but it isn't continued.
There is no (0,4) timeslot 29 (due to overlap optimisation) but the incoming connection is not included in (0,4) timeslot 0.
Is:
<schedule length="29" width="5" height="5">
...
<tile id="(0,0)">
...
<timeslot value="28">
<na rx="(0,0)" tx="(0,4)" route="NL" chan-id="26" config-ch="false" pkt-id="0"/>
<router>
<output id="N" input="L"/>
<output id="S" input="D"/>
<output id="E" input="D"/>
<output id="W" input="D"/>
<output id="L" input="N"/>
</router>
</timeslot>
<latency>
...
<destination id="(0,4)" slotwaittime="29" channellatency="2" chan-id="26" chan-bw="1" config-ch="false" pkt-len="1" rate="0.034482758620689655"/>
...
</latency>
</tile>
...
<tile id="(0,4)">
<timeslot value="0">
<na rx="(0,4)" tx="(3,3)" route="WWNL" chan-id="94" config-ch="false" pkt-id="0"/>
<router>
<output id="N" input="D"/>
<output id="S" input="D"/>
<output id="E" input="D"/>
<output id="W" input="L"/>
<output id="L" input="D"/>
</router>
</timeslot>
...
<timeslot value="28">
<na rx="(0,3)" tx="(0,4)"/>
<router>
<output id="N" input="D"/>
<output id="S" input="D"/>
<output id="E" input="D"/>
<output id="W" input="D"/>
<output id="L" input="E"/>
</router>
</timeslot>
<latency>
...
</latency>
< / tile >
...
</schedule>
Should probably be:
<schedule length="29" width="5" height="5">
...
<tile id="(0,0)">
...
<timeslot value="28">
<na rx="(0,0)" tx="(0,4)" route="NL" chan-id="26" config-ch="false" pkt-id="0"/>
<router>
<output id="N" input="L"/>
<output id="S" input="D"/>
<output id="E" input="D"/>
<output id="W" input="D"/>
<output id="L" input="N"/>
</router>
</timeslot>
<latency>
...
<destination id="(0,4)" slotwaittime="29" channellatency="2" chan-id="26" chan-bw="1" config-ch="false" pkt-len="1" rate="0.034482758620689655"/>
...
</latency>
</tile>
...
<tile id="(0,4)">
<timeslot value="0">
<na rx="(0,4)" tx="(3,3)" route="WWNL" chan-id="94" config-ch="false" pkt-id="0"/>
<router>
<output id="N" input="D"/>
<output id="S" input="D"/>
<output id="E" input="D"/>
<output id="W" input="L"/>
<output id="L" input="S"/><- changed here
</router>
</timeslot>
...
<timeslot value="28">
<na rx="(0,3)" tx="(0,4)"/>
<router>
<output id="N" input="D"/>
<output id="S" input="D"/>
<output id="E" input="D"/>
<output id="W" input="D"/>
<output id="L" input="E"/>
</router>
</timeslot>
<latency>
...
</latency>
< / tile >
...
</schedule>
I had a quick look into the output code and there seems to be no adjustment of the schedule, so I assume that this is caused by a unfinished optimization.
out_broken.xml.zip
Greetings,
David
Hello,
I am currently evaluating your project as part of my Bachelors thesis. I think I might have found an error in the XML output of poseidon.
My parameters:
poseidon -m GRASP -p bitorus5x5.xml -t 60 -d -b 0 -s ./out.xml -a
I am using the provided bitorus architecture.
The output caused my parsing program to crash repeatedly so I decided to inspect the output manually.
The bug seems to be caused by unfinished overlap optimization.
In the shortened output below there should be a connection between (0,0) and (0,4).
It begins in timeslot 28 but it isn't continued.
There is no (0,4) timeslot 29 (due to overlap optimisation) but the incoming connection is not included in (0,4) timeslot 0.
Is:
<schedule length="29" width="5" height="5">...<tile id="(0,0)">...<timeslot value="28"><na rx="(0,0)" tx="(0,4)" route="NL" chan-id="26" config-ch="false" pkt-id="0"/><router><output id="N" input="L"/><output id="S" input="D"/><output id="E" input="D"/><output id="W" input="D"/><output id="L" input="N"/></router></timeslot><latency>...<destination id="(0,4)" slotwaittime="29" channellatency="2" chan-id="26" chan-bw="1" config-ch="false" pkt-len="1" rate="0.034482758620689655"/>...</latency></tile>...<tile id="(0,4)"><timeslot value="0"><na rx="(0,4)" tx="(3,3)" route="WWNL" chan-id="94" config-ch="false" pkt-id="0"/><router><output id="N" input="D"/><output id="S" input="D"/><output id="E" input="D"/><output id="W" input="L"/><output id="L" input="D"/></router></timeslot>...<timeslot value="28"><na rx="(0,3)" tx="(0,4)"/><router><output id="N" input="D"/><output id="S" input="D"/><output id="E" input="D"/><output id="W" input="D"/><output id="L" input="E"/></router></timeslot><latency>...</latency>< / tile >...</schedule>Should probably be:
<schedule length="29" width="5" height="5">...<tile id="(0,0)">...<timeslot value="28"><na rx="(0,0)" tx="(0,4)" route="NL" chan-id="26" config-ch="false" pkt-id="0"/><router><output id="N" input="L"/><output id="S" input="D"/><output id="E" input="D"/><output id="W" input="D"/><output id="L" input="N"/></router></timeslot><latency>...<destination id="(0,4)" slotwaittime="29" channellatency="2" chan-id="26" chan-bw="1" config-ch="false" pkt-len="1" rate="0.034482758620689655"/>...</latency></tile>...<tile id="(0,4)"><timeslot value="0"><na rx="(0,4)" tx="(3,3)" route="WWNL" chan-id="94" config-ch="false" pkt-id="0"/><router><output id="N" input="D"/><output id="S" input="D"/><output id="E" input="D"/><output id="W" input="L"/><output id="L" input="S"/><- changed here</router></timeslot>...<timeslot value="28"><na rx="(0,3)" tx="(0,4)"/><router><output id="N" input="D"/><output id="S" input="D"/><output id="E" input="D"/><output id="W" input="D"/><output id="L" input="E"/></router></timeslot><latency>...</latency>< / tile >...</schedule>I had a quick look into the output code and there seems to be no adjustment of the schedule, so I assume that this is caused by a unfinished optimization.
out_broken.xml.zip
Greetings,
David