b-rodrigues / rap4all

https://raps-with-r.dev/
Other
96 stars 31 forks source link

Mention RStudio projects (.Rproj) for reproducibility #39

Closed andreranza closed 1 year ago

andreranza commented 1 year ago

Thanks for making this OS. I have read some parts of the book, attended one of the workshops held online, and found everything in your talk helpful! One minor thing I noticed is that, as far as I am concerned, RStudio projects should be mentioned to improve reproducibility. At least for those using the RStudio IDE (maybe the majority, nowadays), this is very handy.

Reference:

b-rodrigues commented 1 year ago

Hi Andre

happy that you’re finding the book useful! Regarding .Rproj files, I prefer discussing solutions that don’t rely on RStudio simply because a more general solution is more portable. If your project relies on RStudio to deal with paths, then other users will need to have RStudio as well. This is less portable than a solution that deals with paths in a different way, and relying on RStudio wouldn’t work inside Docker or on Github Actions, hence why I prefered not to rely on it.

I do mention Rstudio projects: https://raps-with-r.dev/prerequisites.html#essential-knowledge but again, prefer to teach without relying on it.

andreranza commented 1 year ago

Thanks a lot Bruno for your answer. Please excuse me, I've somehow missed that part by searching for "project" in the repo. I see your point. I haven't use docker nor GH actions yet, so I am not able to tell how relying on .Rproj would look like in that case at the moment. Anyway, thanks a lot again for clarifying your choice and all the material made available!