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

The following check fails for multi-index DataFrames since `df.index.name` for multi-indices is a list, not a string and therefore `df.index.name in df` is false and the index gets wiped. OD...

It wold be preferable to turn the warnings back on and address the issues explicitly: warnings.filterwarnings('ignore', category=pd.io.pytables.PerformanceWarning) pd.options.mode.chained_assignment = None

There may be a hidden math error in some scheduling models: generally, any model where the is a shift term that is the square of a time period value (start...

Pull request includes the following updates from the previous SEMCOG version: * Conversion from 1-zone to 2-zone * Inclusion of University of Michigan related models * Moved to 48 half-hour...

Draft pull request for disaggregate accessibilities. Works with 1 and 2 zone models. Tested but some issues remain: - Optional sampling and soft-merge methods using kmeans/naive bayes require sklearn package...

We want to build a functionality in ActivitySim to factor the input employment data down by a set of scaling factors that accounts for workers who work-from-home and workers who...

By default when creating subprocesses, windows and macOS “spawn” new processes, while on Linux you “fork”. https://docs.python.org/3/library/multiprocessing.html#contexts-and-start-methods Spawn is slow, but makes a new clean python instance with nothing preloaded....

### 1. User Stories #### User Story One As an owner of a travel demand model, I would like to transition to ActivitySim. As a first step, I would like...

simulation-based shadow pricing method implementation, with more details on the method discussed [here](https://github.com/ActivitySim/activitysim/wiki/Project-Meeting-2022.08.25#shadow-pricing-update-approach-and-implementation).

If a coefficient referenced in a spec file isn't defined in the corresponding coefficient file, it runs though the entire model flow and only crashes when it gets to that...