Adding the possibility to check the origin, destination and secondary destination for all agent journeys #553
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
only works with hotfix for previous bug now. The bug needs to be resolved first.
…system into agent-tours-print-origin-destination
|
I changed it to draft because there is this strange bug with the zone number. It should not be hotfixed like that, but probably needs deeper focus to figure it out. But maybe some of you knows immediately why it is like that. |
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.
The only change here is that tours.txt gets additional informational about all the important zones. Ideally that would allow for some quick filtering by origin and destination. If we could additionally manage to print the route as well it might be possible to do traversal analysis outside of Emme. Sorry if this is getting too Matsim.
I also know that for example the mode split of the agent-based model should still be validated, so it is just building on top of the experimental branch.