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
It would be very useful if the dcm estimation class reports how many records were used in the estimation. Especially in segmented choice models, when the segments might be smaller than estimation_sample_size, it would be extremely helpful to have that info.
It could go into the report_fit method. I would create a pull request but I don't know where the sample size is stored.
The text was updated successfully, but these errors were encountered:
This is something I've wanted as well. I don't think the number of observations is stored currently, but we could modify urbanchoice.mnl_estimate() to retain it:
Going farther, it would be nice to have a full summary table, like we get from StatsModels for OLS. I looked into this last year and set up a prototype in the ChoiceModels codebase. Here's the code and here's what it looks like (cell 13 near the bottom).
So a solution is definitely coming when we update UrbanSim to use the ChoiceModels estimation codebase later this year, but it should also be feasible to add reporting of the observation count as a quick fix. Maybe in conjunction with #208?
It would be very useful if the dcm estimation class reports how many records were used in the estimation. Especially in segmented choice models, when the segments might be smaller than estimation_sample_size, it would be extremely helpful to have that info.
It could go into the report_fit method. I would create a pull request but I don't know where the sample size is stored.
The text was updated successfully, but these errors were encountered: