Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

umxEFA does not return loadings #112

Closed
AgnerF opened this issue Mar 24, 2020 · 3 comments
Closed

umxEFA does not return loadings #112

AgnerF opened this issue Mar 24, 2020 · 3 comments
Assignees
Labels
bug top5 marked as an active goal: close before working on other issues

Comments

@AgnerF
Copy link

AgnerF commented Mar 24, 2020

Thanks for maintaining this code and for fixing issue #103. I am impressed how well umxEFA solves problems with missing values and how it can do a factor analysis with more variables than observations. It takes hours to calculate in my case, even without the summary, but the result is perfect.

Anyway, two new bugs have appeared since last time:

  1. umxEFA returns the data matrix rather than the loadings unless you specify loadings="model".
  2. umxEFA does not work with rotation methods from GPArotation, e.g. quartimax. The error message says "Error in t.default(rm) : argument is not a matrix".
@tbates tbates added the bug label Mar 27, 2020
@tbates tbates self-assigned this Mar 27, 2020
@tbates tbates added the top5 marked as an active goal: close before working on other issues label Jul 15, 2020
@tbates
Copy link
Owner

tbates commented Jul 16, 2020

I pushed a commit to umxEFA last week so that it returns scores by default when requested (used to require user to also set return = "loadings") this and other edits might have fixed your issue. I'm can't replicate the issue with quartimax:

x = umxEFA(mtcars[, myVars], factors = 2, rotation = "quartimax", return = "loadings")
[1] "Rotation results"
Orthogonal rotation method Quartimax converged.
Loadings:
         F1     F2
mpg  -0.893  0.135
disp  0.914 -0.140
hp    0.756 -0.530
wt    0.968  0.177
qsec -0.327  0.833

Rotating matrix:
      [,1]   [,2]
[1,] 0.989 -0.149
[2,] 0.149  0.989

@mcneale
Copy link
Collaborator

mcneale commented Jul 16, 2020

Could you return SEs of the scores as well? With the rubbish scales many of us have to use/analyze, the SEs can vary a lot, which has knock-on side effects of subsequent analyses of the factor scores.

@tbates
Copy link
Owner

tbates commented Jul 18, 2020

Could add a note to people who want the full-Monty to use mxFactorScores which returns this attributed 3-D matrix:

 num [1:50, 1, 1:2] -0.167 -0.106 -2.137 -0.157 1.106 ...
 - attr(*, "dimnames")=List of 3
  ..$ : chr [1:50] "1" "2" "3" "4" ...
  ..$ : chr "G"
  ..$ : chr [1:2] "Scores" "StandardErrors"

Is there also an example paper doing something with SEs, I could cite that.

@tbates tbates closed this as completed Oct 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug top5 marked as an active goal: close before working on other issues
Projects
None yet
Development

No branches or pull requests

3 participants