[Bug]: Error in diag(scales) %*% truevar: non-conformable arguments

[hjmo63]

JASP Version

0.18.3

Commit ID

No response

JASP Module

Factor

What analysis are you seeing the problem on?

Comfirmatory Factor Analysis

What OS are you seeing the problem on?

Windows 10

Bug Description

This is text that appear in the error message (see the image attached):

---

This analysis terminated unexpectedly.
Error in diag(scales) %*% truevar: non-conformable arguments
Stack trace
tryCatchOne(expr, names, parentenv, handlers[[1]])
doTryCatch(return(expr), name, parentenv, handler)
withCallingHandlers(expr = analysis(jaspResults = jaspResults, dataset = dataset, options = options), error = .addStackTrace)
analysis(jaspResults = jaspResults, dataset = dataset, options = options)
.cfaTableReliability(jaspResults, options, cfaResult)
semTools::compRelSEM(cfaResult[['lav']], return.total = TRUE)
omegaCat(truevar = commonCov, denom = totalCov, threshold = threshold[[b]][myIndNames], scales = latScales[[b]][myIndNames])
To receive assistance with this problem, please report the message above at: https://jasp-stats.org/bug-reports

---

The aim was to run a CFA. The curiosity about thist error is that it only occurs when the option "Reliability" under the section "Additional Output" was on!
The data file can be provided by private email on request, as the data is protected by confidentiality and informed consent.

Expected Behaviour

The reliability figures were expected to be presented.

Steps to Reproduce

1. In order to avoid the bug, the opion "Reliability" under the section "Additional Output" was disable.

Log (if any)

No response

Final Checklist

• I have included a screenshot showcasing the issue, if possible.
• I have included a JASP file (zipped) or data file that causes the crash/bug, if applicable.
• I have accurately described the bug, and steps to reproduce it.

[github-actions]

@hjmo63, thanks for taking the time to create this issue. If possible (and applicable), please upload to the issue website (#2791) a screenshot showcasing the problem, and/or a compressed (zipped) .jasp file or the data file that causes the issue. If you would prefer not to make your data publicly available, you can send your file(s) directly to us, issues@jasp-stats.org

[juliuspfadt]

Hi thanks for the report. This is a know issue that is already reported here #2294. Unfortunately it is out of our hands. You can read more in the original issue.

[hjmo63]

Thank you! Julius Pfadt ***@***.***> escreveu (terça, 25/06/2024 à(s) 14:32):

…

Hi thanks for the report. This is a know issue that is already reported here #2294 <#2294>. Unfortunately it is out of our hands. You can read more in the original issue. — Reply to this email directly, view it on GitHub <#2791 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BJLOUQITB4BC6UJ532ST27TZJFWOBAVCNFSM6AAAAABJV24CYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBYHE3TSMBRGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>