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

Missing values in frequency tables #2202

Closed
baltzis opened this Issue Dec 3, 2017 · 2 comments

Comments

Projects
None yet
4 participants
@baltzis

baltzis commented Dec 3, 2017

*** JASP version:** 0.8.4
*** OS name and version:** Windows 10 (64- and 32-bit)
*** Analysis:** When missing values are defined, in the frequency table they always appear as zero answers and the percent column is always identical to the valid percent column. I think that this can't be right, because the difference between the two columns - as I understand it - are indeed the missing values.

JASP seems unable to show the frequency of the missing values. Is this a bug? Shouldn't there be some difference between percent and valid percent columns (like in SPSS)?

Please not, that I am not sure whether my question is related with some bug in JASP 0.8.4 or I am not doing something right.

Thank you

*** Steps to reproduce:** Import some data file (.sav) with missing values in a variable and get Descriptive Statics for this variable. Ask JASP to display the frequency tables.

@EJWagenmakers

This comment has been minimized.

Show comment
Hide comment
@EJWagenmakers

EJWagenmakers Dec 3, 2017

You are correct. Currently the frequency tables do not really use the "percent" column, as the invalids appear to be ignored. We'll fix this. @TimKDJ @vankesteren

EJWagenmakers commented Dec 3, 2017

You are correct. Currently the frequency tables do not really use the "percent" column, as the invalids appear to be ignored. We'll fix this. @TimKDJ @vankesteren

@boutinb boutinb self-assigned this Dec 5, 2017

boutinb added a commit to boutinb/jasp-desktop that referenced this issue Dec 5, 2017

@TimKDJ

This comment has been minimized.

Show comment
Hide comment
@TimKDJ

TimKDJ Dec 7, 2017

Contributor

The correct table will be in version 0.8.5. Thank you for reporting this to us.

Contributor

TimKDJ commented Dec 7, 2017

The correct table will be in version 0.8.5. Thank you for reporting this to us.

@TimKDJ TimKDJ closed this Dec 7, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment