this is a necessary addition to fix #263
See #263 for more information.
This should probably be implemented as an additional argument, so people can still use the re-ordering for backward compatibility.
(Also, validation might otherwise break!).
I'm thinking reorder = FALSE, defaulting to FALSE, so people can use these objects for manual rotation in future.
Besides, my guess would be that as discussed in #263 and on CrossValidated, there's not a lot of reason to re-order components in Q methodology to begin with.
For backward compatbility, and for validation tests, we can set reorder = TRUE.
this is a necessary addition to fix #263 See #263 for more information.
This should probably be implemented as an additional argument, so people can still use the re-ordering for backward compatibility. (Also, validation might otherwise break!).
I'm thinking
reorder = FALSE, defaulting toFALSE, so people can use these objects for manual rotation in future.Besides, my guess would be that as discussed in #263 and on CrossValidated, there's not a lot of reason to re-order components in Q methodology to begin with.
For backward compatbility, and for validation tests, we can set
reorder = TRUE.