You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: DESCRIPTION
+12-11Lines changed: 12 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -1,25 +1,25 @@
1
1
Package: BayesianPlatformDesignTimeTrend
2
-
Title: Simulate and analyse Bayesian Platform Trial with time trend
3
-
Version: 1.0.0
2
+
Title: Simulate and Analyse Bayesian Platform Trial with Time Trend
3
+
Version: 1.1.2
4
4
Author: Ziyan Wang [aut, cre]
5
5
Maintainer: Ziyan Wang <zw7g20@soton.ac.uk>
6
6
Authors@R:
7
7
person(given = "Ziyan",
8
8
family = "Wang",
9
9
role = c("aut", "cre"),
10
10
email = "zw7g20@soton.ac.uk")
11
-
Description: Simulating the multi-arm multi-stage or platform trial with Bayesian approach using the 'rstan' package, which provides the R interface for to the Stan.
12
-
The randomisation approach in this package are fix ratio and Bayesian adaptive randomisation.
13
-
In addition, the time trend problem of platform trial can be studied in this package.
14
-
There is a demo for multi-arm multi-stage trial with two different null scenario and a demo for Bayesian trial cutoff screening.
11
+
Description: Simulating the sequential multi-arm multi-stage or platform trial with Bayesian approach using the 'rstan' package, which provides the R interface for the Stan.
12
+
This package supports fixed ratio and Bayesian adaptive randomization approaches for randomization.
13
+
Additionally, it allows for the study of time trend problems in platform trials.
14
+
There are demos available for a multi-arm multi-stage trial with two different null scenarios, as well as for Bayesian trial cutoff screening.
15
15
The Bayesian adaptive randomisation approaches are described in:
16
16
Trippa et al. (2012) <doi:10.1200/JCO.2011.39.8420> and
17
-
Wathen et al. (2017) <doi:10.1177/1740774517692302>
18
-
The randomisation algorithm is described in
19
-
Zhao W <doi:10.1016/j.cct.2015.06.008>
17
+
Wathen et al. (2017) <doi:10.1177/1740774517692302>.
18
+
The randomisation algorithm is described in:
19
+
Zhao W <doi:10.1016/j.cct.2015.06.008>.
20
20
The analysis methods of time trend effect in platform trial are described in:
21
21
Saville et al. (2022) <doi:10.1177/17407745221112013> and
22
-
Bofill Roig et al. (2022) <doi:10.1186/s12874-022-01683-w>
22
+
Bofill Roig et al. (2022) <doi:10.1186/s12874-022-01683-w>.
* Added a `NEWS.md` file to track changes to the package.
1
+
# Jun 25, 2023, BayesianPlatformDesignTimeTrend version 1.1.2
2
+
This release fix two bugs.
3
+
4
+
- I fixed the bug in function `GP.optim` where the formula of information weighed randomisation is wrong.
5
+
- I fixed the bug in function `demo_Cutoffscreening` where the nextcutoff vector for sample may have only one element. This will lead to the error in function `sample` when you only want to sample one value greater than 1. The argument 'ntrials' in each example should be large (> 100) instead 2 to make the example more like an actual simulation example. I use ntrials = 2 in the example to speed up the check process.
6
+
7
+
# Jun 11, 2023, BayesianPlatformDesignTimeTrend version 1.1.1
8
+
This release fix one bug reported by the cran team.
9
+
10
+
- I fixed the bug in function `GP.optim` where the nextcutoff vector for sample may have only one element. This will lead to the error in function `sample` when you only want to sample one value greater than 1.
11
+
- The argument 'ntrials' in each example should be large (> 100) instead 2 to make the example more like an actual simulation example. I use ntrials = 2 in the example to speed up the check process.
12
+
13
+
# May 2, 2023, BayesianPlatformDesignTimeTrend version 1.1.0
14
+
This release implements additional method of cutoff screening using Bayesian optimization.
15
+
16
+
## New feature
17
+
- Add a new Demo function called `demo_Cutoffscreening_GP`. The function indicates how to use Gaussian process-based Bayesian optimisation algorithm to calibrate the critical value for stopping boundary under the null scenario to control the Type I error rate or FWER before trial simulation.
18
+
19
+
- Add a function `GP_optim` which returns a cutoff value for the next evaluation during the cutoff screening process. The function is used in demo `demo_Cutoffscreening_GP`.
20
+
21
+
## Bugs
22
+
- I found that the output data matrix can not be generated when there are four arm, the 'variable.inf' = "Mixeffect" and 'reg.inf' is "main"/"main + stage_continuous"/"main * stage_discrete".
23
+
It only work for 'variable.inf'="Mixeffect" and 'reg.inf = main + stage_discrete'. The reason why this happen is that the length of stats6 and stats7 variable are not generated correctly at stage 1 since the fixed effect model is used for 'variable.inf'="Mixeffect" at stage 1 to speed up the simulation.
24
+
25
+
## Debug
26
+
- I add one ifelse command to enforce the generation of stats6 and stats7 when 'variable.inf'="Mixeffect". It does not depend on the value of 'reg.inf' now.
27
+
28
+
# May 1, 2023, BayesianPlatformDesignTimeTrend version 1.0.1
29
+
## Major changes
30
+
- I fixed a bug where the fix ratio allocation method code is not suitable for the multi-arm trial
# Apr 25, 2023, BayesianPlatformDesignTimeTrend version 1.0.1
36
+
## Major changes
37
+
- I added a check command for max.ar which is the upper boundary for randomisation ratio for each arm. The command is added in the MainFunction.R. Details are shown below.
38
+
- #-max.ar check
39
+
if (1 - max.ar > 1/K){
40
+
stop("Error: The lower allocation ratio should be at least 1/K. Please check the number of arm at the beginning and the max.ar")
41
+
}
42
+
43
+
- Another change is the randomisation ratio adjustment in the Simulation_AdaptiveRandomisationmethodRatioCalc.R.
44
+
45
+
- I modified the randomisation ratio adjustment command for Thall's approach.
46
+
47
+
- ##----Original code------ (This code only protects the control arm's allocation ratio)
0 commit comments