Implement Leg and Activity Engines and prepare DRT functionality #140
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 includes a couple of changes.
General architectural changes:
Scenario
struct that holds all the entities relevant for simulation (similar to the Java reference implementation)ActivityEngine
andLegEngine
for separation of concernsActivityEngine
holds agents, that perform an activity and releases them at the endLegEngine
performs legs of the agents on the network as well as teleportation. It also communicates updates to other partitions.InternalInterface
is used to transfer agents between both engines (as the reference implementation)vehicles
DRT/Service architecture related changes: