Hi,
I am currently working with latent class models in Apollo and would like to inquire whether it is possible to implement a hierarchical latent class model. That is, a model structure allows for subclasses nested within higher-level latent classes.
If this is supported, could you kindly provide a code example and guidance on how to structure such a model in Apollo?
Thank you very much for your time and assistance!
Best regards,
kiki
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.
Nested Latent Class Model
-
stephanehess
- Site Admin
- Posts: 1320
- Joined: 24 Apr 2020, 16:29
Re: Nested Latent Class Model
Hi
could you provide a mathematical example of what you are after? Then I can advise on how to do this in Apollo
Stephane
could you provide a mathematical example of what you are after? Then I can advise on how to do this in Apollo
Stephane
Re: Nested Latent Class Model
Hi Stephone,
Thank you! The mathematical example can be referred in the paper named "A model for the simultaneous inference of attribute nonattendance and taste heterogeneity", Eq(1)-(9).
The outer latent classes are specified as a conventional latent class model, where each class has its own set of parameters. The inner IANA latent classes have only one set of parameters, which are shared across all inner classes. This parameter structure seems inconsistent with Apollo’s requirements. In the Apollo, all existing specifications of the latent class model have the same parameter structure (same number and naming of parameters) to construct the joint likelihood. When I attempt to include two indices in the utility function to reflect this structure, it triggers errors
Best regards,
kiki
Thank you! The mathematical example can be referred in the paper named "A model for the simultaneous inference of attribute nonattendance and taste heterogeneity", Eq(1)-(9).
The outer latent classes are specified as a conventional latent class model, where each class has its own set of parameters. The inner IANA latent classes have only one set of parameters, which are shared across all inner classes. This parameter structure seems inconsistent with Apollo’s requirements. In the Apollo, all existing specifications of the latent class model have the same parameter structure (same number and naming of parameters) to construct the joint likelihood. When I attempt to include two indices in the utility function to reflect this structure, it triggers errors
Best regards,
kiki
-
stephanehess
- Site Admin
- Posts: 1320
- Joined: 24 Apr 2020, 16:29
Re: Nested Latent Class Model
Hi
you only need the same structure if you write the classes in a loop. Otherwise you can have different structures in different classes. If you share your code, I can have a look
Stephane
you only need the same structure if you write the classes in a loop. Otherwise you can have different structures in different classes. If you share your code, I can have a look
Stephane