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 enables the user to run a drt scenario without running the
DrtCaseSetup
class (which is triggered by the command line option--drt-area <SHP-FILE>
). This means, configuring drt on the config level should be possible and enough.This is achieved by cleaning up the code, mainly in
DrtCaseSetup
. Specifically, code parts for configuration (config
),scenario
preparation, andcontroller
configuration are separated and put into the right order.Finally, the configuration of the controler is not triggered any more by the command line option
--drt-area
but rather by auto-detection of theMultiModeDrtConfigGroup
in the config.The user still has to set the command line option
--intermodality drtAsAccessEgressForPt
if he wants to model drt+pt intermodal trips and fare compensations.I might change the default for that (in another PR), as Flexa is supposed to be intermodal.