In gsDesign2, the failure rate and dropout rate are consolidated into a single table named fail_rate. However, in simtrial::sim_pw_surv, users are asked to input the failure rate and dropout rate separately, as shown below:
It's important to mention that the table fail_rate and dropout_rate mentioned earlier includes a period column, which is not present in gsDesign2. To link gsDesign2 to simtrial, we utilize a function called to_sim_pw_surv.
Decision: we will keep the API of sim_pw_surv as it is, as it provides more flexibility to allow the change points of dropout rate differs from the fail rate.
In gsDesign2, the failure rate and dropout rate are consolidated into a single table named
fail_rate
. However, insimtrial::sim_pw_surv
, users are asked to input the failure rate and dropout rate separately, as shown below:It's important to mention that the table
fail_rate
anddropout_rate
mentioned earlier includes aperiod
column, which is not present in gsDesign2. To link gsDesign2 to simtrial, we utilize a function calledto_sim_pw_surv
.I am considering whether we should align the API of sim_pw_surv with that of gsDesign2, such as
In this way, we could implement
to_sim_pw_surv
inside ofsim_pw_surv
, i.e.,