User Guide for the RMSTpowerBoost Shiny Application

Introduction

This vignette documents the RMSTpowerBoost Shiny application. The app supports analyses based on uploaded pilot data or data generated inside the app.

Workflow Overview

The sidebar holds the setup and analysis controls, and the main panel shows the resulting outputs.

  1. Step 1. Data Source: choose whether to generate a dataset inside the app or upload pilot data from disk.
  2. Step 2. Generation or Cleaning: generated-data users define a simulation recipe; upload users resolve missingness through dropping and/or MICE imputation.
  3. Step 3. Model and Mapping: select the RMST model and map the required columns.
  4. Step 4. Analysis: choose the target quantity, calculation method, and tuning parameters, then run the analysis.
  5. Review outputs: inspect the data, diagnostics, KM plot, analysis tables, and run log.
  6. Export results: after a successful run, download an HTML or PDF report. Generated datasets can also be exported from the Data tab.

Main Panel Tabs

The main panel contains the tabs listed below.

Pipeline

This tab summarizes the current app state and is the landing page when the app opens or resets.

Data

Summary

KM Plot

This tab displays exploratory Kaplan-Meier diagnostics derived from the current dataset.

Analysis

This is the primary results tab. It includes:

For power calculations, the plot shows the estimated power at each requested sample size. For sample-size searches, it shows the search path together with the target-power reference line and the selected sample size.

Run Log

This tab combines the data-cleaning log and the analysis log. It is the first place to inspect when validation fails, model fitting errors occur, or an imputation step leaves unresolved missingness.

About

The About tab gives a short overview of the app and the package.


Export Behavior

After a successful analysis run, the sidebar reveals two report downloads:

If the local environment does not have a full PDF toolchain available, the app falls back to a diagnostic PDF rather than failing silently. HTML export is also available directly from the same download row.