Closed gpessoaamorim closed 1 year ago
I believe the only change I have made to my session lately was to update tidyverse to the latest version; my ggalluvial version is still 0.12.3
@gpessoaamorim thanks a lot for raising this issue. I will get to it within a week.
Would you be able to share a subset or toy version of your data that reproduces the second (bad) plot?
Thanks - subset with toy data attached
Thank you! I ran the code with these data using both versions of {ggalluvial}—0.12.5 and 0.12.3. Both runs produced the same plot, the "good" one above. Could it be that one of your other packages is out of date? If you upgrade to 0.12.5, does this resolve the problem? (Or is there a reason you can't upgrade right now?)
You're absolutely right - just updating {ggalluvial} to 0.12.5 did the trick - I wasn't expecting that to be the issue from the release notes, but I guess it's always worth a try! Thanks for looking into this and apologies for the unwarranted issue request - closed now
@gpessoaamorim no problem! And this was not an unwarranted issue—it's valuable to know that this behavior is possible, even if it's possibly not a problem with {ggalluvial} itself. Thanks again.
I have data in the following structure:
Using the code below
I was able to produce the following plot:
For some reason, I have rerun my code and now I get something similar to this:
It seems that the x axis is not being properly separated, despite both the upstream code and the plotting code remaining the same. Note the x axis is specified as factors as shown on top
Session info here:
Thanks for your thoughts