jamovi

a new version of jTransform was recently pushed to the library (possibly in response to this post) ... it would be worth seeing if that fixes the issue.

cheers

hi,

can you tell me if the issue is specific to gamlj, or if other plots (say the descriptives from the explore menu) have the same problem?

with thanks

can you just confirm for me, when you run it with the --debug2 flag ... that you get three additional terminal windows?

jonathon

hi, could you try the 2.5.4 (from the downloads page). if that doesn't fix the issue, could you start jamovi in debug mode. you'll find 'jamovi debug' in the windows start menu, which will give you a terminal ... then you can start jamovi with the command jamovi --debug2 this will give you some extr...

OK, thanks for the info. i'll spend some time investigating.

i might come back to you to ask you to try some things, if that would be ok?

with thanks

jonathon

hi,

could you take a look here: https://github.com/jamovi/jamovi/issues/1483 and let me know if your experience is similar?

also, could you provide a .omv file (you may need to zip it up first), containing a plot which doesn't export correctly.

with thanks

yes, i think the slowdown increases exponentially with the number of filters.

jonathon

hi,

yes, you're right. there is a performance issue i've been meaning to take a look at.

https://github.com/jamovi/jamovi/issues/1453

jonathon

i think this will come down to how GGally searches for what corresponds to stat = "cross" ... i assume you've begun with running this code in an interactive R session (and had it work) and then you've moved to incorporate it into a jamovi module. i'm wondering if, when running this code in...

hi, yes, packages that rely on OS libraries are a bit tricky with the flatpak. the flatpak is designed to isolate the program from the host operating system, so installing libmagick++-dev into the host won't help unfortunately. sometimes R packages provide an alternative, so V8 for example allows yo...