Open issues

Router cannot find any route at all - abort replanning for agent?
MATSIM-947
Matsim-Code-Examples version branches
MATSIM-940
NullPointerException in TravelTimeCollector
MATSIM-753
Make output folder relative?
MATSIM-652
eclipse looks at a different subset of test cases than the build server
MATSIM-174
Re: Attributes in Activities/Legs
MATSIM-978
How to deal with ConfigGroup.setLocked() when modifying config entries during a simulation run?
MATSIM-977
facility ids
MATSIM-975
how to somewhat certify matsim simulations
MATSIM-974
emissions contrib into core?
MATSIM-971
analysis output into events channel?
MATSIM-970
carrier vehicle types in carrier plans file or separate?
MATSIM-968
matsim: immutable types?
MATSIM-967
distance for nonNetworkWalk from coordinate to link
MATSIM-966
make route distances exclude first and last link
MATSIM-965
how to bind a class both as an events handler and as a controler listener
MATSIM-964
put getDriver back into link enter/leave events?
MATSIM-963
Nightly builds (#170)
MATSIM-948
drt access/egress to pt together with different drt service areas
MATSIM-944
do not use pure transit walk, pure drt walk, ...
MATSIM-943
design guidelines for multi-threading
MATSIM-942
put examples into resources path?
MATSIM-938
Cannot export matsim shapefile from JOSM
MATSIM-936
get rid of separateModes/filterModes/analyzedModes in TravelTimeCalculatorConfig?
MATSIM-934
just all all interaction activities "interaction"?
MATSIM-933
check OR-TOOLS
MATSIM-931
check openrouteservice
MATSIM-930
Do we really need subpopulation support for time allocation mutator
MATSIM-929
ERROR AbstractController:210
MATSIM-928
ArrayIndexOutOfBounds in TravelTimeDataArray during PlanRouter
MATSIM-926
"So-called teleportation" not working as documented
MATSIM-923
attributes writer/reader write/read enums
MATSIM-922
our policy w.r.t. "assert"
MATSIM-920
replace VehicleType interface by implementation
MATSIM-919
move the frozen epsilon material into separate contrib
MATSIM-917
organize packages by feature rather than by layer
MATSIM-916
make Dijkstra inheritance hierarchy non-public
MATSIM-914
MultiNodeDijkstra vs. LeastCostPathTreeExtended vs. DijkstraTree vs ...
MATSIM-913
ActivityWrapperFacility how
MATSIM-912
move jira issue tracker to github?
MATSIM-910
just one ID space for Facility
MATSIM-907
let persons own a vehicle?
MATSIM-906
github automerge pull requests
MATSIM-905
Remove Backward compatibility layer in PlansCalcScoreConfigGroup and PlanCalcRouteConfigGroup
MATSIM-903
Strange behaviour of PlansCalcRoute config group
MATSIM-901
travel times for multiple modes on same network
MATSIM-900
remove teleportation routing defaults
MATSIM-899
otfvis: paint vehicles in queue red
MATSIM-897
towards vehicles v2 xml fmt
MATSIM-896
What should we do with JDEQSim
MATSIM-894
issue 1 of 331

Router cannot find any route at all - abort replanning for agent?

Description

During the Replanning stage it can happen, that a replanning strategy switches an agent to a mode or a departure time for which the router cannot find any useful route. E.g. SubtourModeChoice forces an agent to use drt where no drt is available or TimeAllocationMutator moves the departure time after the departure of the last bus.

Currently we deal with that problem only in the routers for drt and pt, but similar problems can also occur for other modes (e.g. a short car trip where there are no roads / the next road is further away than the destination). The drt and pt routers currently return direct walk trips which create their own problems (see MATSIM-943, ), such as new modes for direct walk whose scoring parameters are unclear.

Would it be better to just abort replanning for the agent and switch back to his old plan? This way the agent will have a valid plan without any awkward direct walks.

I can imagine that the configuration of replanning strategies can become tricky. E.g. if SubtourModeChoice switches a subtour actA -> car -> actB -> car -> actC -> car -> actA to actA -> pt -> actB -> pt -> actC -> pt -> actA there might be a fast pt route for the first two trips, but maybe no service at all from C to A by pt. At the same time there could be drt from C to A, but not between A and B. So both the all pt subtour as well as the all drt subtour are impossible and would be always rejected after the router has not found a route. If SubtourModeChoice always switches the whole subtour from car to either all drt or all pt, the agent can never find the (possibly) optimal tour actA -> pt -> actB -> pt -> actC -> drt -> actA. In the current approach we would at least have actA -> pt -> actB -> pt -> actC -> transit_walk -> actA. So we might have to look deeper into the replanning modules in order not to exclude feasible plans only because no replanning strategy happens to create them in one single replanning step.

Any other ideas how to deal with situations in which there is no feasible or useful route for a certain mode?

Environment

None

Status

Assignee

Unassigned

Reporter

Gregor Leich

Labels

None

Components

Priority

Critical
Configure