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

allow configuring behavior at junctions (trac #3148) #3148

Closed
behrisch opened this issue May 27, 2017 · 19 comments

Comments

@behrisch
Copy link
Contributor

commented May 27, 2017

A number of junction related behaviors shall be made configurable.

  • distance at which crossing pedestrians are considered an obstacle (jmCrossingGap)
  • red light violation depending on red-light-duration-so-far (jmDriveAfterRedTime)
  • maximum speed for red light violation (jmDriveRedSpeed)
  • probability to drive onto an intersection despite jamming potential (jmIgnoreKeepClear)
  • speed threshold below which junction foes with right of way may be ignored (jmIgnoreFoeSpeed)
  • probability to ignore foes with right of way and speed below the threshold (jmIgnoreFoes)

The new parameters should be accessible via TraCI using the getParameter/setParameter calls as is done for the laneChangeModel parameters.

It must be decided whether the parameters are stored at the vehicle level (like lc-parameters) or at the vType level (like cf-parameters). In the latter case, setting them for individual vehicles always implies generating a new singular type. As the first draft of the behavior to be modelled is stateless a vType approach may be sufficient (and would be simpler).

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

{
    "status": "closed", 
    "changetime": "2017-10-06T10:32:25Z", 
    "description": "A number of junction related behaviors shall be made configurable. \n* distance at which crossing pedestrians are considered an obstacle (jmCrossingGap)\n* red light violation depending on red-light-duration-so-far (jmDriveAfterRedTime)\n* maximum speed for red light violation (jmDriveRedSpeed)\n* probability to drive onto an intersection despite jamming potential (jmIgnoreKeepClear)\n* speed threshold below which junction foes with right of way may be ignored (jmIgnoreFoeSpeed)\n* probability to ignore foes with right of way and speed below the threshold (jmIgnoreFoes)\n\nThe new parameters should be accessible via TraCI using the getParameter/setParameter calls as is done for the laneChangeModel parameters.\n\nIt must be decided whether the parameters are stored at the vehicle level (like lc-parameters) or at the vType level (like cf-parameters). In the latter case, setting them for individual vehicles always implies generating a new singular type. As the first draft of the behavior to be modelled is stateless a vType approach may be sufficient (and would be simpler).", 
    "reporter": "namdre", 
    "cc": "", 
    "resolution": "fixed", 
    "_ts": "1507285945830017", 
    "component": "sharps", 
    "summary": "allow configuring behavior at junctions", 
    "priority": "major", 
    "keywords": "", 
    "time": "2017-05-27T22:21:28Z", 
    "milestone": "1.0.0", 
    "owner": "www-data", 
    "type": "enhancement"
}
@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented May 27, 2017

@namdre changed description from:

A number of junction related behaviors shall be made configurable.

  • distance at which crossing pedestrians are considered an obstacle (jmCrossingGap)
  • red light violation depending on red-light-duration-so-far (jmDriveAfterRedTime)
  • maximum speed for red light violation (jmDriveRedSpeed)
  • probability to drive onto an intersection despite jamming potential (jmIgnoreKeepClear)
  • speed threshold below which junction foes with right of way may be ignored (jmIgnoreFoeSpeed)
  • probability to ignore foes with right of way and speed below the threshold (jmIgnoreFoes)

to:

A number of junction related behaviors shall be made configurable.

  • distance at which crossing pedestrians are considered an obstacle (jmCrossingGap)
  • red light violation depending on red-light-duration-so-far (jmDriveAfterRedTime)
  • maximum speed for red light violation (jmDriveRedSpeed)
  • probability to drive onto an intersection despite jamming potential (jmIgnoreKeepClear)
  • speed threshold below which junction foes with right of way may be ignored (jmIgnoreFoeSpeed)
  • probability to ignore foes with right of way and speed below the threshold (jmIgnoreFoes)

The new parameters should be accessible via TraCI using the getParameter/setParameter calls as is done for the laneChangeModel parameters.

It must be decided whether the parameters are stored at the vehicle level (like lc-parameters) or at the vType level (like cf-parameters). In the latter case, setting them for individual vehicles always implies generating a new singular type. As the first draft of the behavior to be modelled is stateless a vType approach may be sufficient (and would be simper).

@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented May 27, 2017

@namdre changed description from:

A number of junction related behaviors shall be made configurable.

  • distance at which crossing pedestrians are considered an obstacle (jmCrossingGap)
  • red light violation depending on red-light-duration-so-far (jmDriveAfterRedTime)
  • maximum speed for red light violation (jmDriveRedSpeed)
  • probability to drive onto an intersection despite jamming potential (jmIgnoreKeepClear)
  • speed threshold below which junction foes with right of way may be ignored (jmIgnoreFoeSpeed)
  • probability to ignore foes with right of way and speed below the threshold (jmIgnoreFoes)

The new parameters should be accessible via TraCI using the getParameter/setParameter calls as is done for the laneChangeModel parameters.

It must be decided whether the parameters are stored at the vehicle level (like lc-parameters) or at the vType level (like cf-parameters). In the latter case, setting them for individual vehicles always implies generating a new singular type. As the first draft of the behavior to be modelled is stateless a vType approach may be sufficient (and would be simper).

to:

A number of junction related behaviors shall be made configurable.

  • distance at which crossing pedestrians are considered an obstacle (jmCrossingGap)
  • red light violation depending on red-light-duration-so-far (jmDriveAfterRedTime)
  • maximum speed for red light violation (jmDriveRedSpeed)
  • probability to drive onto an intersection despite jamming potential (jmIgnoreKeepClear)
  • speed threshold below which junction foes with right of way may be ignored (jmIgnoreFoeSpeed)
  • probability to ignore foes with right of way and speed below the threshold (jmIgnoreFoes)

The new parameters should be accessible via TraCI using the getParameter/setParameter calls as is done for the laneChangeModel parameters.

It must be decided whether the parameters are stored at the vehicle level (like lc-parameters) or at the vType level (like cf-parameters). In the latter case, setting them for individual vehicles always implies generating a new singular type. As the first draft of the behavior to be modelled is stateless a vType approach may be sufficient (and would be simpler).

@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented May 27, 2017

@namdre committed 3e3b592 (aka r24585):
introducing junction model paramters refs #3148

@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented May 27, 2017

@namdre committed d788ff1 (aka r24586):
added test refs #3148

@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented May 27, 2017

@namdre committed e0b8644 (aka r24587):
implemented junction model parameter 'jmIgnoreKeepClearTime' refs #3148

@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented May 27, 2017

@namdre committed 802f869 (aka r24588):
added tests refs #3148

@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented May 27, 2017

@namdre committed 40d2226 (aka r24589):
implemented junction model parameter 'jmDriveAfterRedTime' refs #3148

@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented May 27, 2017

@namdre committed 1e42f4d (aka r24591):
added test refs #3148

@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented May 27, 2017

@namdre committed a81f276 (aka r24592):
implemented junction model parameter 'jmDriveRedSpeed' refs #3148

@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented May 27, 2017

@namdre committed c27b7c4 (aka r24593):
added test refs #3148

@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented May 27, 2017

@namdre committed 0ea30b0 (aka r24594):
implemented junction model parameter 'jmCrossingGap' refs #3148

@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented May 27, 2017

@namdre committed f5798dd (aka r24618):
added test refs #3148

@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented May 27, 2017

@namdre committed 3c70858 (aka r24619):
added test refs #3148

@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented May 27, 2017

  • @namdre committed c62b24b (aka r24620):
    red violators now react to vehicles on the junction. refs #3148
  • @www-data committed 6169589(../commit/616958921975b47c7f2b185543710ae93b9b5a63) (aka r24621):
    added test refs #3148
@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented May 27, 2017

@namdre committed e90e92c (aka r24622):
implemented pedestrian jaywalking refs #3148

@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented May 27, 2017

@namdre commented:

when violating a red light, the major links of the underlying priority junction must check the entry links for all foe lanes (the list of foeLinks is empty).

@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented May 27, 2017

@namdre committed 2abb491 (aka r26357):
added tests refs #3148

@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented May 27, 2017

@behrisch

This comment has been minimized.

Copy link
Contributor Author

commented May 27, 2017

@namdre committed 78945d4 (aka r26359):
addendum to [26358] refs #3148

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

@behrisch behrisch closed this Oct 28, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.