-
Notifications
You must be signed in to change notification settings - Fork 3
/
week1-rstudio.Rmd
283 lines (187 loc) · 12.4 KB
/
week1-rstudio.Rmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
---
title: "Week 1. Introduction to workflow using RStudio and Git"
output:
html_document:
toc: true
include:
after_body: footer.html
---
```{r setup, include=FALSE}
knitr::opts_chunk$set(echo = TRUE)
```
```{r echo=FALSE, message=FALSE, warning=FALSE}
library(kableExtra)
dt <- data.frame("Compartmentalized", "Documented", "Extendible", "Reproducible", "Robust")
kable(dt, col.names=NULL) %>%
kable_styling(full_width = TRUE) %>%
row_spec(1, bold = FALSE, color = "white", background = "blue") %>%
column_spec(column = 1:5, width = "20%")
```
# Overview
I will introduce you to RStudio and GitHub and show you how to use GitHub without having to learn Git. If you already use RStudio and Git, you can skip this week as this will be introductory level. If you have tried RStudio or Git and gotten frustrated or thought 'I don't have time to learn this', this is for you. If you want to learn how to easily keep track of changes in your code, this is for you. If you have never used RStudio, this is for you.
I'm going to show you how to work with Git/GitHub with no command-line interface using [GitHub Desktop](https://desktop.github.com/). See the [More Resources](links.html) tab above for a [nice online workshop](https://happygitwithr.com/) on Git/GitHub if you want to learn more. If you want to learn to use Git with RStudio, see the same workshop or my [2020 set-up info](https://rverse-tutorials.github.io/RWorkflow/set-up.html#Git_from_RStudio).
# RStudio
Open RStudio on your computer or on RStudio Cloud. To do the latter, click this link: https://rstudio.cloud/project/2574104
When you open RStudio you will see 4 panels:
## Create an RStudio Project
**On the desktop app**
1. In RStudio, choose "File->New Project..."
1. Then choose "New Directory" and then choose "Empty Project"
1. In the next dialog, choose a name (_it is best to use only letters, numbers, dashes, and underscores, and include no spaces in the name_).
1. Then click "Create Project".
**On RStudio Cloud**
1. On left, click 'Your Workspace"
1. Then click New Project (blue button on right)
### Add a new script file
1. Add a new file using 'File > New File > R Script'
2. Or you can click the new icon in top left corner.
2. Add some code to that file. Copy and paste in:
```
require(graphics)
## Annette Dobson (1990) "An Introduction to Generalized Linear Models".
## Page 9: Plant Weight Data.
ctl <- c(4.17,5.58,5.18,6.11,4.50,4.61,5.17,4.53,5.33,5.14)
trt <- c(4.81,4.17,4.41,3.59,5.87,3.83,6.03,4.89,4.32,4.69)
group <- gl(2, 10, 20, labels = c("Ctl","Trt"))
weight <- c(ctl, trt)
lm.D9 <- lm(weight ~ group)
opar <- par(mfrow = c(2,2), oma = c(0, 0, 1.1, 0))
plot(lm.D9, las = 1) # Residuals, Fitted, ...
par(opar)
```
### Run the code
1. Select all the lines of code and select 'Run'
2. Run all the code by selecting 'Source'
## Project organization
Keep your projects in separate folders with a uniform set of folder names. For example,
* R - your R code
* data - your data files
* output -
* inst - random stuff
* notes -
### Project settings
One tip is to **not** save your `.Rdata` (your environment) when your are done for the day. Under Tools > Project Options... > General
## Super helpful features
* Edit > Find in Files...
* Code > Comment
* Code > Reindent Lines
* File > New (templates)
* History tab
* Help tab (index at bottom)
* Help > Markdown quick reference
* Tools > addins Use with the stylr and spelling package
## More exercises
R for Data Science is a great book to introduce you to working with data in R. Read through the following sections of the R for Data Science book and work through the examples.
* [Workflow basics](http://r4ds.had.co.nz/workflow-basics.html): super basic review on how R works.
* [Workflow: projects](http://r4ds.had.co.nz/workflow-projects.html): info about organizing RStudio projects.
* [Workflow: scripts](http://r4ds.had.co.nz/workflow-scripts.html): how to evaluate code in scripts.
# Git (GitHub/GitLab)
Tracking your code (and project) changes. Today, I am focusing on Git for individuals **not teams**. If you aren't using a change tracker (version control) already, then start just with a personal project and track only your changes. I also will not cover *branches* today.
## Basics
* Repo: Repository. It is your code and the record of your changes. In a hidden folder called `.git` (so if you wanted to get rid of the history and other Git info, you could delete that folder). You have a local repo and a remote repo (on GitHub/GitLab).
* Actions: Commit, Push, Pull
* Git: The program that keeps track of the changes on local and remote("origin") repo.
* Git GUIs: A graphical interface for Git (which is command line). There are [many](https://git-scm.com/downloads/guis). I am teaching an easy-entry one, [GitHub Desktop](https://desktop.github.com/).
One-person Workflow (to get started):
* Make local changes to code.
* Record what those changes were about and commit to the code change record (history).
* Push those changes to your remote repository (aka origin)
Goals today:
1. Get you started.
2. Show you a simple workflow.
3. Show some simple GitHub features.
## Let's get started!
I am going to show a workflow that is usually robust. Connecting Git on your computer and GitHub is a source of much misery, and in my experience **creating the repo on GitHub first** eliminates the problems. This really important for the first time you connect your computer to the remote repository server (GitHub).
### Make a GitHub Repo {#clonerepo}
**New repo**
1. Go to GitHub and create a new repository (the + in the top right)
2. Click add Readme.md and add .gitignore (type R to get the R .gitignore)
3. Copy the url of your new repo
**Clone the GitHub repo to your computer**
*In the lecture, I showed this step using RStudio. I forgot that you have to tell RStudio where `git.exe` is for this to work. See [these instructions](#rstudiogit) for doing what I did in lecture (around minute 39). In Week 2, I switched to doing this with GitHub Desktop. That is the workflow I recommend when you get started. I have updated the notes to that workflow.*
1. Open GitHub Desktop
2. Click File > Clone Repository...
3. In the popup window, click the URL tab to the right and paste in the url from step 3 above.
4. Double check that you have the right folder for the Local Path. I keep all my repositories in Documents/GitHub so they are easier to find. Click Clone.
**Create an RStudio project from this new folder**
1. Open RStudio and click `New Project` (upper right, blue cube with R)
2. Click New Project... > Existing Directory
3. Navigate to the folder you just cloned from above and click 'Create Project'
Now you are ready to make some changes, commit them and push up to GitHub.
See these links if you want to do the cloning step from within [RStudio Desktop](#rstudiogit) or [RStudio Cloud](#rstudiocloudgit).
### Make some changes and commit
**Make a change**
1. In RStudio. Add a file. File > New File > R Script
2. Type something and then save the file.
**Now add a note and push to GitHub**
If you are doing this from your computer:
3. Switch to GitHub Desktop.
4. Click the changes that you want to commit (check the little checkbox next to the file). Add a comment: first line is subject, newline, description (options). And click `Commit`.
5. Click the Green up arrow to Push to GitHub.
If you are on RStudio Cloud:
Make sure you have RStudio Cloud [set up to use Git](set-up.html#Git_in_RStudio_Cloud).
1. Click the Git tab.
2. Click Commit.
4. Click Push, the first time you do this, it will ask for your your GitHub user name and password. Hopefully you only have to do this once. *Note: you may get an email from GitHub complaining about accessing GitHub via password. Ignore but accessing GitHub from RStudio may stop working in the future.*
### Make some changes and look at the history
1. Repeat 1-4 a few times.
2. Now look at the history. Just click the History tab in GitHub Desktop.
3. Push changes up the GitHub
### Go to GitHub to see your changes there
1. Go to your repo on GitHub
2. Refresh the page and you should see your changes
## Using Git to track personal changes w/o posting to remote repo
1. In GitHub Desktop, click File > Add local repository. Choose 'create repository' when it asks.
2. Don't publish to GitHub.
## Copy someone's else repo to your GitHub account
Don't Fork. That would be if you are contributing to their repo. If you just want to copy it and then adapt it for your purposes, do this.
1. In a browser, navigate to the repository that you want to copy. For example: https://github.com/RVerse-Tutorials/Test.
2. Copy its url.
3. Open GitHub and go to your account. So for me, I would go to github.com/eeholmes because my account is eeholmes.
4. If using GitHub, click the `+` in top right and click `import repository`. Paste in the url and give your repo a name.
5. Now that you have the url of your own repo, the [steps](#clonerepo) to clone it to your computer as the same as before.
## Key tips
1. Avoid making changes on GitHub directly---until you are a bit more experienced. Why? Because you're more likely to create merge conflicts. See the week 2 material for how to fix a merge conflict.
2. Do not use branches (wait till you are more experienced with Git).
3. Do not use Git at the command line. Wait until you are much more experienced (and even then you rarely have to go to the command line).
4. If you use Dropbox or iCloud on multiple computers to keep folders synced up across different computers, don't put your GitHub repos in those folders. Conflicted files are very likely if you ever work-offline.
5. The Git info is in the hidden folder `.git`. If you need to get rid of the repository data (like history), delete that. Don't copy that folder into another repo. The remote url is in `.git/config` if you need to check it.
## Working the Git from RStudio on your desktop {#rstudiogit}
Pushing/Pulling to GitHub from RStudio is a hassle because there are many steps to getting the credentials (passwords) properly communicated. These steps are operating systems dependent and can especially be a hassle if you don't have admin access on a PC.
However, you can clone repositories from GitHub and commit your changes (without pushing to GitHub) without having to do credentials. All you need to do is tell RStudio where `git.exe` is on your computer.
### Telling RStudio where `git.exe` is
1. Open RStudio
2. Click Tools > Global Options
3. Click Git/SVN on the left
4. Click the little check box at the top
5. In the Git executible box, paste in the location of `git.exe`
* On a Mac? It is at `/usr/bin/git` Just paste that in.
* On a PC? Look (by opening a finder window) in the following places. Try the GitHubDesktop one first.
* C:/Program Files/Git/bin/git.exe
* C:/Users/your.username/AppData/Local/Programs/Git/bin/git.exe
* C:/Users/your.username/AppData/Local/GitHubDesktop/app-2.8.3/resources/app/git/cmd/git.exe
6. Restart R. Session > Restart R...
*Note AppData is a hidden folder, so click View and then click the 'hidden files' checkbox if you don't see it in your Users folder.*
### Add the new repo to RStudio
1. Open RStudio and click `New Project` (upper right, blue cube with R)
2. Click New Project... > Version Control > Git and paste in the url. Give your project a name and make sure the directory is where you want the project.
3. Open GitHub Desktop: File > Add Local Repository. Then navigate to the new folder so GitHub Desktop knows about the repo.
4. Done!
## Clone a repo from GitHub into RStudio Cloud {#rstudiocloudgit}
1. Open RStudio Cloud and click 'Your Workspace' on left
2. Click New Project > New Project from Git Repository. Paste in the url.
3. In your project, click the Terminal tab (bottom left). Type
```
git config --global user.email "[email protected]"
git config --global user.name "your name"
```
I think you only do this once.
4. Done! Now you can commit and push from the Git tab.
## NOAA Specific Info
For NOAA staff, GitHub can be used for publishing public projects:
[NOAA GitHub](https://github.com/NOAAGov/NOAA-Affiliated-Projects) and a NWFSC example
[NWFSC Timeseries](https://nwfsc-timeseries.github.io/). NWFSC has a GitHub internal server if you want a repository server for your non-public projects and for internal collaboration.