-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 0.2.0 #19
Version 0.2.0 #19
Conversation
General Layer Rasteriser
Refactor based on rasterise()
@VPetukhov One thing to check is if the vignettes look acceptable to you. After this, we can upload to CRAN (which may require some changes) and version afterwards. |
Hey @evanbiederstedt, UPDATE: the vignette is cool, with the only small thing about |
Hi there @VPetukhov
Yeah, I realize it's using the legacy code. After failing to get jitter working as expected with
Good catch! Will change. I forget now why I used
It's a bit annoying, I agree. The issue is, the vignettes are timed by CRAN, and they need to be under a certain time limit. That's why I came up with this crazy solution. We could try a larger number---I'll try two magnitudes greater or so |
RE: So, it cannot be Ideas? Or is I think that's the last thing to decide, then we are set to merge! |
Are you sure? :) If so, I'm fine with both "rasterpoint" or "mpochemuchka". But my first-glance impression was that its goal was to match the |
You're entirely right---I was confused yesterday (i.e. very wrong). I have figured out what had been bothering me, but it's not worth while getting into. Viktor's original code:
Correcting the mistake here: ggrastr/R/geom-boxplot-jitter.R Line 10 in a02b88b
Sadly, "mpochemuchka" isn't valid:
So, I'll change to |
@VPetukhov I think I figured out the problem; it should be working now.
I cannot explain to myself why the numbers were so skewed previously for vector plots... |
Thank you so much, @evanbiederstedt! Now we're finally done with that! :) |
rasterise()
function