Clean up TimeAllocationMutators, add a new feature #2878
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ionMutatorChanges # Conflicts: # contribs/decongestion/src/test/java/org/matsim/contrib/decongestion/DecongestionPricingTestIT.java # contribs/pseudosimulation/src/test/java/org/matsim/contrib/pseudosimulation/RunPSimTest.java # matsim/src/main/java/org/matsim/core/config/groups/TimeAllocationMutatorConfigGroup.java
…ionMutatorChanges
…ityTimeAllocation
…nges' into feature/timeAllocationMutatorChanges
|
Due to the diferent way how randoms are generated, several integration tests return slightly different values. These have been adjusted. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR reduces the number of TimeAllocationMutators in MATSim from 3 to 1.
Also, the functionality to provide different mutationRanges per Subpopulation has been removed; it has not been accessible from config for several years.
Optionally, it is possible to allow timeMutation only around the initial endTime of an Activity.