Section 6: Warnings

• Type 2: Variable The state of the link from node 0 to node 1(0L1_state) is not modified, value is constant.
• Type 2: Variable The state of the link from node 1 to node 2(1L2_state) is not modified, value is constant.
• Type 2: Variable The state of the link from node 2 to node 3(2L3_state) is not modified, value is constant.
• Type 2: Variable The state of the link from node 3 to node 4(3L4_state) is not modified, value is constant.
• Type 2: Variable The state of the link from node 4 to node 5(4L5_state) is not modified, value is constant.
• Type 2: Variable The state of the link from node 5 to node 6(5L6_state) is not modified, value is constant.
• Type 2: Variable The state of the link from node 6 to node 0(6L0_state) is not modified, value is constant.
• Type 2: Variable Number of packets dropped by node 0(node0_dropped) is not modified, value is constant.
• Type 2: Variable State of node 0(node0_state) is not modified, value is constant.
• Type 2: Variable Number of packets dropped by node 1(node1_dropped) is not modified, value is constant.
• Type 2: Variable State of node 1(node1_state) is not modified, value is constant.
• Type 2: Variable Number of packets dropped by node 2(node2_dropped) is not modified, value is constant.
• Type 2: Variable State of node 2(node2_state) is not modified, value is constant.
• Type 2: Variable Number of packets dropped by node 3(node3_dropped) is not modified, value is constant.
• Type 2: Variable State of node 3(node3_state) is not modified, value is constant.
• Type 2: Variable Number of packets dropped by node 4(node4_dropped) is not modified, value is constant.
• Type 2: Variable State of node 4(node4_state) is not modified, value is constant.
• Type 2: Variable Number of packets dropped by node 5(node5_dropped) is not modified, value is constant.
• Type 2: Variable State of node 5(node5_state) is not modified, value is constant.
• Type 2: Variable Number of packets dropped by node 6(node6_dropped) is not modified, value is constant.
• Type 2: Variable State of node 6(node6_state) is not modified, value is constant.
• Type 4: Variable Number of packets received by node 0(node0_received) is monotonously non decreasing.
• Type 4: Variable Number of packets sent by node 0(node0_sent) is monotonously non decreasing.
• Type 4: Variable Number of packets received by node 1(node1_received) is monotonously non decreasing.
• Type 4: Variable Number of packets sent by node 1(node1_sent) is monotonously non decreasing.
• Type 4: Variable Number of packets received by node 2(node2_received) is monotonously non decreasing.
• Type 4: Variable Number of packets sent by node 2(node2_sent) is monotonously non decreasing.
• Type 4: Variable Number of packets received by node 3(node3_received) is monotonously non decreasing.
• Type 4: Variable Number of packets sent by node 3(node3_sent) is monotonously non decreasing.
• Type 4: Variable Number of packets received by node 4(node4_received) is monotonously non decreasing.
• Type 4: Variable Number of packets sent by node 4(node4_sent) is monotonously non decreasing.
• Type 4: Variable Number of packets received by node 5(node5_received) is monotonously non decreasing.
• Type 4: Variable Number of packets sent by node 5(node5_sent) is monotonously non decreasing.
• Type 4: Variable Number of packets received by node 6(node6_received) is monotonously non decreasing.
• Type 4: Variable Number of packets sent by node 6(node6_sent) is monotonously non decreasing.
• Type 5: Action Link connecting node 0 to node 1 went down(0L1_DOWN) is declared, but does not occur in the trace.
• Type 5: Action Link connecting node 0 to node 1 went online(0L1_UP) is declared, but does not occur in the trace.
• Type 5: Action Link connecting node 1 to node 2 went down(1L2_DOWN) is declared, but does not occur in the trace.
• Type 5: Action Link connecting node 1 to node 2 went online(1L2_UP) is declared, but does not occur in the trace.
• Type 5: Action Link connecting node 2 to node 3 went down(2L3_DOWN) is declared, but does not occur in the trace.
• Type 5: Action Link connecting node 2 to node 3 went online(2L3_UP) is declared, but does not occur in the trace.
• Type 5: Action Link connecting node 3 to node 4 went down(3L4_DOWN) is declared, but does not occur in the trace.
• Type 5: Action Link connecting node 3 to node 4 went online(3L4_UP) is declared, but does not occur in the trace.
• Type 5: Action Link connecting node 4 to node 5 went down(4L5_DOWN) is declared, but does not occur in the trace.
• Type 5: Action Link connecting node 4 to node 5 went online(4L5_UP) is declared, but does not occur in the trace.
• Type 5: Action Link connecting node 5 to node 6 went down(5L6_DOWN) is declared, but does not occur in the trace.
• Type 5: Action Link connecting node 5 to node 6 went online(5L6_UP) is declared, but does not occur in the trace.
• Type 5: Action Link connecting node 6 to node 0 went down(6L0_DOWN) is declared, but does not occur in the trace.
• Type 5: Action Link connecting node 6 to node 0 went online(6L0_UP) is declared, but does not occur in the trace.
• Type 5: Action Node 0 down(node0_DOWN) is declared, but does not occur in the trace.
• Type 5: Action Node 0 up(node0_UP) is declared, but does not occur in the trace.
• Type 5: Action Node 0 dropped packet to node 1(node0_d_node1) is declared, but does not occur in the trace.
• Type 5: Action Node 0 dropped packet to node 6(node0_d_node6) is declared, but does not occur in the trace.
• Type 5: Action Node 1 down(node1_DOWN) is declared, but does not occur in the trace.
• Type 5: Action Node 1 up(node1_UP) is declared, but does not occur in the trace.
• Type 5: Action Node 1 dropped packet to node 0(node1_d_node0) is declared, but does not occur in the trace.
• Type 5: Action Node 1 dropped packet to node 2(node1_d_node2) is declared, but does not occur in the trace.
• Type 5: Action Node 2 down(node2_DOWN) is declared, but does not occur in the trace.
• Type 5: Action Node 2 up(node2_UP) is declared, but does not occur in the trace.
• Type 5: Action Node 2 dropped packet to node 1(node2_d_node1) is declared, but does not occur in the trace.
• Type 5: Action Node 2 dropped packet to node 3(node2_d_node3) is declared, but does not occur in the trace.
• Type 5: Action Node 3 down(node3_DOWN) is declared, but does not occur in the trace.
• Type 5: Action Node 3 up(node3_UP) is declared, but does not occur in the trace.
• Type 5: Action Node 3 dropped packet to node 2(node3_d_node2) is declared, but does not occur in the trace.
• Type 5: Action Node 3 dropped packet to node 4(node3_d_node4) is declared, but does not occur in the trace.
• Type 5: Action Node 4 down(node4_DOWN) is declared, but does not occur in the trace.
• Type 5: Action Node 4 up(node4_UP) is declared, but does not occur in the trace.
• Type 5: Action Node 4 dropped packet to node 3(node4_d_node3) is declared, but does not occur in the trace.
• Type 5: Action Node 4 dropped packet to node 5(node4_d_node5) is declared, but does not occur in the trace.
• Type 5: Action Node 5 down(node5_DOWN) is declared, but does not occur in the trace.
• Type 5: Action Node 5 up(node5_UP) is declared, but does not occur in the trace.
• Type 5: Action Node 5 dropped packet to node 4(node5_d_node4) is declared, but does not occur in the trace.
• Type 5: Action Node 5 dropped packet to node 6(node5_d_node6) is declared, but does not occur in the trace.
• Type 5: Action Node 6 down(node6_DOWN) is declared, but does not occur in the trace.
• Type 5: Action Node 6 up(node6_UP) is declared, but does not occur in the trace.
• Type 5: Action Node 6 dropped packet to node 0(node6_d_node0) is declared, but does not occur in the trace.
• Type 5: Action Node 6 dropped packet to node 5(node6_d_node5) is declared, but does not occur in the trace.
• Type 9: Action Link connecting node 0 to node 1 went down(0L1_DOWN) is not present in any cycles observed in this trace.
• Type 9: Action Link connecting node 0 to node 1 went online(0L1_UP) is not present in any cycles observed in this trace.
• Type 9: Action Link connecting node 1 to node 2 went down(1L2_DOWN) is not present in any cycles observed in this trace.
• Type 9: Action Link connecting node 1 to node 2 went online(1L2_UP) is not present in any cycles observed in this trace.
• Type 9: Action Link connecting node 2 to node 3 went down(2L3_DOWN) is not present in any cycles observed in this trace.
• Type 9: Action Link connecting node 2 to node 3 went online(2L3_UP) is not present in any cycles observed in this trace.
• Type 9: Action Link connecting node 3 to node 4 went down(3L4_DOWN) is not present in any cycles observed in this trace.
• Type 9: Action Link connecting node 3 to node 4 went online(3L4_UP) is not present in any cycles observed in this trace.
• Type 9: Action Link connecting node 4 to node 5 went down(4L5_DOWN) is not present in any cycles observed in this trace.
• Type 9: Action Link connecting node 4 to node 5 went online(4L5_UP) is not present in any cycles observed in this trace.
• Type 9: Action Link connecting node 5 to node 6 went down(5L6_DOWN) is not present in any cycles observed in this trace.
• Type 9: Action Link connecting node 5 to node 6 went online(5L6_UP) is not present in any cycles observed in this trace.
• Type 9: Action Link connecting node 6 to node 0 went down(6L0_DOWN) is not present in any cycles observed in this trace.
• Type 9: Action Link connecting node 6 to node 0 went online(6L0_UP) is not present in any cycles observed in this trace.
• Type 9: Action Node 0 down(node0_DOWN) is not present in any cycles observed in this trace.
• Type 9: Action Node 0 up(node0_UP) is not present in any cycles observed in this trace.
• Type 9: Action Node 0 dropped packet to node 1(node0_d_node1) is not present in any cycles observed in this trace.
• Type 9: Action Node 0 dropped packet to node 6(node0_d_node6) is not present in any cycles observed in this trace.
• Type 9: Action Packet hopping from node 0 to node 1(node0_h_0L1) is not present in any cycles observed in this trace.
• Type 9: Action Packet hopping from node 0 to node 6(node0_h_6L0) is not present in any cycles observed in this trace.
• Type 9: Action Node 0 receiving packet from node 1(node0_r_0L1) is not present in any cycles observed in this trace.
• Type 9: Action Node 0 receiving packet from node 6(node0_r_6L0) is not present in any cycles observed in this trace.
• Type 9: Action Node 1 down(node1_DOWN) is not present in any cycles observed in this trace.
• Type 9: Action Node 1 up(node1_UP) is not present in any cycles observed in this trace.
• Type 9: Action Node 1 dropped packet to node 0(node1_d_node0) is not present in any cycles observed in this trace.
• Type 9: Action Node 1 dropped packet to node 2(node1_d_node2) is not present in any cycles observed in this trace.
• Type 9: Action Packet hopping from node 1 to node 0(node1_h_0L1) is not present in any cycles observed in this trace.
• Type 9: Action Packet hopping from node 1 to node 2(node1_h_1L2) is not present in any cycles observed in this trace.
• Type 9: Action Node 1 receiving packet from node 0(node1_r_0L1) is not present in any cycles observed in this trace.
• Type 9: Action Node 1 receiving packet from node 2(node1_r_1L2) is not present in any cycles observed in this trace.
• Type 9: Action Node 2 down(node2_DOWN) is not present in any cycles observed in this trace.
• Type 9: Action Node 2 up(node2_UP) is not present in any cycles observed in this trace.
• Type 9: Action Node 2 dropped packet to node 1(node2_d_node1) is not present in any cycles observed in this trace.
• Type 9: Action Node 2 dropped packet to node 3(node2_d_node3) is not present in any cycles observed in this trace.
• Type 9: Action Packet hopping from node 2 to node 1(node2_h_1L2) is not present in any cycles observed in this trace.
• Type 9: Action Packet hopping from node 2 to node 3(node2_h_2L3) is not present in any cycles observed in this trace.
• Type 9: Action Node 2 receiving packet from node 1(node2_r_1L2) is not present in any cycles observed in this trace.
• Type 9: Action Node 2 receiving packet from node 3(node2_r_2L3) is not present in any cycles observed in this trace.
• Type 9: Action Node 3 down(node3_DOWN) is not present in any cycles observed in this trace.
• Type 9: Action Node 3 up(node3_UP) is not present in any cycles observed in this trace.
• Type 9: Action Node 3 dropped packet to node 2(node3_d_node2) is not present in any cycles observed in this trace.
• Type 9: Action Node 3 dropped packet to node 4(node3_d_node4) is not present in any cycles observed in this trace.
• Type 9: Action Packet hopping from node 3 to node 2(node3_h_2L3) is not present in any cycles observed in this trace.
• Type 9: Action Packet hopping from node 3 to node 4(node3_h_3L4) is not present in any cycles observed in this trace.
• Type 9: Action Node 3 receiving packet from node 2(node3_r_2L3) is not present in any cycles observed in this trace.
• Type 9: Action Node 3 receiving packet from node 4(node3_r_3L4) is not present in any cycles observed in this trace.
• Type 9: Action Node 4 down(node4_DOWN) is not present in any cycles observed in this trace.
• Type 9: Action Node 4 up(node4_UP) is not present in any cycles observed in this trace.
• Type 9: Action Node 4 dropped packet to node 3(node4_d_node3) is not present in any cycles observed in this trace.
• Type 9: Action Node 4 dropped packet to node 5(node4_d_node5) is not present in any cycles observed in this trace.
• Type 9: Action Packet hopping from node 4 to node 3(node4_h_3L4) is not present in any cycles observed in this trace.
• Type 9: Action Packet hopping from node 4 to node 5(node4_h_4L5) is not present in any cycles observed in this trace.
• Type 9: Action Node 4 receiving packet from node 3(node4_r_3L4) is not present in any cycles observed in this trace.
• Type 9: Action Node 4 receiving packet from node 5(node4_r_4L5) is not present in any cycles observed in this trace.
• Type 9: Action Node 5 down(node5_DOWN) is not present in any cycles observed in this trace.
• Type 9: Action Node 5 up(node5_UP) is not present in any cycles observed in this trace.
• Type 9: Action Node 5 dropped packet to node 4(node5_d_node4) is not present in any cycles observed in this trace.
• Type 9: Action Node 5 dropped packet to node 6(node5_d_node6) is not present in any cycles observed in this trace.
• Type 9: Action Packet hopping from node 5 to node 4(node5_h_4L5) is not present in any cycles observed in this trace.
• Type 9: Action Packet hopping from node 5 to node 6(node5_h_5L6) is not present in any cycles observed in this trace.
• Type 9: Action Node 5 receiving packet from node 4(node5_r_4L5) is not present in any cycles observed in this trace.
• Type 9: Action Node 5 receiving packet from node 6(node5_r_5L6) is not present in any cycles observed in this trace.
• Type 9: Action Node 6 down(node6_DOWN) is not present in any cycles observed in this trace.
• Type 9: Action Node 6 up(node6_UP) is not present in any cycles observed in this trace.
• Type 9: Action Node 6 dropped packet to node 0(node6_d_node0) is not present in any cycles observed in this trace.
• Type 9: Action Node 6 dropped packet to node 5(node6_d_node5) is not present in any cycles observed in this trace.
• Type 9: Action Packet hopping from node 6 to node 5(node6_h_5L6) is not present in any cycles observed in this trace.
• Type 9: Action Packet hopping from node 6 to node 0(node6_h_6L0) is not present in any cycles observed in this trace.
• Type 9: Action Node 6 receiving packet from node 5(node6_r_5L6) is not present in any cycles observed in this trace.
• Type 9: Action Node 6 receiving packet from node 0(node6_r_6L0) is not present in any cycles observed in this trace.
• Type 10: Action Packet hopping from node 0 to node 1(node0_h_0L1) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Packet hopping from node 0 to node 6(node0_h_6L0) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Node 0 receiving packet from node 1(node0_r_0L1) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Node 0 receiving packet from node 6(node0_r_6L0) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Packet hopping from node 1 to node 0(node1_h_0L1) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Packet hopping from node 1 to node 2(node1_h_1L2) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Node 1 receiving packet from node 0(node1_r_0L1) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Node 1 receiving packet from node 2(node1_r_1L2) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Packet hopping from node 2 to node 1(node2_h_1L2) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Packet hopping from node 2 to node 3(node2_h_2L3) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Node 2 receiving packet from node 1(node2_r_1L2) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Node 2 receiving packet from node 3(node2_r_2L3) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Packet hopping from node 3 to node 2(node3_h_2L3) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Packet hopping from node 3 to node 4(node3_h_3L4) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Node 3 receiving packet from node 2(node3_r_2L3) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Node 3 receiving packet from node 4(node3_r_3L4) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Packet hopping from node 4 to node 3(node4_h_3L4) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Packet hopping from node 4 to node 5(node4_h_4L5) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Node 4 receiving packet from node 3(node4_r_3L4) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Node 4 receiving packet from node 5(node4_r_4L5) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Packet hopping from node 5 to node 4(node5_h_4L5) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Packet hopping from node 5 to node 6(node5_h_5L6) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Node 5 receiving packet from node 4(node5_r_4L5) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Node 5 receiving packet from node 6(node5_r_5L6) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Packet hopping from node 6 to node 5(node6_h_5L6) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Packet hopping from node 6 to node 0(node6_h_6L0) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Node 6 receiving packet from node 5(node6_r_5L6) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 10: Action Node 6 receiving packet from node 0(node6_r_6L0) is not element of any action invariant computed for the linear state transformations performed by the actions of this trace.
• Type 11: Variable Number of packets received by node 0(node0_received) is not element of any variable invariant computed for the linear state transformations performed by the actions of this trace.
• Type 11: Variable Number of packets sent by node 0(node0_sent) is not element of any variable invariant computed for the linear state transformations performed by the actions of this trace.
• Type 11: Variable Number of packets received by node 1(node1_received) is not element of any variable invariant computed for the linear state transformations performed by the actions of this trace.
• Type 11: Variable Number of packets sent by node 1(node1_sent) is not element of any variable invariant computed for the linear state transformations performed by the actions of this trace.
• Type 11: Variable Number of packets received by node 2(node2_received) is not element of any variable invariant computed for the linear state transformations performed by the actions of this trace.
• Type 11: Variable Number of packets sent by node 2(node2_sent) is not element of any variable invariant computed for the linear state transformations performed by the actions of this trace.
• Type 11: Variable Number of packets received by node 3(node3_received) is not element of any variable invariant computed for the linear state transformations performed by the actions of this trace.
• Type 11: Variable Number of packets sent by node 3(node3_sent) is not element of any variable invariant computed for the linear state transformations performed by the actions of this trace.
• Type 11: Variable Number of packets received by node 4(node4_received) is not element of any variable invariant computed for the linear state transformations performed by the actions of this trace.
• Type 11: Variable Number of packets sent by node 4(node4_sent) is not element of any variable invariant computed for the linear state transformations performed by the actions of this trace.
• Type 11: Variable Number of packets received by node 5(node5_received) is not element of any variable invariant computed for the linear state transformations performed by the actions of this trace.
• Type 11: Variable Number of packets sent by node 5(node5_sent) is not element of any variable invariant computed for the linear state transformations performed by the actions of this trace.
• Type 11: Variable Number of packets received by node 6(node6_received) is not element of any variable invariant computed for the linear state transformations performed by the actions of this trace.
• Type 11: Variable Number of packets sent by node 6(node6_sent) is not element of any variable invariant computed for the linear state transformations performed by the actions of this trace.
• Type 15: Variable Number of packets received by node 0(node0_received) may deadlock, because it seems to increase to an upper bound and then becomes constant for the rest of the trace ( 75.30 percent of the trace).
• Type 15: Variable Number of packets sent by node 3(node3_sent) may deadlock, because it seems to increase to an upper bound and then becomes constant for the rest of the trace ( 80.80 percent of the trace).
• Type 15: Variable Number of packets received by node 4(node4_received) may deadlock, because it seems to increase to an upper bound and then becomes constant for the rest of the trace ( 74.50 percent of the trace).
• Type 15: Variable Number of packets sent by node 4(node4_sent) may deadlock, because it seems to increase to an upper bound and then becomes constant for the rest of the trace ( 76.20 percent of the trace).
• Type 15: Variable Number of packets received by node 5(node5_received) may deadlock, because it seems to increase to an upper bound and then becomes constant for the rest of the trace ( 76.00 percent of the trace).
• Type 15: Variable Number of packets sent by node 5(node5_sent) may deadlock, because it seems to increase to an upper bound and then becomes constant for the rest of the trace ( 74.60 percent of the trace).
• Type 15: Variable Number of packets received by node 6(node6_received) may deadlock, because it seems to increase to an upper bound and then becomes constant for the rest of the trace ( 74.40 percent of the trace).
• Type 15: Variable Number of packets sent by node 6(node6_sent) may deadlock, because it seems to increase to an upper bound and then becomes constant for the rest of the trace ( 77.00 percent of the trace).
• Type 16: Action Node 0 enqueued packet to node 6(node0_+_node6) may deadlock, because it occurs the last time at event 183 and is not seen for the remaining 81.70 percent of the trace.
• Type 16: Action Node 0 dequeued packet to node 6(node0_-_node6) may deadlock, because it occurs the last time at event 184 and is not seen for the remaining 81.60 percent of the trace.
• Type 16: Action Packet hopping from node 0 to node 6(node0_h_6L0) may deadlock, because it occurs the last time at event 185 and is not seen for the remaining 81.50 percent of the trace.
• Type 16: Action Node 0 receiving packet from node 1(node0_r_0L1) may deadlock, because it occurs the last time at event 247 and is not seen for the remaining 75.30 percent of the trace.
• Type 16: Action Node 0 receiving packet from node 6(node0_r_6L0) may deadlock, because it occurs the last time at event 231 and is not seen for the remaining 76.90 percent of the trace.
• Type 16: Action Node 1 enqueued packet to node 0(node1_+_node0) may deadlock, because it occurs the last time at event 241 and is not seen for the remaining 75.90 percent of the trace.
• Type 16: Action Node 1 dequeued packet to node 0(node1_-_node0) may deadlock, because it occurs the last time at event 242 and is not seen for the remaining 75.80 percent of the trace.
• Type 16: Action Packet hopping from node 1 to node 0(node1_h_0L1) may deadlock, because it occurs the last time at event 243 and is not seen for the remaining 75.70 percent of the trace.
• Type 16: Action Node 1 receiving packet from node 2(node1_r_1L2) may deadlock, because it occurs the last time at event 221 and is not seen for the remaining 77.90 percent of the trace.
• Type 16: Action Node 2 enqueued packet to node 1(node2_+_node1) may deadlock, because it occurs the last time at event 198 and is not seen for the remaining 80.20 percent of the trace.
• Type 16: Action Node 2 dequeued packet to node 1(node2_-_node1) may deadlock, because it occurs the last time at event 199 and is not seen for the remaining 80.10 percent of the trace.
• Type 16: Action Packet hopping from node 2 to node 1(node2_h_1L2) may deadlock, because it occurs the last time at event 200 and is not seen for the remaining 80.00 percent of the trace.
• Type 16: Action Node 2 receiving packet from node 3(node2_r_2L3) may deadlock, because it occurs the last time at event 219 and is not seen for the remaining 78.10 percent of the trace.
• Type 16: Action Node 3 enqueued packet to node 2(node3_+_node2) may deadlock, because it occurs the last time at event 187 and is not seen for the remaining 81.30 percent of the trace.
• Type 16: Action Node 3 enqueued packet to node 4(node3_+_node4) may deadlock, because it occurs the last time at event 190 and is not seen for the remaining 81.00 percent of the trace.
• Type 16: Action Node 3 dequeued packet to node 2(node3_-_node2) may deadlock, because it occurs the last time at event 188 and is not seen for the remaining 81.20 percent of the trace.
• Type 16: Action Node 3 dequeued packet to node 4(node3_-_node4) may deadlock, because it occurs the last time at event 191 and is not seen for the remaining 80.90 percent of the trace.
• Type 16: Action Packet hopping from node 3 to node 2(node3_h_2L3) may deadlock, because it occurs the last time at event 189 and is not seen for the remaining 81.10 percent of the trace.
• Type 16: Action Packet hopping from node 3 to node 4(node3_h_3L4) may deadlock, because it occurs the last time at event 192 and is not seen for the remaining 80.80 percent of the trace.
• Type 16: Action Node 3 receiving packet from node 4(node3_r_3L4) may deadlock, because it occurs the last time at event 239 and is not seen for the remaining 76.10 percent of the trace.
• Type 16: Action Node 4 enqueued packet to node 3(node4_+_node3) may deadlock, because it occurs the last time at event 233 and is not seen for the remaining 76.70 percent of the trace.
• Type 16: Action Node 4 enqueued packet to node 5(node4_+_node5) may deadlock, because it occurs the last time at event 236 and is not seen for the remaining 76.40 percent of the trace.
• Type 16: Action Node 4 dequeued packet to node 3(node4_-_node3) may deadlock, because it occurs the last time at event 234 and is not seen for the remaining 76.60 percent of the trace.
• Type 16: Action Node 4 dequeued packet to node 5(node4_-_node5) may deadlock, because it occurs the last time at event 237 and is not seen for the remaining 76.30 percent of the trace.
• Type 16: Action Packet hopping from node 4 to node 3(node4_h_3L4) may deadlock, because it occurs the last time at event 235 and is not seen for the remaining 76.50 percent of the trace.
• Type 16: Action Packet hopping from node 4 to node 5(node4_h_4L5) may deadlock, because it occurs the last time at event 238 and is not seen for the remaining 76.20 percent of the trace.
• Type 16: Action Node 4 receiving packet from node 3(node4_r_3L4) may deadlock, because it occurs the last time at event 220 and is not seen for the remaining 78.00 percent of the trace.
• Type 16: Action Node 4 receiving packet from node 5(node4_r_4L5) may deadlock, because it occurs the last time at event 255 and is not seen for the remaining 74.50 percent of the trace.
• Type 16: Action Node 5 enqueued packet to node 4(node5_+_node4) may deadlock, because it occurs the last time at event 249 and is not seen for the remaining 75.10 percent of the trace.
• Type 16: Action Node 5 enqueued packet to node 6(node5_+_node6) may deadlock, because it occurs the last time at event 252 and is not seen for the remaining 74.80 percent of the trace.
• Type 16: Action Node 5 dequeued packet to node 4(node5_-_node4) may deadlock, because it occurs the last time at event 250 and is not seen for the remaining 75.00 percent of the trace.
• Type 16: Action Node 5 dequeued packet to node 6(node5_-_node6) may deadlock, because it occurs the last time at event 253 and is not seen for the remaining 74.70 percent of the trace.
• Type 16: Action Packet hopping from node 5 to node 4(node5_h_4L5) may deadlock, because it occurs the last time at event 251 and is not seen for the remaining 74.90 percent of the trace.
• Type 16: Action Packet hopping from node 5 to node 6(node5_h_5L6) may deadlock, because it occurs the last time at event 254 and is not seen for the remaining 74.60 percent of the trace.
• Type 16: Action Node 5 receiving packet from node 4(node5_r_4L5) may deadlock, because it occurs the last time at event 240 and is not seen for the remaining 76.00 percent of the trace.
• Type 16: Action Node 5 receiving packet from node 6(node5_r_5L6) may deadlock, because it occurs the last time at event 232 and is not seen for the remaining 76.80 percent of the trace.
• Type 16: Action Node 6 enqueued packet to node 0(node6_+_node0) may deadlock, because it occurs the last time at event 225 and is not seen for the remaining 77.50 percent of the trace.
• Type 16: Action Node 6 enqueued packet to node 5(node6_+_node5) may deadlock, because it occurs the last time at event 228 and is not seen for the remaining 77.20 percent of the trace.
• Type 16: Action Node 6 dequeued packet to node 0(node6_-_node0) may deadlock, because it occurs the last time at event 226 and is not seen for the remaining 77.40 percent of the trace.
• Type 16: Action Node 6 dequeued packet to node 5(node6_-_node5) may deadlock, because it occurs the last time at event 229 and is not seen for the remaining 77.10 percent of the trace.
• Type 16: Action Packet hopping from node 6 to node 5(node6_h_5L6) may deadlock, because it occurs the last time at event 230 and is not seen for the remaining 77.00 percent of the trace.
• Type 16: Action Packet hopping from node 6 to node 0(node6_h_6L0) may deadlock, because it occurs the last time at event 227 and is not seen for the remaining 77.30 percent of the trace.
• Type 16: Action Node 6 receiving packet from node 5(node6_r_5L6) may deadlock, because it occurs the last time at event 256 and is not seen for the remaining 74.40 percent of the trace.
• Type 16: Action Node 6 receiving packet from node 0(node6_r_6L0) may deadlock, because it occurs the last time at event 218 and is not seen for the remaining 78.20 percent of the trace.