[Bug]: Computing data using drag-and-drop

[wenyingyao]

JASP Version

0.19.0

Commit ID

No response

JASP Module

Other

What analysis are you seeing the problem on?

Creating new variable from existing data

What OS are you seeing the problem on?

Windows 11

Bug Description

In the previous version of JASP, we can easily create indicator variable using drag-and-drop, for example, if I want to create an indicator variable "young" based on my existing data "age", I can create a new column, make it have data type Scale, and drag-and-drop "age<30", the computed column will take value of 1 and 0. Now this functionality does not exist any more, and instead shows "TRUE" and "FALSE" in the computed column which are not usable in any subsequent regression analyses. How do I change this without resorting to R code?

Expected Behaviour

Use drag-and-drop to compute indicator variable easily and show them as numerical data that can be used for analysis directly. This is the main reason that I am using JASP for my class that it does not require coding, but now it is not usable for an entry-level data analysis course. At the very least tell people how to change these TRUE/FALSE variables into 1/0 with proper documentation.

Steps to Reproduce

1. add a column
2. compute with drag and drop
3. put in some logical statement
   ...

Log (if any)

No response

More Debug Information

No response

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.

[github-actions]

@wenyingyao, thanks for taking the time to create this issue. If possible (and applicable), please upload to the issue website (#2927) 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

[JorisGoosen]

Aah this is a small problem introduced by the flexibility to use any type for anything.
Perhaps turning the type of the computed column into Ordinal helps?
Other analyses will now still be able to use it as scale afterwards.

[JorisGoosen]

Ah no...

Ok, I will fix this for the next version.

[JorisGoosen]

(There is a workaround by using R-code and putting the function "as.numeric(X)" around the code.
But given that you dont want to have your students use code this might not be helpful atm.

[tomtomme]

@another workaround now that you can change values - just change true false to 1 0 after the computation:

Also the labels can be deleted or changed as needed if needed.