The problem with c-logit is - as far as I understand- that it does not accept the type of aggregated data I have. My dataset looks something like this:
model choice attribute1 etc.
1 50 100000
2 32 50000
3 98 76000
etc.
where model refers to the type of car, choice to the number of times this car was sold and attribute to f.ex price of that car. Is it the case that STATA cannot so a multinominal discret choice analysis with this type of dataset?
best regards,
astrid
-----Opprinnelig melding-----
Fra: Jitian Sheu [mailto:[email protected]]
Sendt: 30. april 2003 15:56
Til: [email protected]
Emne: st: Re: Constrained multinominal logit problem
For McFadden's Conditional logit model, the right command should be -
clogit-, instead of - mlogit-
these two model are slightly different.
you can see manual or any microeconometric book for a description
jt
----- Original Message -----
From: "Mathiassen, Astrid" <[email protected]>
To: <[email protected]>
Sent: Wednesday, April 30, 2003 7:28 AM
Subject: st: Constrained multinominal logit problem
> Hey,
> I am doing a multinominal discrete choice analysis (McFadden's conditional
logit model). My dataset contains aggregated information. My dependent
variables are the number of times each of the 50 alternatives (of cars) were
chosen. The corresponding attributes are, Zjr, (where j refer to alternativ
and r to attribute f.ex. price).
> For this procedure I use mlogit with 48 constraints. The constraints imply
that the coefficient for each attribute should be equal, hence bjr=b1r for
all j.
> I have redefined the attribute-vector so that Zj*=Zj-Z1. Hence I use
alternative 1 as the base category (reference).
> I am a first time user of STATA and are a bit insecure on how this work.
In particular, I do not understand the output report. The puzzle is that in
the output report ONE, and the last listed elements in the attribute
vectors, is dropped for each alternative - except for the last alternative
where the estimates are reported for all elements of the attribute vector.
This also happens in the special where attribute vector contains only one
element. Hence, it cannot be explained by interedependency between the
elements of the attribute vectors.
> Could you help me understand what's going on? Or could you indicate an
alternative procedure?
>
> Thank you very much in advance
> best regards,
> astrid
>
> My model statement look like this (number refer to the number of times the
alternative was chosen):
> mlogit depvar attribute1 attribute2 etc. [aweight=number], noconstant
constr(2-49) basecategory (1)
>
>
>
>
>
>
>
> *
> * For searches and help try:
> * http://www.stata.com/support/faqs/res/findit.html
> * http://www.stata.com/support/statalist/faq
> * http://www.ats.ucla.edu/stat/stata/
>
*
* For searches and help try:
* http://www.stata.com/support/faqs/res/findit.html
* http://www.stata.com/support/statalist/faq
* http://www.ats.ucla.edu/stat/stata/
*
* For searches and help try:
* http://www.stata.com/support/faqs/res/findit.html
* http://www.stata.com/support/statalist/faq
* http://www.ats.ucla.edu/stat/stata/
