Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement per-vehicle randomization of edge weights (trac #1353) #1353

Closed
behrisch opened this issue Jun 26, 2014 · 6 comments

Comments

@behrisch
Copy link
Contributor

commented Jun 26, 2014

This will be useful for two reasons:

  • avoid biasing in grid-networks (of multiple routes with the same length, always the same one is returned otherwise)
  • get a better starting solution for duaIterate (not every vehicle is taking the exact same shortest path)
  • reduce oscillations when using one-shot routing

Migrated from http://sumo.dlr.de/ticket/1353

{
    "status": "reopened", 
    "changetime": "2015-03-06T11:44:17Z", 
    "description": "This will be useful for two reasons:\n- avoid biasing in grid-networks (of multiple routes with the same length, always the same one is returned otherwise)\n- get a better starting solution for duaIterate (not every vehicle is taking the exact same shortest path)\n- reduce oscillations when using one-shot routing", 
    "reporter": "namdre", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1425642257389036", 
    "component": "routing (DUAROUTER)", 
    "summary": "Implement per-vehicle randomization of edge weights", 
    "priority": "major", 
    "keywords": "", 
    "time": "2014-06-26T09:02:16Z", 
    "milestone": "1.1.0", 
    "owner": "namdre", 
    "type": "enhancement"
}
@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented Jun 26, 2014

@namdre commented:

does it really make a difference whether the random weight of each edge remains constant for each vehicle? If not, the implementation would be even simpler.

@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented Jun 26, 2014

@behrisch changed milestone from "0.22.0" to "1.1.0"

@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented Jun 26, 2014

@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented Jun 26, 2014

wrong ticket referenced in 838e069 (aka r17462)

  • @namdre changed resolution from "fixed" to ""
  • @namdre changed status from "closed" to "reopened"
@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented Jun 26, 2014

@namdre changed description from:

This will be useful for two reasons:

  • avoid biasing in grid-networks (of multiple routes with the same length, always the same one is returned otherwise)
  • get a better starting solution for duaIterate (not every vehicle is taking the exact same shortest path)

to:

This will be useful for two reasons:

  • avoid biasing in grid-networks (of multiple routes with the same length, always the same one is returned otherwise)
  • get a better starting solution for duaIterate (not every vehicle is taking the exact same shortest path)
  • reduce oscillations when using one-shot routing
@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented Jun 26, 2014

@namdre committed cff0b63 (aka r18036):
added option for randomizing routing weights. (only active when using rerouting device yet) refs #1353

@behrisch behrisch added this to the 1.1.0 milestone Oct 28, 2017

@behrisch behrisch modified the milestones: 1.1.0, 1.2.0 Dec 19, 2018

namdre added a commit that referenced this issue Apr 3, 2019
namdre added a commit that referenced this issue Apr 3, 2019

@namdre namdre closed this in 382bd8f Apr 3, 2019

namdre added a commit that referenced this issue Apr 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.