Some bad backtracking routes still sneak through the filtering

[KeetonMartin]

I know there's some kind of check to prevent significant backtracking. However, it seems this generated route was selected for today because its backtracking portion is small relative to the distance all the way to Jamaica. I suggest that we should change the backtrack filtering logic somehow to prevent these situations even for super long routes.

[KeetonMartin]

Another rough one today, also probably slipped through due to a long segment at one end (in this case the D)

[KeetonMartin]

I'm not sure if this is the same issue with filtering or something else, but this one just feels wrong

[blahblahblah-]

This won't fix everything, but after the D, 1, N solution, I realized that the Times Sq/Bryant Pk transfer was not included in the data when the solutions were previously generated, so I went ahead and did that in this commit:
436c5bc

[KeetonMartin]

Woof

[blahblahblah-]

Added crude calculation of progress towards destination per segment, and deprioritize solutions where any segment results in progress below -25%. Hope it helps with the backtracking. 1f27b0d

[KeetonMartin]

Thank you! Seems like it should be a great fix. I'll post again if I see more crazy routes :)

[KeetonMartin]

Ok, unfortunately I've seen a few weird ones in the last few days. N is still too small to say for sure if things got better or worse, but I think we still have some issues on our hands.