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
Ohio and Oregon (ODOTx2) have pooled money to develop an LDT for ActivitySim. ODOTx2 have long term interest in this, as both of their statewide models currently have LDT representation. Other geographically large ActivitySim implementations might desire to use specific representation of longer distance travel (ODOTx2 models handle trips shorter than 25miles different than long distance travel decisions). Work has not yet started on LDT, but should in 2022. Additional status updates will be provided on this issue and the intent is to get feedback from ActivitySim partners as there is interest.
The text was updated successfully, but these errors were encountered:
As discussed on the 10/19/21 call,
- Alex (@bettinardi) and Rebekah (@rls-odot) introduced the effort
- They shared the scope for comment by next week
- Would be good to create an example_long_distance like the other examples so the code added for the model is backed by tests moving forward
- Some of the new components from the cross border model will be useful for this model as well
- Model was already designed, implemented, estimated, and calibrated years ago so this current effort is focused on re-implementation in ActivitySim
- ODOTs will periodically share progress with the agency partners
Ohio and Oregon (ODOTx2) have pooled money to develop an LDT for ActivitySim. ODOTx2 have long term interest in this, as both of their statewide models currently have LDT representation. Other geographically large ActivitySim implementations might desire to use specific representation of longer distance travel (ODOTx2 models handle trips shorter than 25miles different than long distance travel decisions). Work has not yet started on LDT, but should in 2022. Additional status updates will be provided on this issue and the intent is to get feedback from ActivitySim partners as there is interest.
The text was updated successfully, but these errors were encountered: