Skip to content
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

Min_cost failure should be configurable to just be a warning #169

Open
e-lo opened this issue Jul 5, 2018 · 0 comments
Open

Min_cost failure should be configurable to just be a warning #169

e-lo opened this issue Jul 5, 2018 · 0 comments
Assignees

Comments

@e-lo
Copy link
Member

e-lo commented Jul 5, 2018

Right now the min_cost failure in path-finding raises a fatal error.

Desired flow:

  • Default behavior is for fast-trips to fail hard across all processes with a min_cost failure encountered in any trip.
  • An optional config_ft.txt attribute allows all the processes and trips to continue and will generate a list of trips with failed min_costs either at end of path-finding or with a full run of fast-trips.
@e-lo e-lo added the usability label Jul 5, 2018
@e-lo e-lo added this to the SHRP2 Project Completion milestone Jul 5, 2018
@e-lo e-lo assigned lmz Jul 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants