activitysim icon indicating copy to clipboard operation
activitysim copied to clipboard

An Open Platform for Activity-Based Travel Modeling

Results 291 activitysim issues
Sort by recently updated
recently updated
newest added
trafficstars

@e-lo Augment documentation of model steps to include: - Key inputs, required fields, expected formats, and required fields - What settings and parameters files it uses - Where it fits...

@e-lo - Roll CDAP into /default folder - Add documentation to tops of files - Explore renaming and recategorizing misc.py - Refile nested logit helper functions - Put util functions...

Currently, activitysim only exports a list of trips, `final_trips.csv` | trip_id| person_id| household_id| tour_id|primary_purpose | trip_num|outbound | trip_count|purpose | destination| origin| depart|trip_mode | |-------:|---------:|------------:|-------:|:---------------|--------:|:--------|----------:|:--------|-----------:|------:|------:|:---------| | 8684833| 26478| 26478| 1085604|eatout |...

Currently both [core/input.py](https://github.com/RSGInc/activitysim/blob/develop/activitysim/core/input.py#L100) and [models/initialize.py](https://github.com/RSGInc/activitysim/blob/develop/activitysim/abm/models/initialize.py#L63) perform pipeline table column renames during the input/initialize steps. We can remove this from initialize.py and remove the `column_map` option from the [various annotation yamls](https://github.com/RSGInc/activitysim/blob/develop/example/configs/initialize_households.yaml).

As we consider future scenarios around CVs / AVs / EVs we might want to input given household and person characteristics as inputs and overwrite the "intelligence" in activitysim for...

We currently have two similar, but slightly different, approaches to shadow pricing. The "ctramp" approach from MTC TM1 and the "daysim" approach from DaySim. They are similar, but once the...

In many regions, job centers are concentrated in a few areas. Zones in these areas tend to have large employment. A max percentage-based convergence criteria doesn't prevent possible large absolute...

For example, tour category school + person type results in different tour primary purposes --> K-8, high school, university. It would probably be better to only use tour primary purpose...

@guyrousseau - For instance in mode choice, a sub-routine could be added in the source code that allows the user to enter calibration target values, and the program could adjust...

Performance (and perhaps memory) suffers for very large datasets when strings could be factors. This requires some thought as currently pipeline store doesn't handle factors (just numeric and string types).