Hi David and Stephane!
I have a question about price variable.
In my stated preference database, I have four levels (150, 250, 350, 450) for the price attribute.
Is that a correct practice, if I divide by 100 these levels in my database and I use these levels (1.15, 2.5, 3.5, 4.5) for estimate models?
I've experienced it before, price attribute levels with narrower ranges work better, especially in case of random parameter models, and models is WTP-space.
And after, when I calculate WTP estimates (beta(attribute)/beta(price)), I multiply by 100 the received values.
Is it a correct practice?
Could you recommend literature on the subject?
Thank you very much for your answer!
Best regards,
David
Important: Read this before posting to this forum
- This forum is for questions related to the use of Apollo. We will answer some general choice modelling questions too, where appropriate, and time permitting. We cannot answer questions about how to estimate choice models with other software packages.
- There is a very detailed manual for Apollo available at http://www.ApolloChoiceModelling.com/manual.html. This contains detailed descriptions of the various Apollo functions, and numerous examples are available at http://www.ApolloChoiceModelling.com/examples.html. In addition, help files are available for all functions, using e.g. ?apollo_mnl
- Before asking a question on the forum, users are kindly requested to follow these steps:
- Check that the same issue has not already been addressed in the forum - there is a search tool.
- Ensure that the correct syntax has been used. For any function, detailed instructions are available directly in Apollo, e.g. by using ?apollo_mnl for apollo_mnl
- Check the frequently asked questions section on the Apollo website, which discusses some common issues/failures. Please see http://www.apollochoicemodelling.com/faq.html
- Make sure that R is using the latest official release of Apollo.
- Users can check which version they are running by entering packageVersion("apollo").
- Then check what is the latest full release (not development version) at http://www.ApolloChoiceModelling.com/code.html.
- To update to the latest official version, just enter install.packages("apollo"). To update to a development version, download the appropriate binary file from http://www.ApolloChoiceModelling.com/code.html, and install the package from file
- If the above steps do not resolve the issue, then users should follow these steps when posting a question:
- provide full details on the issue, including the entire code and output, including any error messages
- posts will not immediately appear on the forum, but will be checked by a moderator first. This may take a day or two at busy times. There is no need to submit the post multiple times.
Price variable
-
- Site Admin
- Posts: 1046
- Joined: 24 Apr 2020, 16:29
Re: Price variable
David
changing the units of the price attribute in this way will just change the units of the coefficient, so your model will remain the same. Rescaling like this can be beneficial sometimes for computational reasons - have a look at the discussions in the manual about using scaling, which means you don't need to do the transformations yourself
Stephane
changing the units of the price attribute in this way will just change the units of the coefficient, so your model will remain the same. Rescaling like this can be beneficial sometimes for computational reasons - have a look at the discussions in the manual about using scaling, which means you don't need to do the transformations yourself
Stephane
Re: Price variable
Thank you for your help Stephane!