stefancoe

Airport transit trips soared when testing a pricing scenario.

Like UW, U-District, for example.

Some parcels will share the same network node as a transit stop and have a distance of 0. I think Daysim may consider this not accessible. Add code to accessibility.py...

An r squared north of .99 seems good enough and this may save on run time since we never achieve our target rmse, which may be sensitive to one value...

travcost field in _trips.tsv file all 0s

7

This is the [commit](https://github.com/RSGInc/DaySim/commit/f75418f0505f96442ba5ebd394bf90de29e6d95e#diff-9d333767ce72ef4f46708b2674693e3621f47c04749d18ec102859cee9829068L542) that causes it to stop being populated with non-zero values (when there are actual costs). I added TravelCost = modeImpedance.TravelCost; back in and it works, so...

Use lower case column names throughout

1

I think Daysim expects parcel file name to be lowercase. We switch between upper and lower case a lot. Let's be consistent and use lowercase.

We should have an input checker to validate all tables at the beginning of each run. Likely this would use pandera.

maz_to_maz tables are required in two zone systems. Should they be?

3

Any reason not to make these optional?

@jpn-- See attached log and trace file. This is happening with sharrow on or off when running with multiprocessing. [activitysim.log](https://github.com/ActivitySim/activitysim/files/11326216/activitysim.log) [choosers-605809.csv](https://github.com/ActivitySim/activitysim/files/11326217/choosers-605809.csv)