Dear Professors,
I am trying to estimate MDCEV model with my SP data for mode choice. In my dataset, each choice has a price attribute. The price attribute varies along individual, among individuals and alternatives
By checking the sample data and code provided in Apollo website for the MDCEV, the example of "time use data" does not include prices. And, in the definition of setting for the MDCEV without outside good, the COST for individual alternatives is equal to 1.
Following the explanation provided by the Apollo manual regarding the COST, I think I have a "vector of
length equal to the number of observations in the data". However, I do not know the code or the changes I must make in the "time use data" code to include the price attribute.
Thank you very much in advance.
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. We check the forum at least twice a week. It may thus take a couple of days for your post to appear and before we reply. There is no need to submit the post multiple times.
MDCEV with price attribute
-
stephanehess
- Site Admin
- Posts: 1355
- Joined: 24 Apr 2020, 16:29
Re: MDCEV with price attribute
Hi
I assume that for each alternative, you have a colum in the dataset with the price attribute for that alternative.
Let's assume your alternatives are called alt1, alt2, ..., and the costs are in columns called cost_alt1, cost_alt2, ...
Then you could specify it like this:
Hope this helps
Stephane
I assume that for each alternative, you have a colum in the dataset with the price attribute for that alternative.
Let's assume your alternatives are called alt1, alt2, ..., and the costs are in columns called cost_alt1, cost_alt2, ...
Then you could specify it like this:
Code: Select all
cost = list(alt1 = cost_alt1,
alt2 = cost_alt2,
...
Stephane
Re: MDCEV with price attribute
Hi Stephane,
Thank you for your response.
I did what you recommended and I got this message:
Error en apollo_validate(mdcev_settings, modelType, functionality, apollo_inputs):
INPUT ISSUE - Expenditure for some observations for model component "model" is either less or more than budget!
We have a mode choice with two alternatives. The continuous decision is the percentage of each alternative used by the decision-makers in each scenario, so the budget is 100.
I do not know where the mistake is. How can I solve this issue?
Thank you very much in advance.
Thank you for your response.
I did what you recommended and I got this message:
Error en apollo_validate(mdcev_settings, modelType, functionality, apollo_inputs):
INPUT ISSUE - Expenditure for some observations for model component "model" is either less or more than budget!
We have a mode choice with two alternatives. The continuous decision is the percentage of each alternative used by the decision-makers in each scenario, so the budget is 100.
I do not know where the mistake is. How can I solve this issue?
Thank you very much in advance.
-
stephanehess
- Site Admin
- Posts: 1355
- Joined: 24 Apr 2020, 16:29
Re: MDCEV with price attribute
Hi
You say below that the price attribute varies across individuals and alternatives, but your budget is looking at a % allocation. So those two things are not really consistent with each other. You might want to look at a FMNL model instead of MDCEV. You can then include price in the utility function
Stephane
You say below that the price attribute varies across individuals and alternatives, but your budget is looking at a % allocation. So those two things are not really consistent with each other. You might want to look at a FMNL model instead of MDCEV. You can then include price in the utility function
Stephane
Re: MDCEV with price attribute
Hi Stephane,
Thank you for your reply. After that, I realised that the definition of the budget was not correct. So, I changed it (price x quantity) and, then it worked.
However, it does not reach convergence with the "bgw" estimation method. For comparison purpose, I run the MDCEV for the example "leisure time" and I got same result: no convergence reached. The model diagnosis is "relative function convergence" in both cases.
How can I solve this?
Thanks!
Thank you for your reply. After that, I realised that the definition of the budget was not correct. So, I changed it (price x quantity) and, then it worked.
However, it does not reach convergence with the "bgw" estimation method. For comparison purpose, I run the MDCEV for the example "leisure time" and I got same result: no convergence reached. The model diagnosis is "relative function convergence" in both cases.
How can I solve this?
Thanks!
-
stephanehess
- Site Admin
- Posts: 1355
- Joined: 24 Apr 2020, 16:29
Re: MDCEV with price attribute
Hi
sorry, I had missed this post. Relative function convergence is normal convergence with BGW
Stephane
sorry, I had missed this post. Relative function convergence is normal convergence with BGW
Stephane