@@ -16,9 +16,9 @@ knitr::opts_chunk$set(
1616)
1717```
1818
19- # Introduction
19+ ## Introduction
2020
21- ** RandomForge — An Open Project for Clinical Trial Randomization in R**
21+ ** randomforge — An Open Project for Clinical Trial Randomization in R**
2222
2323` randomforge ` is a newly started, open-source project on GitHub that aims to
2424provide a clean and transparent implementation of clinical trial randomization
@@ -38,7 +38,7 @@ This vignette explains how to:
38383 . Use GitHub effectively even if you are new to it
3939
4040
41- # 1. Installing randomforge and running a simple randomization
41+ ## Installing randomforge and running a simple randomization
4242
4343At this stage, the package is not yet on CRAN.
4444You can install the development version directly from GitHub:
@@ -78,8 +78,7 @@ blockSizes <- getBlockSizes(config$treatmentArmIds, 8)
7878
7979# Create a permuted block randomization method
8080randomMethodPBR <- getRandomMethodPBR(
81- blockSizes = blockSizes,
82- fixedBlockDesignEnabled = FALSE
81+ blockSizes = blockSizes
8382)
8483
8584# Create a random allocation value service
@@ -88,12 +87,12 @@ ravService$createNewRandomAllocationValues(config)
8887
8988# Create a few randomization results
9089resultList <- lapply(1:8, function(i) {
91- getNextRandomResult(
90+ suppressMessages( getNextRandomResult(
9291 randomDataBase = randomDataBase,
9392 randomProject = randomProject,
9493 randomMethod = randomMethodPBR,
9594 randomAllocationValueService = ravService
96- )
95+ ))
9796})
9897
9998# Convert results to a data frame
@@ -102,7 +101,7 @@ randomDataBase |>
102101 knitr::kable()
103102```
104103
105- # 2. How to contribute to randomforge
104+ ## How to contribute to randomforge
106105
107106Contributions of all kinds are welcome:
108107
@@ -118,7 +117,7 @@ get involved.
118117We are happy to support new contributors.
119118
120119
121- # 3. Option A: Get invited as a direct contributor
120+ ### Option A: Get invited as a direct contributor
122121
123122If you prefer not to deal with forks or pull requests, you can simply request
124123to be added as a contributor to the GitHub repository.
@@ -137,24 +136,24 @@ Once added, you will be able to push branches and open pull requests directly
137136in the main repository.
138137
139138
140- # 4. Option B: Contribute via Fork (recommended for most users)
139+ ### Option B: Contribute via Fork (recommended for most users)
141140
142141If you are not familiar with GitHub contribution workflows, here is a simple
143142step-by-step guide.
144143
145- ## Step 1 — Create a GitHub account
144+ #### Step 1 — Create a GitHub account
146145If you do not already have one, register at
147146https://github.com
148147
149- ## Step 2 — Open the randomforge repository
148+ #### Step 2 — Open the randomforge repository
150149Navigate to:
151150https://github.com/RCONIS/randomforge
152151
153- ## Step 3 — Click “Fork”
152+ #### Step 3 — Click “Fork”
154153The button is in the upper-right corner.
155154This creates * your own copy* of the repository under your GitHub account.
156155
157- ## Step 4 — Clone your fork to your local machine
156+ #### Step 4 — Clone your fork to your local machine
158157
159158``` bash
160159git clone https://github.com/YOUR_USERNAME/randomforge.git
@@ -166,29 +165,29 @@ Then:
166165cd randomforge
167166```
168167
169- ## Step 5 — Create a new branch for your change
168+ #### Step 5 — Create a new branch for your change
170169
171170``` bash
172171git checkout -b my-feature-branch
173172```
174173
175- ## Step 6 — Make your changes locally
174+ #### Step 6 — Make your changes locally
176175Edit R files, documentation, tests, examples, or vignettes.
177176
178- ## Step 7 — Commit your changes
177+ #### Step 7 — Commit your changes
179178
180179``` bash
181180git add .
182181git commit -m " Add new feature / fix / improvement"
183182```
184183
185- ## Step 8 — Push your branch to your fork
184+ #### Step 8 — Push your branch to your fork
186185
187186``` bash
188187git push origin my-feature-branch
189188```
190189
191- ## Step 9 — Open a Pull Request
190+ #### Step 9 — Open a Pull Request
192191Go back to your fork on GitHub and click:
193192
194193** “Compare & pull request”**
@@ -202,7 +201,7 @@ In the Pull Request description, please provide:
202201We will review all contributions as soon as possible.
203202
204203
205- # 5. Getting help
204+ ## Getting help
206205
207206If you get stuck at any point — GitHub workflow, code questions, architecture
208207discussion — feel free to:
@@ -214,8 +213,8 @@ All questions are welcome, especially from newcomers.
214213We want to make contributing as easy and friendly as possible.
215214
216215
217- # 6. Thank you
216+ ## Thank you
218217
219- We appreciate your interest in contributing to the RandomForge project.
218+ We appreciate your interest in contributing to the * randomforge * project.
220219Your ideas and contributions help shape a more open, transparent, and
221220community-driven future for clinical trial randomization in R.
0 commit comments