I am using jamovi desktop 2.4.11 as a portable app started from the unpacked zip-file.
When I am using multiple instances of the same analysis, e.g., three times descriptives (each one for a different variable, example file attached), the syntax/analysis is changing after activating a filter.
In the attached file I have 4 random variables (A, B, C, and D) and I am running the three following analyses:
jmv::descriptives(
data = data,
vars = A)
jmv::descriptives(
data = data,
vars =
jmv::descriptives(
data = data,
vars = C)
After activating the prepared filter (Filter1 = D==2) the syntax of the three analyses is changing, e.g.:
jmv::descriptives(
data = data,
vars = A)
jmv::descriptives(
data = data,
vars =
jmv::descriptives(
data = data,
vars = A)
If adjusting the third descriptives back to C, it changes again after deactivating the filter to A or sometimes to B. Furthermore all arguments (e.g. showing the variance) will be reseted to the standard.
Sometimes it changes the second descriptives, if this one is currently highlighted.
This behavior includes other analyses, too, not only the descriptives. Is this a bug or am I just using the tool wrong? I am coming from SPSS and trying to switch to jamovi for my classes, so maybe I just need an advice how to use jamovi properly.
Really strange: After opening the attached file the first time, the syntax will not change. After clicking on one analysis or adding more analyses, you can see the above described behavior.
Wish you a merry Christmas and a happy new year.
Activating filter changes syntax
Activating filter changes syntax
- Attachments
-
- FilterChangesSyntax.omv
- (5.86 KiB) Downloaded 256 times
Re: Activating filter changes syntax
Looks like a bug to me. If I toggle back and forth a dozen times--between the filter being on versus off--the "variables" being "described" do change arbitrarily.
Re: Activating filter changes syntax
Thanks for testing and verifying.
As this seems to be a reproduceable bug I reported it on the issues page on github.
As this seems to be a reproduceable bug I reported it on the issues page on github.