The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
An interface to the 'mclust' package to easily carry out latent profile analysis ("LPA"). Provides functionality to estimate commonly-specified models. Follows a tidy approach, in that output is in the form of a data frame that can subsequently be computed on. Also has functions to interface to the commercial 'MPlus' software via the 'MplusAutomation' package.
Version: | 1.1.0 |
Depends: | R (≥ 2.10) |
Imports: | dplyr, ggplot2, gtable, grid, mclust, methods, mix, MplusAutomation, tibble |
Suggests: | knitr, lme4, missForest, parallel, pillar, rmarkdown, testthat |
Published: | 2021-11-17 |
DOI: | 10.32614/CRAN.package.tidyLPA |
Author: | Joshua M Rosenberg [aut, cre], Caspar van Lissa [aut], Jennifer A Schmidt [ctb], Patrick N Beymer [ctb], Daniel Anderson [ctb], Matthew J. Schell [ctb] |
Maintainer: | Joshua M Rosenberg <jmrosenberg at utk.edu> |
BugReports: | https://github.com/data-edu/tidyLPA/issues |
License: | MIT + file LICENSE |
URL: | https://data-edu.github.io/tidyLPA/ |
NeedsCompilation: | no |
Citation: | tidyLPA citation info |
Materials: | README NEWS |
In views: | Psychometrics |
CRAN checks: | tidyLPA results |
Reference manual: | tidyLPA.pdf |
Vignettes: |
Introduction to tidyLPA Benchmarking mclust and MPlus |
Package source: | tidyLPA_1.1.0.tar.gz |
Windows binaries: | r-devel: tidyLPA_1.1.0.zip, r-release: tidyLPA_1.1.0.zip, r-oldrel: tidyLPA_1.1.0.zip |
macOS binaries: | r-release (arm64): tidyLPA_1.1.0.tgz, r-oldrel (arm64): tidyLPA_1.1.0.tgz, r-release (x86_64): tidyLPA_1.1.0.tgz, r-oldrel (x86_64): tidyLPA_1.1.0.tgz |
Old sources: | tidyLPA archive |
Reverse suggests: | tidySEM |
Please use the canonical form https://CRAN.R-project.org/package=tidyLPA to link to this page.
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.