-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Send routing failures to skims #3735
Merged
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
…ce alternatives. Add location fields to replanning event
4 tasks
Test! |
dimaopen
approved these changes
Mar 15, 2023
src/main/scala/beam/agentsim/agents/modalbehaviors/ChoosesMode.scala
Outdated
Show resolved
Hide resolved
Test! |
Test now! |
Test now! |
Test! |
Test! |
1 similar comment
Test! |
…replanning-event # Conflicts: # src/main/scala/beam/agentsim/agents/modalbehaviors/ChoosesMode.scala # src/test/scala/beam/router/skim/SkimmerSpec.scala
Test! |
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.
Several fixes to make sure that the skimmer keeps track of situations where no route is possible from an origin to a destination (particularly relevant for transit) so that we don't keep sending agents on that trip without realizing it's impossible. A couple of changes:
RouteNotAvailableForChosenMode
for when someone has a mode already chosen but an itinerary of that mode doesn't show up as possible in mode choice. Also added origin (and sometimes destination) location to the replanning event to make it easier understand what happened after the fact. Also create a failedODSkimmerEvent in this situation.observations
in the skims to clarify the difference between acompletedTrip
and afailedTrip
To do:Add test coverage