#### VspConfigConsistencyCheckerImpl ``` vsp should move away from facilitiesSource=FacilitiesSource.none You are setting the marginal utility of traveling with mode ride to -12.0. VSP standard is to set this to zero. Please document carefully why you are using a value different from zero, e.g. by showing distance distributions. You are setting the marginal utility of traveling with mode bike to -3.0. VSP standard is to set this to zero. Please document carefully why you are using a value different from zero, e.g. by showing distance distributions. found qsim.linkDynamics=FIFO; vsp should use PassingQ or talk to kai found qsim.usePersonIdForMissingVehicleId==true; vsp should set this to false or talk to kai found `qsim.usingTravelTimeCheckInTeleporation==false'; vsp should try out `true' and report. you are considering car abailability; vsp config is not doing that. Instead, we are using a daily monetary constant for car. travelTimeCalculator is not analyzing different modes separately; vsp default is to do that. Otherwise, you are using the same travel times for, say, bike and car. ``` #### DrtConfigGroup ``` qsim.endTime should be specified and qsim.simEndtimeInterpretation should be 'onlyUseEndtime' if postponed request rejection is allowed. Otherwise, rejected passengers (who are stuck endlessly waiting for a DRT vehicle) will prevent QSim from stopping. Keep also in mind that not setting an end time may result in agents attempting to travel without vehicles being available. Consider increasing global.numberOfThreads to at least the value of drt.numberOfThreads in order to speed up the DRT route update during the replanning phase. ```