🚀 Feature: Year 2023 Calibration and Validation

[DavidOry]

User Story

As a model owner, I would like to have a validated model system with a base year of 2023.

Progress:

• Sufficiently defined
• Approach determined
• Tests developed
• User story satisfied
• Doc strings
• General documentation
• Passing tests

Priority

High

Level of Effort

High -- see Task Order 6

Resolution Ideas

At the end of Sprit 3, the modeling system was performing well for year 2015 (details here). To get to 2015, we must:

1. Prepare the year 2023 inputs: MAZ/TAZ data, networks
2. Prepare the year 2023 calibration targets: telecommuting, work location choice, mode choice
3. Prepare the year 2023 validation information: PeMS counts, transit boardings, BART station-to-station

Project

MTC Task Order 6

Who should be involved?

Users: @FlaviaTsang, @lmz
Reviewers: @gregerhardt, @DavidOry

Risk

Low. Only changes in configuration and UEC constants are expected.

Tests

Acceptance Criteria summaries (partially blocked by #174)

[DavidOry]

Updates on the MTC side:

1. Roadway network: likely summer earliest?
2. Transit network: likely summer earliest?
3. MAZ/TAZ data: springish? (TM1 data is here for reference)
4. Calibration targets: springish?
5. Validation: summerish? New on-board survey of BART is almost ready.