Skip to content
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

Failure to convert variable to continuous: values contain text[Bug]: #2626

Open
2 of 3 tasks
cudzz opened this issue Mar 6, 2024 · 3 comments
Open
2 of 3 tasks

Failure to convert variable to continuous: values contain text[Bug]: #2626

cudzz opened this issue Mar 6, 2024 · 3 comments
Assignees
Labels
Bug: Medium Bugs that don't influence the basic function of the app, but it's better to fix them at some point. Component: Import/Export

Comments

@cudzz
Copy link

cudzz commented Mar 6, 2024

JASP Version

0.18.3

Commit ID

No response

JASP Module

Unrelated

What analysis are you seeing the problem on?

Before-- Just opening data

What OS are you seeing the problem on?

macOS Intel

Bug Description

have data that I uploaded to JASP before (with fewer subjects) where the program automatically interpreted the variables I needed to be continuous as such. Now after cleaning up my fresh subset of data from new subjects in excel and exporting it as a cvs file, the variables will not change. They also won't change manually when I try to and the following message pops up: "failure to convert variable to continuous: values contain text".

I have also checked my data multiple times and don't have text in the columns that I want to change.

Expected Behaviour

It should look like this:
Screen Shot 2024-03-04 at 11 28 39

It's showing up like this: and I cannot change it.
Screen Shot 2024-03-04 at 11 29 10

Steps to Reproduce

No idea.

Log (if any)

For JASP-Table 1.csv.zip

CVS file used is linked.

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.
@shun2wang
Copy link
Contributor

Yes exactly, if I look into the csv file it seems has about 100 empty rows at bottom, if I remove them then worked. in .csv we can see something like:

"
","
","
","
","
","
","
","
","
","
","
","
","

@boutinb it's really tricky, I remember we discussed we may find a way to trim empty rows,for now, we can at least detect active rows (black row numbers). We can work backwards from the last active row to determine whether it is a empty row, and then select the longest column as whole active rows number. For example:

JASP row No. col1 col2 col3 col4
1 a 21 w q
2 a 32 q
3 32 a
4 x
5

so we should trim row 5. blank rows at the top has little impact because it is easy for users to spot it and decide whether to remove it?Or only for this issue, we can consider how to skip empy values when convert the variable?

@cudzz
Copy link
Author

cudzz commented Mar 7, 2024

Oh thank you. I got rid of the 11 rows and it worked! Somewhere along the procedure i must have copied too much over.

@cudzz cudzz closed this as completed Mar 7, 2024
@tomtomme tomtomme reopened this Mar 7, 2024
@tomtomme tomtomme added Bug: Medium Bugs that don't influence the basic function of the app, but it's better to fix them at some point. Component: Import/Export and removed OS: macOS Intel Bug labels Mar 7, 2024
@tomtomme
Copy link
Member

tomtomme commented Mar 7, 2024

Confirmed for flatpak. Will close the duplicate #2623

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug: Medium Bugs that don't influence the basic function of the app, but it's better to fix them at some point. Component: Import/Export
Projects
None yet
Development

No branches or pull requests

5 participants