Skip to content

Project Planning

yilong zhang edited this page Jun 7, 2023 · 13 revisions

Propose to split the work into four streams. For each stream, we need a direct response person to ensure the work is delivered as planned with agreed priority.

  • package development: the goal is to ensure R packages API are user-friendly, and results are accurate.
  • computational efficiency: the goal is to ensure a more efficient version of implementation with accurate results.
  • shiny: the goal is to use API to build Shiny app for general user.
  • manuscript: the goal is to provide clear documentation.

Package development

gsDesign2 (Yujie -> Maintainer)

  • software best practice (Yilong).
  • documentation of info_scale (Yujie).
  • examples of updated design (Yujie).
  • add gs_power_ve and gs_design_ve (Keaven).
  • add as_rtf and as_flextable (SP?).
  • implement stratified sample size method from Bernstein and Lagakos (?).

simtrial (Nan -> Maintainer)

  • add RMST.

Grammar of design/simulations (De-prioritize)

Computational efficiency (Nan drive with contractor)

  • simtrial -> data.table (?).
  • gsDesign2::gs_bound_spending -> C++ (SP?).
  • gsDesign2::expected_event -> data.table (?).

Shiny

  • gsDesign2 Shiny (Greg/Bing).

Manuscript

  • gsDesign Shiny Book (Keaven/Nan).
  • gsDesign2 under NPH (Yujie/Yilong).
Clone this wiki locally