jamovi

PeteD wrote: ↑Sun Oct 29, 2023 5:48 am I'm getting this error today: Version 2.3.38

Lost everything until saving, and luckily it wasn't a lot.

Should have said: On Windows 11. (Can't see how to attached screenshot.)

I'm getting this error today: Version 2.3.38

Lost everything until saving, and luckily it wasn't a lot.

You say: barplots with error bars are discouraged by, for example, Nature journals because they break a number of important rules : they don't show the data, and they don't show the distribution. I would *love* to have the reference to this article to pass on to people I know. Any chance you can pro...

Yep--variables without spaces in their names work OK.
Thanks.
P.

And now three groups of students are encountering the same error with different data sets (2 x Mac; 1 x windows; plus the windows machine I am using).

I got a barchart working on a windows computer with made-up data. But the students' data failed again: Debug Error in parse(text = elt): <text>:1:7: unexpected symbol 1: Usage of ^ eval(ev) eval(ev) private$.barPlot(image, theme = t$theme, ggtheme = t$ggtheme, ...) ggplot(data = tab, aes_string(y = ...

Hi team My students are having trouble with data in two-way tables: Two qualitative variables, and the chi-test of independence. The test works OK, but when they select to find a barchart, an error emerges (in English in version 1.6.23; in Japanese in 2.0.0; they are using a Mac laptop): "<text...

Yes, the *variable names* were the problem, *not* the file name as the error message stated. There was no issue with the file name.

Easy to fix when the error message points to the correct place! All good now.

P.

Hi all When I try to export a data file in SPSS (.sav) format, I get a message saying the file name contains an illegal character. (See attachment.) I can export the same file as .csv, and I can save the .omi file without similar errors using the same file name. And I get the same error message what...

But I see no one has (yet) proposed a correct alternative! [RE "Having to call something "continuous" that is clearly discrete doesn't really do anyone a service when setting up data."] I proposed "quantitative". Even if that is not perfect, it surely is less confusing...