You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Oregon Modeling Steering Collaborative (OMSC) is currently designing a statewide survey (across all MPOs), as Oregon has done over the last several decades. As this survey is being completed, OMSC has interest in completing a joint ActivitySim estimation across all MPO model regions in the state (or as many regions as possible). The current understanding of the estimation feature in ActivitySim is that it is only geared for one ActivitySim implementation at a time (one model region). OMSC's effort would require an expansion/enhancement to the existing ActivitySim estimation feature to allow estimation to occur across multiple ActivitySim implementations (regions).
The text was updated successfully, but these errors were encountered:
@bettinardi discussed this effort on the 10/19/21 call,
May be some kind of bundler of multiple estimation data bundles (EDBs) across model setups
Or a way to point larch to multiple directories of data (EDBs) for joint estimation
Larch already does some of this so it feels doable
May need to make improvements to estimation mode, like sampling of destinations and times-of-days and figure out a way to deal with data conflicts across setups (like multiple TAZ 1000s)
ODOT will share progress with the agency partners as the effort progresses
The Oregon Modeling Steering Collaborative (OMSC) is currently designing a statewide survey (across all MPOs), as Oregon has done over the last several decades. As this survey is being completed, OMSC has interest in completing a joint ActivitySim estimation across all MPO model regions in the state (or as many regions as possible). The current understanding of the estimation feature in ActivitySim is that it is only geared for one ActivitySim implementation at a time (one model region). OMSC's effort would require an expansion/enhancement to the existing ActivitySim estimation feature to allow estimation to occur across multiple ActivitySim implementations (regions).
The text was updated successfully, but these errors were encountered: