Debug trip mode choice

[josiekre]

I updated the availability matrix. With the test data, the following counts resulted:

We can see that now RIDEHAIL is available at the trip level for valid combinations according to the documented table here: CTPSSTAFF#12

At the tour level, RIDESHARE still holds ~23% of tours.

At the trip level, RIDESHARE now is ~9% of trips and before it was 1%.

However, if you also look at trips with WALK that are in a tour with RIDESHARE, the numbers align.

Please check my work here. Does this satisfy debugging trip mode (ignoring the fact that RIDESHARE is still at 23% which will be addressed elsewhere)?

---

I am going to come back to this pull request if there is time and do some more clean up so do not yet merge it. Items to be cleaned up:

• Remove DRIVEALONEFREE and DRIVEALONEPAY from trip and tour mode files
• Remove tour_mode_is_non_motorized references remaining in code

[josiekre]

Via @mnbina in Teams:

yeah, that looks good! thanks for the tours x trips summaries

i think it might just be that there are a lot of short trips, resulting from tour mode choice logsums that are pretty far off because tour mode choice is pretty far off

looks like this can be "done" but circle back after the other things (bay area to CTPS translation, tour mode choice calibration) are done