-
Notifications
You must be signed in to change notification settings - Fork 100
Project Meeting 2018.06.21
Ben Stabler edited this page Jun 23, 2018
·
26 revisions
- Trip mode choice implemented in branch trip-mode
- Updated trip destination choice to use trip mode choice logsums now as well
- Needed to revise and clean-up mode choice utility specifications to be easier to use / finalize
- @Jeff working on the full scale example run now
- A few trips failing with all zero_probs, and still investigating
- Issue in tour_mode_choice caused by the fact that some WALKDIST and BIKEDIST skims are asymmetrical (O->D vs. D->O) so tour_mode_choice would allow outbound walk (<3mi) but the return was >3mi, so they couldn’t get back
- Remember transit subzones were not implemented in this version
- Once complete, we'll do a pull request and then update documentation and re-release
- Example model design and sub-model designs updated
- Sub-models hyperlinked flow chart integrated
- Updated listing of all sub-model input files
- Updated data schema and built auto-documentation tool based on our data pipelining technology
- Updated getting started steps
- Lots of little clean-up in the docstrings and existing documentation
- Released Friday June 8th
- @Ben will update and re-release for trip mode choice updates
- Updated Progress Report through trip mode choice
- Current scope will be completed in a few days and all funds will be expended by then
- Updated Phase 4 Scope of Work posted for comment
- Moved multiprocessing to the top since it is the next important step
- Updated shadow pricing design to be flexible for use in all regions - allow for specifying classifiers for types of persons, land use, and geographies in the form of expression files for example
- Moved continued verification and clean-up to the end since it's an ongoing part of the overall effort
- Moved multiple zone systems to the end and suggested we test with either MTC TM2 or SANDAG instead of TM1 + fake data
- Lots of discussion about how best to implement support for multiple zones systems
- No one wants to create fake data for the TM1 example
- @Lisa and @Wu to think about setting up MTC and SANDAG
- @Ben to break out task into sub-tasks
- Setup example to implement new features for
- Add support for multiple zone systems
- Implement transit virtual path building
- See table below for multiple zone systems in use by region
- See you Monday night in Atlanta
Region | TAZs | TAZs + MAZs/parcels | TAZs + MAZs/parcels + transit stops | Notes |
---|---|---|---|---|
PSRC | X | gets transit access/egress times from nearest stop in the buffered MAZ/parcel file | ||
SFCTA | X | gets transit access/egress times from nearest stop in the buffered MAZ/parcel file | ||
MTC TM1 | X | |||
MTC TM2 | X | does transit virtual path building | ||
SANDAG | X | does transit virtual path building | ||
SEMCOG | X | current trip-based model | ||
ARC | X | X |