Yes. tripId is currently not interacting with repeated laps or flow
vehicles.
It was implemented for the use case of importing a complete schedule in
"uncompressed form" from an external data source (gtfs etc)
In this use case no flows or route-repeat definitions are used.
Instead each vehicle is
@Jakob,
*Rerouting:* Yes, I am interested in having two routes for a single public
transit line. Any vehicle assigned to this line will swap between the
routes once it reaches the end point at one direction or a depot. I will
make an attempt soo, will inform about the progress, and troubles if
Rerouting currently does not work with stops that follow a fixed schedule
(attribute 'until').
However, the use case with depot + cycle1 + cycle2 + ... + cyclen + depot
was already discussed and is demonstrated in
Re-routing should not be needed for public transport simulation. The line
attribute is used when matching passengers with rides.
Note, that only the initial line value is currently used for public
transport routing.
The tripId attribute is only there for informational purposes. It can be
used to
Hello,
I think there must be a simpler way of re-routing using the attribute *line*
of tag. As per definition, we can set a new line attribute on the
vehicles at this particular stop, it will be triggered automatically.
Also, I observe that there is a *tripId* attribute for tag. Can it
be used
The problem is with the rerouter that reassigns a new non-repeating route
and thereby loses all the repeated stops. If you remove the rerouter, the
vehicle will stop in each lap.
Am Di., 16. Juni 2020 um 10:27 Uhr schrieb Chris Weinhaupl <
chrisweinha...@gmail.com>:
>
> Thanks for the 'repeat'
Hello Jakob,
"A defines a place and direction for stopping, (because it is on
a specific lane and lanes are directional)".
Yes, I missed the direction aspect of a bus stop. In my example, my up and
down stops are the same, so I devised the route with a relevant set of
edges for having a cyclic
The error is correct because each of the stops must fit into a single loop
of the route.
I think there is a misunderstanding on your part abut the nature of busStop
definitions in SUMO:
A defines a place and direction for stopping, (because it is on a
specific lane and lanes are directional).
Possibly your simulation is running afoul of
https://github.com/eclipse/sumo/issues/7036 (which I hope I mentioned
already).
A route with edges "22 59 53cd 53[0] 53[1][0] 53[1][1][0] 77[1][0] 77ab
77bc 21a 21b 103 14 9 211 45 44 38 15 24" should work with the latest
development version (not
Hello Jakob,
Thank you for your example, I tried to imitate it and it worked.
Actually, my intuition was right, but I struggled in understanding the
network properties. For instance, a connection from an edge to the same
edge is not trivial, look at the below example. Just notice the bold edges
@Dillip Rout: Please take a look at
https://github.com/eclipse/sumo/tree/master/tests/sumo/basic/routes/parsing/repeat_flow_busstop
@Chris Weinhaupl: You need to add the 'repeat' attribute in your route
definition to define additional laps
Am Mo., 15. Juni 2020 um 08:30 Uhr schrieb Tripplanner
Hello Jakob,
I tried something similar to your example:
It is observed that vehicles assigned to such a line (public transit route)
are indeed taking multiple trips as per the definition and the relative
time values are maintained. Each of these assigned vehicles
This creates 4 vehicles that will lap the route.
The bus will stop at the first stop, however on the second lap the vehicle
will not stop at the busStop.
Thanks for the assistance, what may I change make the same vehicle repeat
and stop at the first stop on the second/third/forth lap etc?
These are two different periods:
- the period in the flow defines the time between individual vehicles
- the period in the route defines the (expected) time to complete one loop
of the route
Both times are independent of each other. If you want multiple vehicles on
the same route the flow-period
Hello Jajob,
As I believe, the following line of code is responsible for dispatching or
starting vehicles. For example, the first vehicle starts at 1 sec and the
second starts at 201. There could be at most two vehicles since the flow
ends at 211 sec.
If my above assumption is correct, then what
The following example (from
https://github.com/eclipse/sumo/tree/master/tests/sumo/basic/routes/parsing/repeat_flow_stops
) defines
2 buses that run a looped route 3 times each (initial run and 2 repeats).
The 'until' times are relative to the flow vehicle departures (at time 0
and 200) and the
Hello,
As per the documentation (
https://sumo.dlr.de/docs/Definition_of_Vehicles,_Vehicle_Types,_and_Routes.html#repeated_routes),
repeat is similar to frequency, am I correct?.
Or, the frequency is similar to vehsPerHour defined in flow (
Hello,
I have the same issue, that is, tried to simulate bus service. For a line
(or public transit route), several vehicles (fleet) repeatedly make many
trips according to headway (period in SUMO) or frequency. As per the
suggestions @Jackob, I tried the following.
Thanks @namdre
I would like 70 buses to repeat a 40km loop stopping at defined
busstops along the way.
I tried re-router but I cant make the bus stop the second time around.
I tried to figure out a config that matches your suggestion.(just below).
May I ask for a sample config of a repeating
19 matches
Mail list logo
