add an new input element which forces vehicles to drive across a specified lane with a specified speed (trac #1020)
This works similar to a stop but with speeds > 0 The speed should be kept while the vehicle is between startPos and endPos.
Among other things this gives fine grained control over vehicle trajectories without using TraCI.
Migrated from http://sumo.dlr.de/ticket/1020
{
"status": "new",
"changetime": "2014-05-26T08:01:08Z",
"description": "This works similar to a stop but with speeds > 0\nThe speed should be kept while the vehicle is between startPos and endPos.\n\nAmong other things this gives fine grained control over vehicle trajectories without using TraCI.",
"reporter": "namdre",
"cc": "",
"resolution": "",
"_ts": "1401091268508388",
"component": "simulation data input",
"summary": "add an new input element which forces vehicles to drive across a specified lane with a specified speed",
"priority": "major",
"keywords": "",
"time": "2013-09-05T10:33:46Z",
"milestone": "1.1.0",
"owner": "",
"type": "enhancement"
}
@namdre commented:
would it be better to invent a new element which has no duration/until attribute and only ''speed'' but resolves to the same data structures internally?
- @namdre changed description from:
The speed for a stop should default to 0 but it should also be possible to set arbitry speeds including the symbalic value "max".
When giving speeds other than 0, the duration of the stop is ignored (should become optional) but the speed should be kept while the vehicle is between startPos and endPos.
Among other things this gives fine grained control over vehicle trajectories without using TraCI.
to:
This works similar to a stop but with speeds > 0 The speed should be kept while the vehicle is between startPos and endPos.
Among other things this gives fine grained control over vehicle trajectories without using TraCI.
- @namdre changed summary from "add an optional ''speed'' attribute to stop elements" to "add an new input element which forces vehicles to drive across a specified lane with a specified speed"
@namdre commented:
suggested name:
<waypoint>
@behrisch changed milestone from "0.21.0" to "1.1.0"
I think it makes sense to use SUMOVehicleParameter::Stop and all the other stop infrastructure to implement this.
also some kind of special value like speed="max" or speed="current" would be nice
setting speed="1000" has this effect. I agree that a special input value would look nicer.