Additional estimation integration improvements in PR #328 based on feedback from SEMCOG, SFCTA, and Jeff Newman
Estimation mode works with existing destination choice sampling features. Maybe we should improve our examples and/or add more functionality to our existing sampling routines?
As we continue to work on estimation mode, make sure the integration with larch avoids duplication
Joe: Goal is that model specification coding occurs in one place only (ActivitySim) whether for application or to generate estimation files. We want to avoid any potential for inconsistency between estimation and application
I'm going to add some additional discussion about it being a framework (in addition to a stream of submodels) based on discussion Joe and I had related to just running TM2 tour mode choice example; for example, ideas around a data contract/registry for each submodel
Joe suggests we list out use cases for types of regional revisions - just changing coefficients, changing modes/alternatives, adding new submodels, revising the order/sequence of submodels - and how we might manage this
Alex is concerned that having each agency partner update/maintain their model is unsustainable and that we need to focus on version management by the partners
Stefan thinks the additional assurances for upgrading to new versions would be helpful
I think we need to separate explicit examples for each region from the need for more generic / modular examples to test all functionality
We need to over time increase submodel modularity
@Joe to setup a call next week to discuss in more detail since this is a complex topic to sort out in short meetings
@Partners to think about how much customization they need as we move forward
We're planning to discuss August 20th
Task 10 Support for Three Zone Systems and TVPB (milestone)
@Lisa working on data prep; I'm working on expression revisions
Jeff and I discussed more easily running just tour mode choice and potential improvements like exposing creation of tour and trip tables like initialize_households and initialize_landuse (e.g. initialize_tours and initialize_trips). Let's see what makes sense as we work on this example.