jrlewi
October 10, 2018, 3:10am
2
Hi @bharath222 : It's hard to understand what you are trying to accomplish without providing a reproducible example (a.k.a. reprex). I've provided a couple links discussing what a reprex is and tips for creating them.
In space, no one can hear you scream.
– Alien (1979)
Luckily the tidyverse is a friendlier place. Ease of adoption and ease of use are fundamental design principles for the packages in the tidyverse. If you are banging your head in frustration,...
Why reprex?
Getting unstuck is hard. Your first step here is usually to create a reprex, or reproducible example. The goal of a reprex is to package your code, and information about your problem so that others can run it and feel your pain. Then, hopefully, folks can more easily provide a solution.
What's in a Reproducible Example?
Parts of a reproducible example:
background information - Describe what you are trying to do. What have you already done?
complete set up - include any library() calls and data to reproduce your issue.
data for a reprex: Here's a discussion on setting up data for a reprex
make it run - include the minimal code required to reproduce your error on the data…