Hi Stephane,
in the meantime I fixed the problem. It seems that the order in which I define the alternatives in mnl_settings has to be the same order of my utility functions, at least in the case I am using lists. So when the utility funtion for "users" in my case comes first and the the utility ...
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.
Search found 3 matches
- 01 May 2021, 12:07
- Forum: Errors during model validation and/or estimation.
- Topic: Singular Hessian and estimated parameters close to 0
- Replies: 4
- Views: 21161
- 28 Apr 2021, 07:48
- Forum: Errors during model validation and/or estimation.
- Topic: Singular Hessian and estimated parameters close to 0
- Replies: 4
- Views: 21161
Re: Singular Hessian and estimated parameters close to 0
Hey Stephane,
please find the R script attached. Thanks for your help. I just X`d file paths
Best regards
Lukas ...
please find the R script attached. Thanks for your help. I just X`d file paths
Best regards
Lukas ...
- 27 Apr 2021, 16:31
- Forum: Errors during model validation and/or estimation.
- Topic: Singular Hessian and estimated parameters close to 0
- Replies: 4
- Views: 21161
Singular Hessian and estimated parameters close to 0
Hello all,
I am facing a problem with estimating a simple MNL model. I have done this several times before without any problems, but with the current model I always geht the error message "Singular Hessian, cannot calculate s.e.". Furthermore, all my estimated paramters are very close to 0. I have ...
I am facing a problem with estimating a simple MNL model. I have done this several times before without any problems, but with the current model I always geht the error message "Singular Hessian, cannot calculate s.e.". Furthermore, all my estimated paramters are very close to 0. I have ...