This document provides guidance on sharing reproducible R code projects using version control with Git and GitHub. It discusses configuring Git and RStudio to work together, organizing R projects, publishing projects on GitHub, and tips for making code more shareable. Version control with Git allows tracking changes, collaboration, and recovering from issues like computer crashes. Following standards for coding style, documentation, and packaging environments helps ensure projects are reproducible.

1. Sharing 101
Code Reproducibility & Sharing
Series
Omnia Mohamed
Data Analytics Engineer , IBM

2. What you will NOT learn during this session?
How to Code in R
How to be professional Git users

3. What you’ll get from this session?
How to configure Git and R to play nice together
How to organize your R projects
How to publish your first R project on github
Some tips to make your code more shareable

4. Why we need git?

5. Version Control

6. Secure organized location for your code
Computer crashed?

7. Building a Career
● An essential skill for work market
● Your git account will be a portfolio of your data science projects
● Base for blogging

8. Team Collaboration
No need for shared folders
Easier tracking of changes
Code merging capabilities
Easy finger pointing

9. Who is who?
Git
Open source project for version control originally developed in 2005.
Github
Web-based Git repository hosting service, which offers all of the distributed revision
control and source code management (SCM) functionality.

10. Where do I start?
Install R & Rstudio
https://cloud.r-project.org/
https://www.rstudio.com/products/rstudio/download/
Install Git
https://gitforwindows.org/

11. Configure your account on git local
Open Git bash and run the following commands:
git config --global user.name 'Jane Doe'
git config --global user.email 'jane@example.com'
git config --global --list #this should show the configurations you just set

12. Create your first repository
From Git website :
Create new repository

13. Create your first repository
Get it local
Using R Studio :
1. File -> new project ->version control -> git
2. Insert repository url that u get from this screen
Or from git bash command line:
git clone https://github.com/YOUR-USERNAME/YOUR-REPOSITORY.git

14. Write your first script
File -> New ->R script
Generate some random data
x <- rnorm(1000)
y <- x * 2 + rnorm(1000)
df <- data.frame(x, y)
Visualize it
ggplot(data = df,mapping = aes(x,y))+geom_point()
Save!

15. Let’s land on git

16. Simple git workflow

17. Let’s land on git
Commit to local repository
Add comments
Push to remote repository
Check it out on the web

18. Tips for new gities
Comment your commits
Commit frequently
Push only tested code
Pull frequently

19. Sharing data science projects
The Ikea Mode Plug & Play Mode

20. The keys of a plug & play project
● Has readme file
● Standard coding convention
● Organized project directory
● Reproducible code
● Executable outputs

21. Read Me File
Project Title
Project scope
Environment and version info
Prerequisite
Installation guide
Example of usage
Authors
Contribution
License
You don’t need to
include all sections,
only the ones applies
to your project

22. Project Directory organization
Script files
known also
as “scripts”
folder
Markdown
reports each
markdown
has a folder
inside
Your data is saved here under 2 folders:
“Raw” for original data
“Preprocessed” for manipulated and
cleaned data
Each shiny app has a
folder under this one
You can have
additional folders as
you need like docs or
figs

23. Standard coding convention
Tidy verse style guide
Google R style guide

24. Make it Readable
File names : meaningful with no special chars and prefixed with order of the file if they
should run in sequence ,ex. 00_dataprep_functions.R
Attribute names : lowercase with _ ,ex. expiry_date
Assignment : using -> instead of ,ex. x <- 5 Alt+ -

25. Functions naming and commenting
Same naming as objects ,ex:
#' Drop last column of dataframe
#' @param data A dataframe.
#' @return dataframe after dropping last column.
#' @examples
#' drop_last_col(iris)
drop_last_col <- function(data){
dropped_data <- data[-c(length(data))]
return(dropped_data)
}
Function objective
Function parameters
Name is lowercase no special characters ,
opening brackets right after function
definition
Closing brackets at the end on seperate
line

26. Make it Reproducible - here
here() :
library(here)
file_name -> here(“data”,”file.csv”)
#The file_name string now holds the value of : “myprojectrootfolder/data/file.csv”

27. Make it Reproducible - Seed
For reproducing data or results that depend on random generation use seed() to
ensure same results every time.
par(mfrow=c(2,2))
for(i in 1:4){
x <- rnorm(1000)
hist(x, main = paste0("fig",i))
}

28. Make it Reproducible - Seed
par(mfrow=c(2,2))
for(i in 1:4){
set.seed(123)
x <- rnorm(1000)
hist(x, main = paste0("fig",i))
}

29. Make it reproducible - pacman
Make sure that the packages you use are installed on the running machine:
#check if pacman package doesn’t exist then install it
if(!require(pacman)){
install.packages("pacman")
}
#pacman will check the installation of packages , install them and load them into environment
pacman::p_load("tidyverse", "caTools", "glmnet")

30. Make it Reproducible
Environment practices:
● Use Packrat for libraries management
● Using checkpoint
● Using docker for full environment sharing

31. Make it executable
● Use R markdown for reporting analysis (will have a session on it later ;) )
● Use shiny apps for tools and interactive reports
● Use APIs for accessible models (Plumer is your friend)
● Create packages

32. Now it’s your turn
Fork repo of world life expectancy dataset:
https://github.com/rfordatascience/tidytuesday/tree/master/data/2018/2018-07-03
Create your own project
Organize it your way
Find out :
● Top 3 countries with highest life expectancy in 2015 .
● Top 3 countries who improved over past 20 years.
Share your repo with us on the meetup website
First 3 to submit
with the mentioned
guidelines will win
voucher of 50LE
worth

33. May the odds be ever in your favor!

34. References
Git Resources:
https://git-scm.com/book/en/v2
https://happygitwithr.com/install-git.html#install-git-windows
https://www.javaworld.com/article/2113465/git-smart-20-essential-tips-for-git-and-
github-users.html

35. References - cont.
Reproducibility and project organization:
https://swcarpentry.github.io/r-novice-gapminder/02-project-intro/
https://kbroman.org/steps2rr/pages/organize.html
https://github.com/swcarpentry/good-enough-practices-in-scientific-
computing/blob/gh-pages/good-enough-practices-for-scientific-computing.pdf
Read me template:
https://gist.github.com/PurpleBooth/109311bb0361f32d87a2

36. References - Cont.
Style guides:
https://style.tidyverse.org/files.html#names
https://google.github.io/styleguide/Rguide.xml
Environment packaging :
https://rstudio.github.io/packrat/walkthrough.html
https://colinfay.me/docker-r-reproducibility/

37. Thank you!
Cairo
Meetup