-
Notifications
You must be signed in to change notification settings - Fork 29
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
[Bug]: quality control indivudal control chart won't run #2394
[Bug]: quality control indivudal control chart won't run #2394
Comments
Hi @mindyschwartz, thanks for your report. I cannot reproduce this error, would you mind sharing your dataset or JASP file here? |
JASP file. It won't let me run a variable chart for individuals with
session# as the axis label and SCL or PT CON as the variable. I am able to
run the chart for all the other variables (OQ, WAI etc) but I get an error
message when I try to run it for these two variables.
…On Wed, Nov 8, 2023 at 1:36 PM JTPetter ***@***.***> wrote:
Hi @mindyschwartz <https://github.com/mindyschwartz>, thanks for your
report. I cannot reproduce this error, would you mind sharing your dataset
or JASP file here?
—
Reply to this email directly, view it on GitHub
<#2394 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BD2SWYVGSK2Z4TD7GKUMZDDYDPGJFAVCNFSM6AAAAAA7DKPM66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBSGQ2DANRUGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@mindyschwartz I cannot see the JASP file, unfortunately. I think you might need to upload it on GitHub directly (and possibly change the ending to .zip). |
JASP data sheet_Without missing data.csv |
JASP with input missing data.jasp.zip |
@mindyschwartz Thanks, that worked. I could reproduce this with JASP 0.18.1. This is fixed already in the development code. So this will work in the next release (or if you need it earlier, you can download a nightly release at https://static.jasp-stats.org/Nightlies/ some time after jasp-stats/jaspQualityControl#288 is closed) |
thanks for the reply. I need it for a school assignment due at the end of
November. Will the nightly release or the JASP 0.18.1 be released before
then so I can run my analysis for the assignment in time?
…On Wed, Nov 8, 2023 at 3:49 PM JTPetter ***@***.***> wrote:
@mindyschwartz <https://github.com/mindyschwartz> Thanks, that worked. I
could reproduce this with JASP 0.18.1. This is fixed already in the
development code. So this will work in the next release (or if you need it
earlier, you can download a nightly release at
https://static.jasp-stats.org/Nightlies/ some time after
jasp-stats/jaspQualityControl#288
<jasp-stats/jaspQualityControl#288> is closed)
—
Reply to this email directly, view it on GitHub
<#2394 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BD2SWYQT7NPD2C4UPQUAL43YDPV7HAVCNFSM6AAAAAA7DKPM66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBSGY2TGOBUGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@mindyschwartz I am pretty confident it should happen before the end of November. Otherwise, you can also download an older version from the JASP website, the bug is also apparently not present in JASP 0.17.3 for instance. |
JASP Version
0.18.1
Commit ID
No response
JASP Module
Quality Control
What analysis are you seeing the problem on?
variable chart for indivudals
What OS are you seeing the problem on?
macOS Silicon
Bug Description
Error in tableIListCombined[['test3']]: subscript out of bounds
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 = da
taset, options = options)
To receive assistance with this problem, please report the message above at: https://jasp-stats.org/bug-reports
Expected Behaviour
produced a control chart
Steps to Reproduce
...
Log (if any)
No response
Final Checklist
The text was updated successfully, but these errors were encountered: