Skip to content

[Bug]: Unidimensional Reliability CFA to PFA #3756

@dispatchgirl02

Description

@dispatchgirl02

JASP Version

0.95.2

Commit ID

No response

JASP Module

Reliability

What analysis are you seeing the problem on?

Unidimensional reliability McDonald's Omega

What OS are you seeing the problem on?

Windows 11

Bug Description

This analysis terminated unexpectedly.

Error in ff$loadings: $ operator is invalid for atomic vectors

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)

.frequentistComputeScaleResults(jaspResults, dataset, options, model)

.applyOmegaPFA(cc, loadings = TRUE)

Image
Image

Expected Behaviour

It shouldn't have terminated at all. It should be able to switch from CFA to PFA without any issue. I had already addressed the Q04 in my data having a negative inhibiting the omega calculation. I attempt the switch from CFA to PFA and it breaks

Steps to Reproduce

  1. toggle from CFA to PFA under unidimensional reliability

Log (if any)

No response

More Debug Information

-------- Application Info --------
JASP Version: JASP 0.95.2
Build Branch: development
Build Date: Sep 15 2025 19:32:54 (Netherlands)
Last Commit: d4766a76c131ef29aca77a3e8b2980360d7fca1a

-------- Basic Info --------
Operating System: Windows 11 Version 24H2
Product Version: 11
Kernel Type: winnt
Kernel Version: 10.0.26100
Architecture: x86_64
Install Path: C:/Program Files/WindowsApps/45842JASP.JASP_0.95.12.0_x64__wz6q9dg667qsj
Platform Name: windows
System Local: en_US

-------- Extra Info --------
Current code page
Active code page: 437
Active code page: 65001

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.

Metadata

Metadata

Assignees

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions