-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy path09-initiating-rstudio-project.qmd
104 lines (63 loc) · 3.68 KB
/
09-initiating-rstudio-project.qmd
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
---
output-file: initiating-rstudio-project.html
---
# Initiating an R/RStudio project {#sec-initiate-projects}
Following is a diagram of the steps in initiating your own R/RStudio project.
<!---  -->
```{mermaid}
%%| label: initiate-project-workflow
%%| fig-cap: A flowchart for initiating an R project
%%| fig-align: center
%%| file: mermaid/create-new-project.mmd
```
## Create a new project in RStudio {#sec-create-project}
### Click on New Project button on RStudio
### Create a New Directory
### Select New Project as project type
### Specify details for new project
#### Specify a project name {.unnumbered}
::: {.callout-note}
Best practices for naming a project are:
* Make sure that name is succinct (as short as possible while at the same time descriptive of the project);
* Don't use spaces for your project name. If you need to separate words, use a ***hyphen*** or an ***underscore***;
* Avoid using capital letters.
:::
#### Specify a directory/location {.unnumbered}
Select a directory in your local machine where to place the directory of your new project
#### Decide whether to use git to version this project {.unnumbered}
Here you can decide whether you want to use git to version your project. Remember that using git doesn't mean you have to use GitHub. git is software installed in your local machine and it versions what you have on your local machine. You don't need GitHub or any other similar service to version your code with git in your local machine.
I would recommend that you tick this option for any new project you create so that you can version your work in your local machine even if you don't want or decide not to use GitHub or any other remote git service.
#### Do you want to open a new session {.unnumbered}
This is by default unticked and will open the new project within the existing RStudio session (if any). This means that if you have an existing RStudio session with another project that you are working on, that project will be closed and the new project you are creating will open in the existing RStudio session.
If you need your existing RStudio session and the project within it to remain open alongside the new project you are creating, tick this box/option.
#### Click on Create New Project {.unnumbered}
Once you click on ***Create New Project***, you will now see the new project open in RStudio.
You will also see something like below within the file explorer pane of RStudio.
## 2. Structure/organise your new project appropriately
::: {.callout-note}
Project organisation is vital because:
* supports productivity because the different components of the project are placed in directories where they should be;
* enables clarity in communicating project structure;
* facilitates collaboration.
:::
Organising an R project can be user- and project-dependent but there are generally accepted project organising structure that is common to most well-organised projects. Below is an example:
```
|-- my-project
|-- data
|-- output
|-- figures
|-- R
|-- my-project.Rproj
|-- analysis_workflow.R
|-- README.md
```
## 3. Start coding
This will include creating bespoke R functions (as required) and creating an Rscript for the step-by-step processes in your scientific workflow.
## Next steps
The next steps will depend on whether you will use git and GitHub for versioning your project and whether or not you will work on your project as a solo scientist or work and collaborate with other scientists.