#### VspConfigConsistencyCheckerImpl

```
you have values set for the default scoring fct; we should only set values for explicit subpopulations
You have no strategy configured that uses ChangeExpBeta. vsp default is to use ChangeExpBeta at least in one strategy.
timeAllocationMutator is affecting duration; vsp default is to not do that.  Reason is that the upstream demand generation uses activityEndTimes for long activity types and duration for short activity types.  However, for a short activity of, say, 10min, a mutation of plus/minus the time mutation range leads to problems.
timeAllocationMutator mutates around the initial end time only; vsp default is to not do that.  Reason is that mutating around the initial end time destroys the economic interpretation of MATSim ... since travellers who stop adjusting because of this switch are no longer driven by the scoring function, but by the computational process.
The latest activity end time of the timeAllocationMutator is too early.  It should be infinity, but since that setting is not possible, it should minimally be the last time step of the qsim.
```
<style>
.dash-row.row-warnings .dash-card-frame {
    background: none;
}
.dash-row.row-warnings .no-warnings {
	color: #4BB543;
	font-weight: bold;
}
.dash-row.row-warnings .found-warnings {
	color: #ED4337;
	font-weight: bold;
}
.dash-row.row-warnings h4 {
	color: white;
	background: #6f5425;
	font-weight: bold;
	padding: 0.75rem 1.5rem;
	margin-top: 1rem;
	border-radius: 10px 10px 0 0;
}
.dash-row.row-warnings pre {
	background: #f8f3d6;
	color: #6f5425;
	border-radius: 0 0 10px 10px;
	white-space: pre-wrap;
}
</style>