The cascading types are expected when you call functions that change vType
attributes on a singe vehicle (i.e. traci.vehicle.setLength). In order to
change the property only for a single vehicle, the type is cloned every
time.
However, the reported information is insufficient to understand the
prob
Here is what happens:
- your network has disconnected components
- when you generate intermediate locations, there is a high probability
that some of them are in different components of the network
- walks between disconnected are invalid and rejected when generating the
route file
Here is the sol
The bearing mainly depends on the route of the pedestrian but also on
evasive maneuvers during the interaction with cars and other pedestrians.
The bearing reflects a distribution only in the sense that there is some
distribution in the origin and destination patterns of the person
definitions.
If
Hi Jakob,
Thanks for the prompt reply.
What I see in the vType in the saved file for both types is:
I tried to play around also with the minGap (only difference I see between
these two vTypes) and that is indeed influencing the headway - only for the
rl type:
1) If minGap = 0: I get the h
Thanks Jakob.
But is there a distribution by how the absolute bearing is attributed for a
person or it's just randomly?
And extending the question it could be helpful to know:
- There is a distribution for walks too?
- If it is true, is it possible to change it?
Regards,
Em qui., 23 de mar. d
