Open lisalan520 opened 9 years ago
I don't know exactly, but this is almost always because you have one column that is exactly the same as another column so the estimation is not identified. The most common case is that both columns end up as all zeros, but they can be the same, or one can be the same as the other times some factor, so like col_a = col_b * 2.0 or something. I intended to add a check for this but haven't had the time to add it.
Very helpful! This gives me a direction. I'll double check with my data. Thank you very much!
@lisalan520 have you managed to solve this issue? We have been sitting with exactly the same issue and if you could give us any guidance as to what caused this for you, it would save us a lot of time.
I too faced the same issue..turns out, one of the columns had a duplicate. removing that solved it!
Hi there,
First off, I'm still at location choice model (I got crash when I tried to update to discrete choice model). I get the following error when I run "elcm_choice" model with my own data. Do you have any idea what is going on? Thanks very much!
Here is the message in ipython notebook:
Running model 'elcm_estimate'
LinAlgError Traceback (most recent call last)