jasp-stats / jasp-issues

This repository is solely meant for reporting of bugs, feature requests and other issues in JASP.
55 stars 29 forks source link

[Bug] process did not get a vector or list as column #2777

Open ektas55 opened 2 weeks ago

ektas55 commented 2 weeks ago

JASP Version

0.18.3

Commit ID

No response

JASP Module

Process

What analysis are you seeing the problem on?

PROCESS

What OS are you seeing the problem on?

Windows 11

Bug Description

I am trying to work On PROCESS but it is showing error This analysis terminated unexpectedly.

Error in x$[[<-(i, value): Did not get a vector or list as column.. Stack trace doTryCatch(return(expr), name, parentenv, handler)

withCallingHandlers(expr = analysis(jaspResults = jaspResults, dataset = dataset, options = options), error = .addStackTrace)

analysis(jaspResults = jaspResults, dataset = dataset, options = options)

.procRsquared(jaspResults, options, modelsContainer)

[[<-(*tmp*, 'var', value = NULL)

[[<-.jaspTableR(*tmp*, 'var', value = NULL)

x$.__enclos_env__$private$setField(field, value)

[[<-(*tmp*, field, value = NULL)

.local(x, i, j, ..., value = value)

x$[[<-(i, value)

To receive assistance with this problem, please report the message above at: https://jasp-stats.org/bug-reports

Expected Behaviour

Should have shown output

Steps to Reproduce

  1. No
  2. ...

Log (if any)

No response

Final Checklist

github-actions[bot] commented 2 weeks ago

@ektas55, thanks for taking the time to create this issue. If possible (and applicable), please upload to the issue website (https://github.com/jasp-stats/jasp-issues/issues/2777) 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

tomtomme commented 1 week ago

@ektas55 thx for the report. Can you rename the .jasp file you used to .zip and upload it here so we can try to reproduce the error? Sadly the error message alone does not tell the whole story of what went wrong.

maltelueken commented 6 days ago

Thanks for creating the issue, my suspicion is that this bug is already solved in the new release, but without the .jasp file I can't be sure.