activitysim
activitysim copied to clipboard
An Open Platform for Activity-Based Travel Modeling
MWCOG staff encountered an _insufficient resources_ error when running a chunk-size training run for our Gen3, Phase I, Model on a server with 128 GB of RAM and 12 physical...
Currently there is no way to index into the land-use data file for each destination in the destination choice models. This makes it inconvenient to add district-district constants in destination...
As we have more contributors to the code, we should begin to enforce code formatting. The review of the SANDAG cross-border model and other enhancements revealed code changes that added...
The consortium has identified that we should review our formal governance document, which has not been reviewed in its entirety in a few years. Partners and collaborators are invited to...
Related to #335... @toliwaga said: _Sometimes (e.g. for mtctm1) [two YAML specificiations] will be identical to non_mandatory_tour_destination.yaml it would be nice to have a macro (like inherit_settings) that allows you...
At some point, it may be useful to develop and settle on official names for the [sub-model specification files](https://activitysim.github.io/activitysim/abmexample.html#sub-model-specification-files) types used in ActivitySim. The documentation does a good job laying...
In the non-mandatory tour destination and joint tour destination setting YAML (for the MTC example), it indicates that the logsums for the destination choice can optionally be included in the...
_Disclaimer: This is feature enhancement request. If I understand the code correctly, this should save some time while not impacting the results of the model. If my understanding of the...
Within [tour_frequency.py](activitysim/abm/models/util/tour_frequency.py) and [joint_tour_destination.py](activitysim/abm/models/joint_tour_destination.py), the non-mandatory tour types are hard-coded within the code. While the ARC model does use the same tour types as MTC, they are implemented slightly differently....
The write trip matrices methods should use the time period definitions included in the network LOS. The current implementation relies on time period labels being defined in the write_matrices.yaml outside...