Re: [sumo-user] Appropriate values for jmTimegapMinor

[Jakob Erdmann <namdre.sumo@xxxxxxxxx>]

Yes and No.

- a) and c) are computed from context values. ( Please excuse the typo)

- d) does refer to the gap between the merging vehicle C and the second vehicle on the main flow B (Please exuse the typo)

- b) really does refer to the minimum time gap between the leading vehicle on the main flow (A) and the merging vehicle (C). This only ever plays a role if vehicle A is driving very slowly

The difference between the necessary gap for the first vehicle (Grenzzeitlücke) and the following vehicles to merge (Folgezeitlücke) is included into the computation of c) because the follower vehicle can pass the conflicht section with higher average speed.

The degree to which this makes a difference depends also on the 'visibilityDistance' attribute of the connection.

By default, vehicles will only have clear visibilty of foe traffic at a distance of 4.5m before the stop line which will make them slow down before that point. If you increase the value, you will see less slow down by merging follower vehicles and thus reduced 'Folgezeitlücke'.

regards,

Jakob

2018-07-02 10:08 GMT+02:00 florian preusse <flopreusse@xxxxxxxxxx>:

Hi Jakob,

thank you for your answer, but Im afraid, that I dont quite understand this attribute still. I might be wrong, but could it be, that the letters you used (A,B,C) are a bit mixed up? Did you mean it this way?

"Consider two vehicles A and B in the main flow with time gap T and a vehicle C that wants to merge/pass in between.

T consists of

- a) the time vehicle A take to travel its own length

- b) the time gap between the back of vehicle A and the front of vehicle B

- c) the time for vehicle C to pass the intersection or merge which depends on the geometry of the intersection and the speed, acceleration and length of vehicle C

- d) the time gap between the back of vehicle C and the front of vehicle B

The value of jmTimeGapMinor models b) and d).

The values of a) and c) are computed from context values such as junction geometry which has the effect that required gaps for turning left or passing across are larger than those for turning right."

So if I understand right, there is no difference in Sumo, if a vehicle I being first or second in line to merge into the main flow? The Attribute jmTimegapMinor would therefore be more comparable to Grenzzeitlücke than Folgezeitlücke (Sorry I cant find an appropriate Translation), right?

Thank you and Kind regards,

Florian

---

Von: sumo-user-bounces@xxxxxxxxxxx <sumo-user-bounces@xxxxxxxxxxx> im Auftrag von Jakob Erdmann <namdre.sumo@xxxxxxxxx>
Gesendet: Sonntag, 1. Juli 2018 20:41
An: Sumo project User discussions
Betreff: Re: [sumo-user] Appropriate values for jmTimegapMinor

 

Hello,

the values from the table refers to gross time gaps in the main flow that a vehicle would accept for merging.

Consider two vehicles A and B in the main flow with time gap T and a vehicle C that wants to merge/pass in between.

T consists of

- a) the time vehicle A take to travel its own length

- b) the time gap between the back of vehicle A and the front of vehicle C

- c) the time for vehicle C to pass the intersection or merge which depends on the geometry of the intersection and the speed, acceleration and length of vehicle C

- d) the time gap between the back of vehicle C and the front of vehicle A

The value of jmTimeGapMinor models b) and d).

The values of a) and b) are computed from context values such as junction geometry which has the effect that required gaps for turning left or passing across are larger than those for turning right.

I would assume that the default value of 1s is not too far off but I'm not aware of any calibration effort that went into that choice.

regards,

Jakob

2018-06-30 10:57 GMT+02:00 florian preusse <flopreusse@xxxxxxxxxx>:

Dear Sumo-Users,

I´m still working on the behaviour of the vehicles in my simulation and there is one attribute, that I would like to set, but I´m not quite sure which value would be appropriate. The attribute I´m refering to is the following:

jmTimegapMinor

float s

1

This value defines the minimum time gap when passing ahead of a prioritized vehicle.

In a german guidline it says, that there is many different values for time gaps that a car needs to perform a right turn, left trun or crossing movement ahead of a prioritized vehicle. It also says, that it´s relevent, if the vehicle is first in line (e.g. 6.7 s for a crossing movement of the first vehicle) or if it is just following the vehicle in front (e.g. only 3.3 s for a crossing movement). The table I´m refering to is shown underneath.

Now I would like to know, if there is anyone who has experiences in setting jmTimegapMinor, because as far as I understand, it is representing all of these different values in one attribute. Is that right? And if so, why is the default value set to 1 s?

My first thought would have been to choose a value in the middle so, something around 4.5 s for regular vehicles, because they are performing all of the different movements in my simulation. Another approach, that comes to my mind is choosing the highest value of the given table. But then it really reduces the capacity of my unsignalised nods. 

If anyone as a good idea, how to handle this attribute or knows about other attrbiutes to specify the movements more in detail, I would be very grateful!

Thanks a lot and kind regards,

Florian Preuße

_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/sumo-user

_______________________________________________
sumo-user mailing list
sumo-user@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/sumo-user