snowRMM Latent Profile Analysis Error Message: argument 1 is not a vector
Posted: Sun Oct 11, 2026 11:48 am
Hello there!
Has anyone tried to analyze the PISA data using the snowRMM Latent Profile Analysis module? When I tried it with data from my country (about 7,000 participants), I kept receiving the same error message: argument 1 is not a vector. I have already:
1. Inspected the original Excel dataset and identified blank cells in all four LPA indicators.
2. Removed cases with missing values
4. Verified that all four indicators were numeric decimals.
5. Set the measurement level of the indicators to Continuous in jamovi.
6. Considered reducing the number of profiles from three to two.
7. Removed one of the variables and reran LPA using the remaining three indicators; the error persisted.
8. Investigated whether negative values were causing the error.
9. Added 10 to all indicator values; the error persisted.
10. Considered whether excessive decimal precision was causing the error.
11. Tested a subset containing the first 500 cases; the error persisted.
12. Ran LPA using the built-in iris dataset; the analysis appeared to work.
Thank you in advance to anyone who can help me. Thank you.
-enerbon
Has anyone tried to analyze the PISA data using the snowRMM Latent Profile Analysis module? When I tried it with data from my country (about 7,000 participants), I kept receiving the same error message: argument 1 is not a vector. I have already:
1. Inspected the original Excel dataset and identified blank cells in all four LPA indicators.
2. Removed cases with missing values
4. Verified that all four indicators were numeric decimals.
5. Set the measurement level of the indicators to Continuous in jamovi.
6. Considered reducing the number of profiles from three to two.
7. Removed one of the variables and reran LPA using the remaining three indicators; the error persisted.
8. Investigated whether negative values were causing the error.
9. Added 10 to all indicator values; the error persisted.
10. Considered whether excessive decimal precision was causing the error.
11. Tested a subset containing the first 500 cases; the error persisted.
12. Ran LPA using the built-in iris dataset; the analysis appeared to work.
Thank you in advance to anyone who can help me. Thank you.
-enerbon