jasp-stats / jasp-issues

This repository is solely meant for reporting of bugs, feature requests and other issues in JASP.
56 stars 29 forks source link

[Bug]: Path diagram not readable in JASP #2692

Open aitorgarces opened 2 months ago

aitorgarces commented 2 months ago

JASP Version

0.18.3

Commit ID

No response

JASP Module

SEM

What analysis are you seeing the problem on?

SEM

What OS are you seeing the problem on?

Windows 10

Bug Description

"I have been trying to perform SEM analysis, but I encounter a problem when producing the path diagram: the labels are unreadable and everything is superimposed, including the coefficients. SEM-wrong path diagram

Expected Behaviour

I would like it to be solved - I tried modifyin the R code in JASP but it didn't work either.

Steps to Reproduce

  1. Produce the PATH DIAGRAM under the Output options label.

Log (if any)

No response

Final Checklist

tomtomme commented 2 months ago

Did you try changing its size via the triangle on the lower right of each plot?

aitorgarces commented 2 months ago

Did you try changing its size via the triangle on the lower right of each plot?

Yes, @tomtomme, I did. But it didn't work either.

tomtomme commented 2 months ago

Confirmed also for 0.19 beta flatpak. The problem: If I change size of the path plot numbers also change size, not only the shapes.

@juliuspfadt To fix this we may need a) a way to fix or to alter the font size in the GUI OR b) an algorithm that detects when fonts overlap and places them differently. We have something for this for boxplots. When a boxplot has many outliers, the row numbers get placed so that they do not overlap most of the time.

Other suggestions from duplicate #680:

juliuspfadt commented 2 months ago

Good suggestion. However I doubt this will be fixable on our end. The plot is entirely based on semPlot which is producing plots that are not as nicely scalable as plots produced with ggplot. I think there is not R-package that produces nice looking sem plots to be honest.

juliuspfadt commented 1 month ago

if @vandenman can back me up, we can close this as not fixable on our end.

github-actions[bot] commented 2 weeks ago

This issue will be automatically closed in 42 days due to inactivity. Feel free to leave a comment if you believe this is still relevant.