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
This may be a lower priority issue since this is an older version of activitysim, but reporting here for posterity. When trying to run activitysim 1.2.2 with e.g. test_prototype_mtc (or sandag-abm3-example too), it just fails silently and no output (not even logs) are produced.
The only bigger issue here is that the current docs asks users to install with python=3.9, which would default to activitysim 1.2.2. Having the primary example then failing when new users are following the log creates a point of confusion.
If there's not an obvious reason to why this is happening, and I assume it's not worth anyone's time to figure this out for an old version of activitysim, perhaps the best solution is to either 1. update the docs and/or 2. take down 1.2.2 from conda-forge?
After issuing activitysim run -c configs -o output -d data, everything finishes in like a second and no output (screen or logs or anything else) is produced at all.
The text was updated successfully, but these errors were encountered:
chunhochow
changed the title
activitysim 1.2,2 (which is installed if you follow the current docs) doesn't actually run and fails silently
activitysim 1.2.2 (which is installed if you follow the current docs) doesn't actually run and fails silently
Jan 17, 2025
Last two version of sharrow library(sharrow=2.12.0 and sharrow=2.13.0) is not compatible with python 3.9. And installing activitysim according to the document mamba create -n asim python=3.9 activitysim -c conda-forge --override-channels installs last version of sharrow which is 2.13.0. So downgrading sharrow(sharrow=2.11.1 or lower versions) fixes the problem.
This may be a lower priority issue since this is an older version of activitysim, but reporting here for posterity. When trying to run activitysim 1.2.2 with e.g. test_prototype_mtc (or sandag-abm3-example too), it just fails silently and no output (not even logs) are produced.
The only bigger issue here is that the current docs asks users to install with python=3.9, which would default to activitysim 1.2.2. Having the primary example then failing when new users are following the log creates a point of confusion.
If there's not an obvious reason to why this is happening, and I assume it's not worth anyone's time to figure this out for an old version of activitysim, perhaps the best solution is to either 1. update the docs and/or 2. take down 1.2.2 from conda-forge?
To Reproduce
Steps to reproduce the behavior:
mamba create -n asim python=3.9 activitysim -c conda-forge --override-channels
test_prototype_mtc
at https://activitysim.github.io/activitysim/v1.3.1/users-guide/run_primary_example.htmlactivitysim run -c configs -o output -d data
, everything finishes in like a second and no output (screen or logs or anything else) is produced at all.The text was updated successfully, but these errors were encountered: