You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This came up when I was reviewing the cod in QueueWithBuffer to re-implement parts of it in the distributed QSim. kintematicWaves works with backwards travelling holes and basically adds an inflow capacity on top of that logic. The backwards travelling holes are described in a publication, while the inflow capacity is not described.
As far as I have understood, the inflow capacity throttles vehicles accessing the link, even though the storage capacity of that link is not yet exhausted. This makes sense in my opinion because, when a vehicle enters a street segment, the link is blocked for a brief moment, before the next vehicle can enter.
The text was updated successfully, but these errors were encountered:
I have added some tests for this functionality in PR: #3533
Now, auditing would also mean to think about, whether the inflow capacity calculation makes sense at all. Since @kainagel stated, that he implemented that functionality, some time in the distant past, I would like to sit down with him and take a look.
This came up when I was reviewing the cod in
QueueWithBuffer
to re-implement parts of it in the distributed QSim.kintematicWaves
works with backwards travelling holes and basically adds an inflow capacity on top of that logic. The backwards travelling holes are described in a publication, while the inflow capacity is not described.The inflow capacity is calculated as
q = (#lanes / effectiveCellSize) / (1. / vHole + 1 / vFree)
As far as I have understood, the inflow capacity throttles vehicles accessing the link, even though the storage capacity of that link is not yet exhausted. This makes sense in my opinion because, when a vehicle enters a street segment, the link is blocked for a brief moment, before the next vehicle can enter.
The text was updated successfully, but these errors were encountered: