texttest -a complex -d /home/delphi/gcc/sumo/tests -reconnect /home/delphi/gcc/texttesttmp/gcc4_64.02May002455.20941 -g
texttest -a complex -d /home/delphi/gcc/sumo/tests
---------- Differences in png ---------- Binärdateien /home/delphi/gcc/sumo/tests/complex/traci/pythonApi/gui/png.complex und /home/delphi/gcc/texttesttmp/gcc4_64.27Apr002527.13107/complex/traci/pythonApi/gui/png.complex sind verschieden.
****************************************************** Ticket #1691 (new defect: ) edge shapes at junctions get lost on matsim reimport http://sumo.dlr.de/trac.wsgi/ticket/1691 Reported By: behrisch Owned by: Priority: major Milestone: 1.0.0 Component: net building (NETGEN, NETCONVERT) Version: Description: matsim always include the node into the edge shape and thus a reimport does not give the same result. The same issue exists for dlr-navteq #1687 ****************************************************** (This bug was triggered by text found in file 'net' matching '.*') ---------- Differences in net ---------- 4c4 < <net version="0.13" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://sumo.dlr.de/xsd/net_file.xsd"> --- > <net version="0.27" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://sumo.dlr.de/xsd/net_file.xsd"> 6c6 < <location netOffset="-399345.66,-5809365.64" convBoundary="-1.31,0.00,1737.68,767.39" origBoundary="13.519602,52.425528,13.545248,52.434465" projParameter="+proj=utm +zone=33 +ellps=WGS84 +datum=WGS84 +units=m +no_defs"/> --- > <location netOffset="-399345.66,-5809362.43" convBoundary="0.00,0.00,1737.68,770.60" origBoundary="1351960.240000,5242549.880000,1354524.800000,5243232.070000" projParameter="+proj=utm +zone=33 +ellps=WGS84 +datum=WGS84 +units=m +no_defs"/> 9c9 < <lane id=":175648134_0_0" index="0" allow="bicycle" speed="5.56" length="4.82" shape="15.90,169.70 14.56,169.04 14.04,168.28 14.35,167.40 15.46,166.42"/> --- > <lane id=":175648134_0_0" index="0" allow="bicycle" speed="5.56" length="4.67" shape="15.89,172.86 14.59,172.22 14.09,171.48 14.38,170.63 15.47,169.68"/> 12,13c12,13 < <lane id=":261599791_0_0" index="0" speed="27.78" length="0.10" shape="34.60,181.48 34.67,181.47"/> < <lane id=":261599791_0_1" index="1" speed="27.78" length="0.10" shape="34.18,178.21 34.20,178.20"/> --- > <lane id=":261599791_0_0" index="0" speed="27.78" length="0.27" shape="34.70,184.52 34.45,184.56"/> > <lane id=":261599791_0_1" index="1" speed="27.78" length="0.27" shape="34.29,181.35 34.00,181.39"/> 16c16 < <lane id=":261599791_2_0" index="0" speed="27.78" length="2.41" shape="34.18,178.21 32.85,177.55 32.33,176.78"/> --- > <lane id=":261599791_2_0" index="0" speed="27.78" length="2.34" shape="34.29,181.35 33.00,180.71 32.50,179.96"/> 19c19 < <lane id=":261599791_6_0" index="0" speed="27.78" length="2.41" shape="32.33,176.78 32.64,175.91 33.76,174.93"/> --- > <lane id=":261599791_6_0" index="0" speed="27.78" length="2.34" shape="32.50,179.96 32.80,179.12 33.88,178.17"/> 22,23c22,23 < <lane id=":261599791_3_0" index="0" speed="27.78" length="0.10" shape="33.34,171.66 33.34,171.66"/> < <lane id=":261599791_3_1" index="1" speed="27.78" length="0.10" shape="33.75,174.93 33.76,174.93"/> --- <truncated after showing first 30 lines>
****************************************************** Ticket #1691 (new defect: ) edge shapes at junctions get lost on matsim reimport http://sumo.dlr.de/trac.wsgi/ticket/1691 Reported By: behrisch Owned by: Priority: major Milestone: 1.0.0 Component: net building (NETGEN, NETCONVERT) Version: Description: matsim always include the node into the edge shape and thus a reimport does not give the same result. The same issue exists for dlr-navteq #1687 ****************************************************** (This bug was triggered by text found in file 'net' matching '.*') ---------- Differences in net ---------- 4c4 < <net version="0.13" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://sumo.dlr.de/xsd/net_file.xsd"> --- > <net version="0.27" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://sumo.dlr.de/xsd/net_file.xsd"> 6c6 < <location netOffset="-399345.66,-5809365.64" convBoundary="-1.31,0.00,1737.68,767.39" origBoundary="13.519602,52.425528,13.545248,52.434465" projParameter="+proj=utm +zone=33 +ellps=WGS84 +datum=WGS84 +units=m +no_defs"/> --- > <location netOffset="0.00,-19.68" convBoundary="0.00,0.00,1737.68,747.71" origBoundary="0.00,19.68,1737.68,767.39" projParameter="!"/> 9c9 < <lane id=":175648134_0_0" index="0" allow="bicycle" speed="5.56" length="4.82" shape="15.90,169.70 14.56,169.04 14.04,168.28 14.35,167.40 15.46,166.42"/> --- > <lane id=":175648134_0_0" index="0" speed="5.56" length="4.67" shape="15.89,149.97 14.59,149.33 14.09,148.59 14.39,147.74 15.47,146.79"/> 12,13c12,13 < <lane id=":261599791_0_0" index="0" speed="27.78" length="0.10" shape="34.60,181.48 34.67,181.47"/> < <lane id=":261599791_0_1" index="1" speed="27.78" length="0.10" shape="34.18,178.21 34.20,178.20"/> --- > <lane id=":261599791_0_0" index="0" speed="27.78" length="0.23" shape="34.71,161.64 34.51,161.66"/> > <lane id=":261599791_0_1" index="1" speed="27.78" length="0.23" shape="34.31,158.46 34.06,158.49"/> 16c16 < <lane id=":261599791_2_0" index="0" speed="27.78" length="2.41" shape="34.18,178.21 32.85,177.55 32.33,176.78"/> --- > <lane id=":261599791_2_0" index="0" speed="27.78" length="2.34" shape="34.31,158.46 33.02,157.81 32.52,157.07"/> 19c19 < <lane id=":261599791_6_0" index="0" speed="27.78" length="2.41" shape="32.33,176.78 32.64,175.91 33.76,174.93"/> --- > <lane id=":261599791_6_0" index="0" speed="27.78" length="2.34" shape="32.52,157.07 32.82,156.23 33.91,155.28"/> 22,23c22,23 < <lane id=":261599791_3_0" index="0" speed="27.78" length="0.10" shape="33.34,171.66 33.34,171.66"/> < <lane id=":261599791_3_1" index="1" speed="27.78" length="0.10" shape="33.75,174.93 33.76,174.93"/> --- <truncated after showing first 30 lines>
different outputs from detectors which should detect the same
(This bug was triggered by text found in file 'output' matching 'failed')
---------- Differences in output ----------
10c10
< success 0.1 ['--step-length', '.1', '--end', '100'] ['3/1to2/1_0']
---
> failed 0.1 ['--step-length', '.1', '--end', '100'] 3/1to2/1_0 (71.3, 71.4) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
12c12
< success 1 ['--step-length', '.1', '--end', '100'] ['3/1to2/1_0']
---
> failed 1 ['--step-length', '.1', '--end', '100'] 3/1to2/1_0 (72.0, 73.0) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
14c14
< success 10 ['--step-length', '.1', '--end', '100'] ['3/1to2/1_0']
---
> failed 10 ['--step-length', '.1', '--end', '100'] 3/1to2/1_0 (80.0, 90.0) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
18c18
< success 0.1 ['--step-length', '.1', '--end', '1000'] ['3/1to2/1_0']
---
> failed 0.1 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (71.3, 71.4) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
20c20
< success 1 ['--step-length', '.1', '--end', '1000'] ['3/1to2/1_0']
---
> failed 1 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (72.0, 73.0) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
22c22
< success 10 ['--step-length', '.1', '--end', '1000'] ['3/1to2/1_0']
---
> failed 10 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (80.0, 90.0) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
24c24
< success 100 ['--step-length', '.1', '--end', '1000'] ['3/1to2/1_0']
---
> failed 100 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (100.0, 200.0) [('e1', -1.0), ('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
34c34
< success 0.1 ['--step-length', '1', '--end', '100'] ['3/1to2/1_0']
<truncated after showing first 30 lines>
different outputs from detectors which should detect the same (This bug was triggered by text found in file 'output' matching 'failed') ---------- Differences in output ---------- 2c2 < success ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0'] --- > success 0.1 ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0'] 4c4 < success ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0', '1/1to0/1_0'] --- > success 0.1 ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0', '1/1to0/1_0'] 6c6 < success ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0'] --- > success 1 ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0'] 8c8 < success ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0', '1/1to0/1_0'] --- > success 1 ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0', '1/1to0/1_0'] 10c10 < success ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0'] --- > success 10 ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0'] 12c12 < success ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0', '1/1to0/1_0'] --- > success 10 ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0', '1/1to0/1_0'] 14c14 < success ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0'] --- > success 100 ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0'] 16c16 < success ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0', '1/1to0/1_0'] <truncated after showing first 30 lines>
different outputs from detectors which should detect the same
(This bug was triggered by text found in file 'output' matching 'failed')
---------- Differences in output ----------
34c34
< success 0.1 ['--step-length', '.1', '--end', '1000'] 2/1to1/1_0 (230.0, 230.1) [('e2', 9.99), ('e3', 10.0), ('edge', 9.99), ('lane', 9.99)]
---
> failed 0.1 ['--step-length', '.1', '--end', '1000'] 2/1to1/1_0 (148.1, 148.2) [('e2', 9.99), ('e3', 10.0), ('edge', 10.0), ('lane', 10.0)]
36c36
< success 0.1 ['--step-length', '.1', '--end', '1000'] 1/1to0/1_0 (148.1, 148.2) [('e2', 9.99), ('e3', 10.0), ('edge', 9.99), ('lane', 9.99)]
---
> failed 0.1 ['--step-length', '.1', '--end', '1000'] 2/1to1/1_0 (148.1, 148.2) [('e2', 9.99), ('e3', 10.0), ('edge', 10.0), ('lane', 10.0)]
38c38
< success 1 ['--step-length', '.1', '--end', '1000'] 2/1to1/1_0 (230.0, 231.0) [('e2', 9.99), ('e3', 10.0), ('edge', 9.99), ('lane', 9.99)]
---
> failed 1 ['--step-length', '.1', '--end', '1000'] 2/1to1/1_0 (148.0, 149.0) [('e2', 9.96), ('e3', 10.0), ('edge', 10.0), ('lane', 10.0)]
40c40
< success 1 ['--step-length', '.1', '--end', '1000'] 1/1to0/1_0 (148.0, 149.0) [('e2', 9.91), ('e3', 10.0), ('edge', 9.91), ('lane', 9.91)]
---
> failed 1 ['--step-length', '.1', '--end', '1000'] 2/1to1/1_0 (148.0, 149.0) [('e2', 9.96), ('e3', 10.0), ('edge', 10.0), ('lane', 10.0)]
42c42
< success 10 ['--step-length', '.1', '--end', '1000'] 2/1to1/1_0 (230.0, 240.0) [('e2', 9.42), ('e3', 9.9), ('edge', 9.42), ('lane', 9.42)]
---
> failed 10 ['--step-length', '.1', '--end', '1000'] 2/1to1/1_0 (140.0, 150.0) [('e2', 9.98), ('e3', 10.0), ('edge', 10.0), ('lane', 10.0)]
44c44
< success 10 ['--step-length', '.1', '--end', '1000'] 1/1to0/1_0 (140.0, 150.0) [('e2', 9.96), ('e3', 9.99), ('edge', 9.96), ('lane', 9.96)]
---
> failed 10 ['--step-length', '.1', '--end', '1000'] 2/1to1/1_0 (140.0, 150.0) [('e2', 9.98), ('e3', 10.0), ('edge', 10.0), ('lane', 10.0)]
46c46
< success 100 ['--step-length', '.1', '--end', '1000'] 2/1to1/1_0 (200.0, 300.0) [('e1', 10.0), ('e2', 9.22), ('e3', 5.71), ('edge', 9.22), ('lane', 9.22)]
---
> failed 100 ['--step-length', '.1', '--end', '1000'] 2/1to1/1_0 (100.0, 200.0) [('e1', 10.0), ('e2', 7.95), ('e3', 10.0), ('edge', 10.0), ('lane', 10.0)]
48c48
< success 100 ['--step-length', '.1', '--end', '1000'] 1/1to0/1_0 (100.0, 200.0) [('e1', 9.53), ('e2', 5.82), ('e3', 6.93), ('edge', 5.82), ('lane', 5.82)]
<truncated after showing first 30 lines>
different outputs from detectors which should detect the same
(This bug was triggered by text found in file 'output' matching 'failed')
---------- Differences in output ----------
10c10
< success 0.1 ['--step-length', '.1', '--end', '100'] ['3/1to2/1_0']
---
> failed 0.1 ['--step-length', '.1', '--end', '100'] 3/1to2/1_0 (75.4, 75.5) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
12c12
< success 1 ['--step-length', '.1', '--end', '100'] ['3/1to2/1_0']
---
> failed 1 ['--step-length', '.1', '--end', '100'] 3/1to2/1_0 (76.0, 77.0) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
14c14
< success 10 ['--step-length', '.1', '--end', '100'] ['3/1to2/1_0']
---
> failed 10 ['--step-length', '.1', '--end', '100'] 3/1to2/1_0 (80.0, 90.0) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
18c18
< success 0.1 ['--step-length', '.1', '--end', '1000'] ['3/1to2/1_0']
---
> failed 0.1 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (75.4, 75.5) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
20c20
< success 1 ['--step-length', '.1', '--end', '1000'] ['3/1to2/1_0']
---
> failed 1 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (76.0, 77.0) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
22c22
< success 10 ['--step-length', '.1', '--end', '1000'] ['3/1to2/1_0']
---
> failed 10 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (80.0, 90.0) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
24c24
< success 100 ['--step-length', '.1', '--end', '1000'] ['3/1to2/1_0']
---
> failed 100 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (100.0, 200.0) [('e1', -1.0), ('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
34c34
< success 0.1 ['--step-length', '1', '--end', '100'] ['3/1to2/1_0']
<truncated after showing first 30 lines>
different outputs from detectors which should detect the same
(This bug was triggered by text found in file 'output' matching 'failed')
---------- Differences in output ----------
10c10
< success 0.1 ['--step-length', '.1', '--end', '100'] ['3/1to2/1_0']
---
> failed 0.1 ['--step-length', '.1', '--end', '100'] 3/1to2/1_0 (76.4, 76.5) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
12c12
< success 1 ['--step-length', '.1', '--end', '100'] ['3/1to2/1_0']
---
> failed 1 ['--step-length', '.1', '--end', '100'] 3/1to2/1_0 (77.0, 78.0) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
14c14
< success 10 ['--step-length', '.1', '--end', '100'] ['3/1to2/1_0']
---
> failed 10 ['--step-length', '.1', '--end', '100'] 3/1to2/1_0 (80.0, 90.0) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
18c18
< success 0.1 ['--step-length', '.1', '--end', '1000'] ['3/1to2/1_0']
---
> failed 0.1 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (76.4, 76.5) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
20c20
< success 1 ['--step-length', '.1', '--end', '1000'] ['3/1to2/1_0']
---
> failed 1 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (77.0, 78.0) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
22c22
< success 10 ['--step-length', '.1', '--end', '1000'] ['3/1to2/1_0']
---
> failed 10 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (80.0, 90.0) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
24c24
< success 100 ['--step-length', '.1', '--end', '1000'] ['3/1to2/1_0']
---
> failed 100 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (100.0, 200.0) [('e1', -1.0), ('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
34c34
< success 0.1 ['--step-length', '1', '--end', '100'] ['3/1to2/1_0']
<truncated after showing first 30 lines>
different outputs from detectors which should detect the same
(This bug was triggered by text found in file 'output' matching 'failed')
---------- Differences in output ----------
0a1,48
> Loading configuration... done.
> failed 0.1 ['--step-length', '.1', '--end', '51'] 3/1to2/1_0 (38.4, 38.5) [('e2', 9.6), ('e3', 9.5), ('edge', 9.6), ('lane', 9.6)]
> Loading configuration... done.
> failed 1 ['--step-length', '.1', '--end', '51'] 3/1to2/1_0 (38.0, 39.0) [('e2', 9.64), ('e3', 9.5), ('edge', 9.64), ('lane', 9.64)]
> Loading configuration... done.
> failed 10 ['--step-length', '.1', '--end', '51'] 3/1to2/1_0 (30.0, 40.0) [('e2', 9.86), ('e3', 9.5), ('edge', 9.86), ('lane', 9.86)]
> Loading configuration... done.
> failed 100 ['--step-length', '.1', '--end', '51'] 3/1to2/1_0 (0.0, 51.0) [('e2', 9.62), ('e3', 9.5), ('edge', 9.62), ('lane', 9.62)]
> Loading configuration... done.
> failed 0.1 ['--step-length', '.1', '--end', '100'] 3/1to2/1_0 (38.4, 38.5) [('e2', 9.6), ('e3', 9.5), ('edge', 9.6), ('lane', 9.6)]
> Loading configuration... done.
> failed 1 ['--step-length', '.1', '--end', '100'] 3/1to2/1_0 (38.0, 39.0) [('e2', 9.64), ('e3', 9.5), ('edge', 9.64), ('lane', 9.64)]
> Loading configuration... done.
> failed 10 ['--step-length', '.1', '--end', '100'] 3/1to2/1_0 (30.0, 40.0) [('e2', 9.86), ('e3', 9.5), ('edge', 9.86), ('lane', 9.86)]
> Loading configuration... done.
> failed 100 ['--step-length', '.1', '--end', '100'] 3/1to2/1_0 (0.0, 100.0) [('e1', 9.5), ('e2', 9.53), ('e3', 9.5), ('edge', 9.47), ('lane', 9.47)]
> Loading configuration... done.
> failed 0.1 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (38.4, 38.5) [('e2', 9.6), ('e3', 9.5), ('edge', 9.6), ('lane', 9.6)]
> Loading configuration... done.
> failed 1 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (38.0, 39.0) [('e2', 9.64), ('e3', 9.5), ('edge', 9.64), ('lane', 9.64)]
> Loading configuration... done.
> failed 10 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (30.0, 40.0) [('e2', 9.86), ('e3', 9.5), ('edge', 9.86), ('lane', 9.86)]
> Loading configuration... done.
> failed 100 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (0.0, 100.0) [('e1', 9.5), ('e2', 9.53), ('e3', 9.5), ('edge', 9.47), ('lane', 9.47)]
> Loading configuration... done.
> failed 0.1 ['--step-length', '1', '--end', '51'] 3/1to2/1_0 (39.0, 40.0) [('e2', 9.6), ('e3', 9.5), ('edge', 9.6), ('lane', 9.6)]
> Loading configuration... done.
> failed 1 ['--step-length', '1', '--end', '51'] 3/1to2/1_0 (39.0, 40.0) [('e2', 9.6), ('e3', 9.5), ('edge', 9.6), ('lane', 9.6)]
> Loading configuration... done.
<truncated after showing first 30 lines>
****************************************************** Ticket #3522 (new enhancement: ) Save CF parameters that were changed over traci. http://sumo.dlr.de/trac.wsgi/ticket/3522 Reported By: leo Owned by: Priority: major Milestone: 1.1.0 Component: simulation data output Version: Description: Currently these are not saved. ****************************************************** (This bug was triggered by text found in file 'output' matching '(0.0, '== 1.0')') ---------- Differences in output ---------- 20,26c20,26 < (0.0, '== 0.0') < (0.5, '== 0.0') < (3.5, '== 0.0') < (2.5, '== 0.0') < (3.5, '== 0.0') < (3.5, '== 0.0') < (1.0, '== 0.0') --- > (0.0, '== 1.0') > (0.5, '== 1.0') > (3.5, '== 2.0') > (2.5, '== 3.0') > (3.5, '== 6.0') > (3.5, '== 7.0') > (1.0, '== 1.3') 28,34c28,34 < (0.0, '== 0.0') < (0.5, '== 0.0') < (4.5, '== 0.0') < (2.5, '== 0.0') < (4.5, '== 0.0') < (4.5, '== 0.0') < (1.0, '== 0.0') --- > (0.0, '== 1.0') > (0.5, '== 1.0') > (4.5, '== 2.0') > (2.5, '== 3.0') > (4.5, '== 6.0') <truncated after showing first 30 lines>
****************************************************** Ticket #2465 (assigned defect: ) traci distance request is incorrect after rerouting http://sumo.dlr.de/trac.wsgi/ticket/2465 Reported By: behrisch Owned by: hilb_ro Priority: major Milestone: 1.0.0 Component: TraCI Version: Description: retrieving the already driven distance (0xa4 0x84) gives incorrect values (starting from the rerouting edge instead of the beginning) ****************************************************** (This bug was triggered by text found in file 'output' matching '162') ---------- Differences in output ---------- 7c7 < 1165.0 --- > 162.04
mapping failure (This bug was triggered by text found in file 'output' matching 'failed') ---------- Differences in output ---------- 0a1 > internal corner (inside, segment2) failed: x=198, x2=198.0, y=1.9, y2=1.9, lane=middle_0, lane2=middle_0, pos=102, pos2=98.0 posLat=2.0 posLat2=1.9