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.
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.