Error in DvrpModeRoutingModule about matsim-maas HOT 6 CLOSED

I can't tell from the error message, and right now don't have enough time to run this myself.

The speedy alt router for dvrp is in principle replaceable, but you are right that it does not use the config setting from controler. If you wanted to bushwhack your way forward, the approach would be:

1. inline the TaxiControlerCreator material.
2. inline the MultiModeTaxiModule material.
3. inline the TaxiModeModule material. And there, change the routing factory.
   But I am not recommending this. :-|

People tell me that "drt" is better maintained than "taxi". Can't say of that would help in this case here ...

I will ask other people to step in with help.

PS: Thank you so much for providing so much material.

from matsim-maas.

Thanks for reporting this issue. There was a bug in the landmark calculation, it should be fixed now: matsim-org/matsim-libs#2559.

There is also one more error: please remove the route element from all taxi legs in the input plans.

from matsim-maas.

This PR brings in the fix in matsim-libs to matsim-maas: #106. Please use this matsim version (or newer).

from matsim-maas.

Great, thank you for looking into this so quickly.
I also suspected missing landmarks in the roundabout network, so my plan for today was to try with a bigger network, but I will now go on with the fix and report back.

from matsim-maas.

Thanks again, the scenario robotaxi+roundabout runs through now.

One minor comment/question:
QSim seems to want the agents to walk:

Caused by: java.lang.RuntimeException: just encountered mode for which no scoring parameters are defined: walk
        at org.matsim.core.scoring.functions.CharyparNagelLegScoring.calcLegScore(CharyparNagelLegScoring.java:114)
        at org.matsim.core.scoring.functions.CharyparNagelLegScoring.handleLeg(CharyparNagelLegScoring.java:192)
        at org.matsim.core.scoring.SumScoringFunction.handleLeg(SumScoringFunction.java:115)
        at org.matsim.core.scoring.ScoringFunctionsForPopulation.handleLeg(ScoringFunctionsForPopulation.java:232)
        at org.matsim.core.scoring.EventsToLegs.handleEvent(EventsToLegs.java:354)
        at org.matsim.core.scoring.ScoringFunctionsForPopulation.handleEvent(ScoringFunctionsForPopulation.java:185)
        at org.matsim.core.events.EventsManagerImpl.callHandlerFast(EventsManagerImpl.java:294)
        at org.matsim.core.events.EventsManagerImpl.processEvent(EventsManagerImpl.java:119)
        at org.matsim.core.events.SimStepParallelEventsManagerImpl$ProcessEventsRunnable.run(SimStepParallelEventsManagerImpl.java:344)
        at java.base/java.lang.Thread.run(Thread.java:833)

But neither the original robotaxi_config.xml nor the roundabout.xml define modeParams for walk. When I add walk in my modeParams, the simulation runs through again:

<parameterset type="modeParams">
   <param name="mode" value="walk" />
</parameterset>

So while I appreciate QSim to motivate the agents for physical activity, I still wonder why this situation never happened when I ran roundabout and robotaxi seperately, both without defining a modeParam for walk?

from matsim-maas.

Matsim may need walk legs to "bushwhack" from facilities to the network. So it is in principle possible that it needs scoring values for walk even if walk is not used as a "main" mode. So maybe such a "bushwhacking walk" was not necessary in the robotaxi example, but they become necessary when combining robotaxi and roundabout. (Or not: Please spend some time checking at least in the plans file where these walk legs show up.)

from matsim-maas.