Describe the bug
The model crashes in trip_mode_choice because all probabilities are 0. Tour mode choice is 'walk' so 'walk' should be the only option in trip mode choice, but the OD distance for 'walk' is longer than the max allowed so all choices end up with 0 probability. Tracing the distances (scroll to bottom of attached trace files) in tour and trip mode choice shows different walk distances being used for the same OD. I confirmed that the distance used in tour mode choice is from our maz_to_maz_walk table and the distance used in trip mode choice is from the walk distance skim. The skim distance is quite large because the two MAZs belong to a very large TAZ and the skim value represents the intrazonal travel time. The MAZs are right next to each other so the distance is actually quite small.

We saw another case where the MAZs were not in the same zone and the distance values were different in the reverse direction according to the trip_mode_choice log file. So one direction was getting the maz_to_maz distance while the other was getting the skim distance.

To Reproduce
Steps to reproduce the behavior:

1. Use this mp settting, but change from 20 to 12 processors.
2. Use this for folder for all others settings, but change number of households to 100,000.
3. I'll provide a link once I get the input data uploaded.

Expected behavior
Tour and trip mode choice should use the same walk distance for the same OD.

tour_mode_choice_annotate_choosers_preprocessor-4c698d.csv

trip_mode_choice_annotate_trips_preprocessor-4c698d.csv