My favorites | Sign in
Project Home Downloads Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 10: [FIXED] Distance is broken: Algorithms are affected
1 person starred this issue and may be notified of changes. Back to list
 
Project Member Reported by r.h.gr...@googlemail.com, Jan 7, 2012
just load any graph and try the skyline algorithm with any combination of attributes (at least two). the results are always identical but the found links aren't the same.
Therefore something seems to be broken inside the skyline algorithm

Jan 7, 2012
Project Member #1 r.h.gr...@googlemail.com
edit:
It seems that the algorithm isn't the broken part. (Dijkstra is also somekind of un-functional. It detects only one route everytime and it is the same for SHORTEST and FASTEST).

Summary: Something is broken: Algorithms are affected
Jan 7, 2012
Project Member #2 r.h.gr...@googlemail.com
After validation, bug seems not to be a bug. Looks like some rare circumstances if all found links are exactly of the same distance and need the same time to travel (e.g. all use the motorway and primaries and the differ only in one or two primary_links)
Summary: [FIXED:Not really a bug] Something is broken: Algorithms are affected
Jan 7, 2012
Project Member #3 r.h.gr...@googlemail.com
The algorithmic calculation of the link length are mixed up. This is based on the new distance calculation (now in meters).
Has to be checked and verified!
Summary: [PARTIALLY FIXED:Not really a bug] Something is broken: Algorithms are affected
Labels: -Priority-High Priority-Critical
Jan 7, 2012
Project Member #4 r.h.gr...@googlemail.com
It is clearly something wrong with the new distance function.
Dijkstra puts out massive warnings like:

Information: start algorithm
Jan 08, 2012 12:30:06 AM de.lmu.ifi.dbs.trafficmining.algorithms.OSMDijkstra linkCost
Warnung: invalid time!: 0m, 50km/h => 0h
Jan 08, 2012 12:30:06 AM de.lmu.ifi.dbs.trafficmining.algorithms.OSMDijkstra linkCost
Warnung: invalid time!: 0m, 50km/h => 0h
Jan 08, 2012 12:30:06 AM de.lmu.ifi.dbs.trafficmining.algorithms.OSMDijkstra linkCost
Warnung: invalid time!: 0m, 50km/h => 0h
Jan 08, 2012 12:30:06 AM de.lmu.ifi.dbs.trafficmining.algorithms.OSMDijkstra linkCost
Warnung: invalid time!: 0m, 50km/h => 0h
Jan 08, 2012 12:30:06 AM de.lmu.ifi.dbs.trafficmining.algorithms.OSMDijkstra linkCost
Warnung: invalid time!: 0m, 50km/h => 0h
Summary: Distance is broken: Algorithms are affected
Jan 8, 2012
Project Member #5 r.h.gr...@googlemail.com
fixed at r707b9280606e 
Summary: [FIXED] Distance is broken: Algorithms are affected
Mar 16, 2012
Project Member #6 franz.graf
is this now fixed or not?
Mar 30, 2012
Project Member #7 franz.graf
(No comment was entered for this change.)
Status: Fixed

Powered by Google Project Hosting