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
PyLogit estimation for MNL is more flexible than the native ChoiceModels implementation (originally brought over from urbansim.urbanchoice.mnl), but much slower. See initial experiments here: Destination-choice-models-02.ipynb
What's causing the performance gap? If it would be easy to fix in PyLogit, then we wouldn't need to maintain a separate estimation codebase.
The text was updated successfully, but these errors were encountered:
PyLogit estimation for MNL is more flexible than the native ChoiceModels implementation (originally brought over from
urbansim.urbanchoice.mnl
), but much slower. See initial experiments here: Destination-choice-models-02.ipynbWhat's causing the performance gap? If it would be easy to fix in PyLogit, then we wouldn't need to maintain a separate estimation codebase.
The text was updated successfully, but these errors were encountered: