faq 89260036

agent's pt plan: No route was found

by Rolando Armas on 2016-10-19 10:07:08

---

Hi Matsim friends:

This question is related with topics.

So, I have changed the leg modes to pt to aproximately 80% of agents, but when I run the simulation, I get the next warning messages:

  INFO Counter:51 [PersonPrepareForSim] handled person # 1
   WARN MultiNodeDijkstra:165 No route was found
   INFO Counter:51 [PersonPrepareForSim] handled person # 2
   WARN MultiNodeDijkstra:165 No route was found
   WARN MultiNodeDijkstra:165 No route was found
   INFO Counter:51 [PersonPrepareForSim] handled person # 4
   WARN MultiNodeDijkstra:165 No route was found
   WARN MultiNodeDijkstra:165 No route was found
   WARN MultiNodeDijkstra:165 No route was found
   WARN MultiNodeDijkstra:165 No route was found
   WARN MultiNodeDijkstra:165 No route was found
 ...

That means that some agents does not have a chance to go by public transportation to their destinations?

If is that so, what happened with those agents? 

I have checked the log file and I realize that 66% of the agents has a transit_walk leg.

INFO LegHistogramListener:80 number of legs:    8830    100%
 INFO LegHistogramListener:87 number of car legs:    1116    12.638731596828991%
 INFO LegHistogramListener:89 (car legs include legs by pt vehicles)
 INFO LegHistogramListener:87 number of pt legs:    1857    21.030577576443942%
 INFO LegHistogramListener:87 number of transit_walk legs:    5857    66.33069082672706%

Does it mean that they are going by walk ?

How can I do to improve the rate of agents that can take the bus services?

Thanks again!

---

Comments: 1

---

Re: agent's pt plan: No route was found

by Kai Nagel on 2016-11-03 14:32:13

Dear Rolando,

I am not a pt expert, but it looks like nobody of them is answering.

I am never sure if our statistics there refers to "legs" or to "trips" (composed of several legs), but having (too) many pure transit_walk trips seems to happen quite often.  In general, this happens when the pt router "thinks" that direct walk is better than pt. Possible reasons include:

• nearest pt stop too far away
• accessible pt stops not served by lines going into the right direction
• pt departing at the "wrong" time (i.e. traveller having to wait long time for pt)

If you think it is "wrong" time, maybe the "TimeAllocationMutator_ReRoute" strategy may help.

If you think it is "not enough pt stops nearby", then there are some options in "transitRouter" config. 

Hope this helps, please report.

Best

Kai