-
Notifications
You must be signed in to change notification settings - Fork 135
Phase 5 Scope of Work
Phase 5 will be performed during FY1920, ending in June 2020, and is likely to focus on, integration of multiple zone system support, support for modeling AVs and TNCs, input validation checking, output summarization, integration of PopulationSim, additional documentation / tutorial, and performance tuning.
Task 1: Project Management
Task 2: Support for Two Zone Systems
Task 3: Support for Modeling AVs and TNCs
Task 4: Input Validation Checking
Task 5: Output Summarization
Task 6: Integration of PopulationSim
Task 7: Additional Documentation and Tutorial
Task 8: Performance Tuning
The purpose of this first task is to manage the overall project, including invoicing and conference calls with the project team, and coordination with the AMPO agency partners. All deliverables, including meeting notes, software, tests, documentation, and issue tracking will be managed through GitHub. UrbanLabs will twice review project progress and QA/QC select project deliverables, as identified by the AMPO partners.
Deliverable(s): (Due XXX weeks from NTP)
- Management of Bi-Weekly Meetings
- Pre- and Post-Meeting Notes
- Invoicing and Progress Reports
- Client Coordination
- QA/QC of Select Deliverables
Comments
- xxxx
The goal of this task is to integrate comprehensive support for two zone system network level-of-service (see partner zone systems) into the ActivitySim framework. In two zone system models, for example the PSRC and SFCTA models, trips are modeled from MAZ/parcel-to-MAZ/parcel and the network level-of-service zone system varies by mode:
- Auto - TAZ-to-TAZ skims
- Walk/bike/near auto - MAZ-to-MAZ for nearby zone pairs using path costs from an allstreets network
- Transit - TAZ-to-TAZ skims except for access/egress time, which comes from the MAZ/parcel file, which includes access distance by transit line-haul for each MAZ
In three zone system models, for example the SANDAG and MTC TM2 models, transit stop-to-stop skims + a set of nearby stops for each MAZ are used to do transit virtual path building during a demand model run in order to build MAZ-to-MAZ transit impedance through the best access and egress stops. Under a separate contract, support for three zone systems (minus transit virtual path building) was prototyped using the SANDAG ABM model inputs.
The scope of this task is to integrate the prototyped three zone system implementation into a new two zone system example model for the MTC TM1 example. This will include switching from the one-zone skims classes to the multi-zone NetworkLOS classes, updating logging, updating tracing, updating all expression files with spatial data, including logsums, updating tests, updating expected test results, and updating the documentation. Full support for three zone systems (which adds transit virtual path building) may be done in a later phase of work.
The model system will operate at the "zone" level, which could be either MAZs or TAZs, and it will be possible to index into skims using the zone IDs or other zone attributes (such as TAZ if zones are MAZs for example). For testing, the MTC TM1 TAZ data will be copied to MAZs as if there is a one-to-one correspondence. In order to better test the relationships between the different data structures, a couple of MAZs will be re-assigned to different TAZs. The complete new example model will be tested and documented.
Deliverable(s): (Due XXX from NTP)
- Integration of Support for both One and Two Zone System Models
- Additional Full Scale Example
- Updated Documentation and Tests
Deliverable(s): (Due XXX weeks from NTP)
- xxxx
Comments
- xxxx
Deliverable(s): (Due XXX weeks from NTP)
- xxxx
Comments
- xxxx
Deliverable(s): (Due XXX weeks from NTP)
- xxxx
Comments
- xxxx
Integration of PopulationSim into the consortium.
Deliverable(s): (Due XXX weeks from NTP)
- xxxx
Comments
- xxxx
Deliverable(s): (Due XXX weeks from NTP)
- xxxx
Comments
- xxxx
Deliverable(s): (Due XXX weeks from NTP)
- xxxx
Comments
- xxxx
| Region | TAZs (1) | TAZs + MAZs/parcels (2) | TAZs + MAZs/parcels + transit stops (3) | Notes |
|---|---|---|---|---|
| PSRC | X | Transit IVT, etc from TAZ-to-TAZ skims. Transit access/egress times looked up by sub-mode in the buffered MAZ/parcel file and represent time to nearest stop. | ||
| SFCTA | X | Transit IVT, etc from TAZ-to-TAZ skims. Transit access/egress times looked up by sub-mode in the buffered MAZ/parcel file and represent time to nearest stop. | ||
| MTC TM1 | X | |||
| MTC TM2 | X | Does transit virtual path building during a model run to build MAZ to MAZ impedance through the best transit access and egress stops | ||
| SANDAG | X | Does transit virtual path building during a model run to build MAZ to MAZ impedance through the best transit access and egress stops | ||
| SEMCOG | ? | ? | ? | Trip-based model uses TAZs |
| ARC | X | |||
| ODOT | X | Does transit virtual path building during a model run to build MAZ to MAZ impedance through the best transit access and egress stops | ||
| MetCouncil | X |