Why Simulate the Joint Procedure?
A multiple-endpoint group sequential design makes decisions from a collection of statistics observed repeatedly over time. The statistics are correlated across endpoints, and statistics from successive looks on the same endpoint are also correlated. Moreover, a rejection can change later decisions under a prespecified multiplicity rule. Checking one endpoint at a time, or checking only a single look, can therefore miss errors in the implemented procedure.
Joint simulation provides an empirical check of the complete decision rule: generate all endpoint statistics at all planned looks, apply the rule in its actual order, and record whether any true null hypothesis is rejected. The resulting estimate is a diagnostic, not a replacement for the design’s theoretical justification. In particular, a simulation under the global null alone does not establish strong familywise error control.
Joint Model and Target Quantity
Suppose there are \(m\) endpoints and \(K\) planned looks. Let \(t_k\) be the information fraction at look \(k\), with \(0<t_1<\cdots<t_K=1\). For clarity, assume that all endpoints are assessed at these same information fractions. Write \(R\) for the prespecified \(m\times m\) correlation matrix between endpoint score processes. It must be positive semidefinite and have diagonal entries equal to 1.
This covariance gives unit variance for each statistic and the usual canonical correlation across looks. It can be generated by accumulating multivariate normal increments: for interval \((t_{k-1},t_k]\), generate an increment with covariance \((t_k-t_{k-1})R\), add it to the cumulative process, then divide each endpoint’s cumulative score by \(\sqrt{t_k}\). Under an alternative, the score increment for endpoint \(j\) has mean \(\theta_j(t_k-t_{k-1})\). This construction retains dependence across both endpoints and looks.
Let \(T\) denote the set of true null hypotheses in a configuration. If \(D_j\) is 1 when the full procedure rejects endpoint \(j\), and 0 otherwise, the familywise error indicator for one simulated trial is \(\mathbf{1}\{\sum_{j\in T}D_j>0\}\). The familywise error rate is the probability of that event. Strong control requires this probability to be no greater than the design’s target \(\alpha\) for every configuration of true and false null hypotheses, under the assumptions of the procedure.
Simulation Algorithm and Monte Carlo Uncertainty
The simulation must encode the actual rule, not just the nominal boundaries in isolation. That includes which statistics are available at each look, the endpoint-specific local boundaries, any permitted alpha propagation after rejection, and the stopping rule. These features should agree with the prespecified design. The simulated trial stops when the rule says it stops; later statistics must not be used to make decisions after that point.
Specify which hypotheses are true and choose effect values for the false nulls. Set the information fractions, endpoint correlation matrix, and all design decisions before running the simulations.
Generate the joint score process through the planned looks, with zero drift for true nulls and the specified drift for false nulls.
Give the generated statistics to the implemented rule in chronological order. Record each rejection and follow the rule’s stopping and any permitted transition instructions.
Set the replicate’s familywise error indicator to 1 if any true null was rejected; otherwise set it to 0. Repeat independently for the chosen number of trials.
Estimate the error rate, quantify Monte Carlo uncertainty, and repeat across relevant null configurations and model checks.
If \(B\) independent trials are simulated and \(X\) have at least one rejection of a true null, the Monte Carlo estimate is \(\hat{q}=X/B\). Its estimated Monte Carlo standard error is \(\sqrt{\hat{q}(1-\hat{q})/B}\). This standard error describes simulation noise, not uncertainty in the clinical treatment effect. A rough 95% Monte Carlo interval is \(\hat{q}\pm1.96\sqrt{\hat{q}(1-\hat{q})/B}\); for rates near 0 or 1, a binomial interval such as Wilson’s is preferable. When judging a small excess over \(\alpha\), increase \(B\): a point estimate alone cannot distinguish a small design defect from ordinary simulation variation.
Worked Examples
Worked Example: Estimating Error Under the Global Null
Consider a hypothetical design with three endpoints and three looks at information fractions 0.40, 0.70, and 1.00. Suppose the planned endpoint correlations and the full sequential multiplicity rule are supplied to the simulation. Under the global null, all three \(\theta_j\) values are zero. In \(B=100{,}000\) simulated trials, suppose at least one endpoint is rejected in \(X=4{,}726\) trials.
The estimated familywise error rate is \(\hat{q}=4{,}726/100{,}000=0.04726\), or 4.726%. The estimated Monte Carlo standard error is \(\sqrt{0.04726(1-0.04726)/100{,}000}=0.000671\), which is 0.0671 percentage points. A rough 95% interval is \(0.04726\pm1.96(0.000671)=(0.04595,0.04857)\).
For a hypothetical target \(\alpha=0.05\), this run gives no indication that the global-null error rate exceeds 5%; the interval’s upper end is about 4.857%. This is evidence about this simulated configuration and model, not proof of control in every configuration.
Worked Example: Checking a Partial-Null Configuration
Now keep the same hypothetical design, but let endpoints 1 and 2 be true nulls and endpoint 3 be false, with standardized effect \(\theta_3=0.25\). Simulate \(100{,}000\) trials. Suppose endpoint 1 or 2, or both, is rejected in 5,260 trials. Rejection of endpoint 3 does not count as a familywise error in this configuration.
The estimate is \(\hat{q}=5{,}260/100{,}000=0.05260\), or 5.260%. Its Monte Carlo standard error is \(\sqrt{0.05260(1-0.05260)/100{,}000}=0.000706\), or 0.0706 percentage points. The rough 95% interval is \(0.05260\pm1.96(0.000706)=(0.05122,0.05398)\).
For a 5% target, this result is a warning: even the interval’s lower end is above 5%. It warrants checking the rule and simulating additional relevant configurations. In particular, inspect whether a rejection of endpoint 3 changes later decisions exactly as specified, and whether that change is permitted by the design’s multiplicity procedure. A single partial-null result does not identify the cause, but checking only the global null would have missed this signal.
Justifying the Joint Covariance
The covariance used in the simulation follows directly from the accumulated-score construction. Let \(W_j(t)\) be endpoint \(j\)’s cumulative score noise by information time \(t\), with \(\operatorname{Cov}(W_a(s),W_b(t))=R_{ab}\min(s,t)\). The standardized noise at time \(t\) is \(W_j(t)/\sqrt{t}\). Therefore, for \(s\leq t\), \[ \operatorname{Cov}\left(\frac{W_a(s)}{\sqrt{s}},\frac{W_b(t)}{\sqrt{t}}\right) =\frac{R_{ab}s}{\sqrt{s}\sqrt{t}} =R_{ab}\sqrt{\frac{s}{t}}. \] With \(s=t_k\) and \(t=t_l\), this is the stated covariance formula. In particular, for the same endpoint, \(a=b\), the correlation between looks is \(\sqrt{t_k/t_l}\) when \(t_k\leq t_l\). Treating looks as independent would contradict this derivation and could materially change the simulated stopping and rejection pattern.
Worked Example: Diagnosing a Dependence-Model Error
For a hypothetical two-endpoint design, suppose the intended endpoint correlation is \(R_{12}=0.60\), and statistics are assessed at information fractions 0.50 and 1.00. Under the joint canonical model, the correlation between endpoint 1 at the first look and endpoint 2 at the final look is \(0.60\sqrt{0.50/1.00}=0.4243\). The same-endpoint correlation between the first and final looks is \(\sqrt{0.50}=0.7071\).
As a model diagnostic, generate \(50{,}000\) joint-null replicates and calculate the empirical correlation of the endpoint statistics at the first look. Suppose it is 0.603. This is close to the intended 0.60 and is plausible simulation variation. Now suppose an implementation mistakenly sets the endpoint correlation to zero. In a separate hypothetical run of \(50{,}000\) trials, it estimates familywise error as 4.78%, while the intended-correlation run estimates 5.31%.
The two rates are not interchangeable estimates of one design: they come from different joint models. The discrepancy signals that the dependence assumption matters for this rule and that the zero-correlation implementation is not a valid check of the intended design. Re-run after verifying how \(R\) is entered, confirm that it is a valid correlation matrix, and compare empirical correlations at every pair of endpoints and looks with their specified values.
What a Simulation Can and Cannot Diagnose
A useful validation checks more than the final error-rate estimate. Inspect marginal means and variances under the null, empirical correlations across endpoints and looks, the number of trials stopping at each look, and the frequency of each rejection sequence. Compare those summaries with their expected behavior under the model. Also test the decision code on deliberately simple inputs: for example, statistics well below every boundary should produce no efficacy rejection, while a statistic beyond a valid active boundary should trigger the prescribed decision. These checks can reveal indexing errors, an incorrectly applied look-specific boundary, a sign error, or a rejected endpoint being counted twice.
Strong error control concerns all configurations of true null hypotheses, not only the case where every endpoint is null. Simulate the global null and selected partial-null configurations, including plausible effect sizes on the false nulls that can alter the procedure’s later path. If the number of endpoints is small, configurations can often be enumerated; otherwise, use a reasoned selection of configurations and effect values. Simulation over a finite set of configurations is still not a mathematical proof for all possible configurations and alternatives.
Joint simulation is most useful as a complement to a theoretical argument or a validated design calculation. A valid closed-testing construction or other established procedure supplies the control justification under its assumptions; simulation can uncover a mismatch between that rule and its software implementation, or show that an assumed dependence model has not been represented as intended. By contrast, simulating separate endpoints independently, using only marginal nominal levels, or checking only the final look discards features that may determine the familywise error rate.
The result is also conditional on the simulation model. A multivariate normal model may be a reasonable canonical approximation for the planned statistics, but it does not automatically represent every feature of a real trial. Unequal information timing, non-normal statistics, changing endpoint availability, or a dependence structure that differs from the assumed one may require a more suitable data-generating model. State the model, information schedule, correlation assumptions, alternative configurations, random-number seed, number of replicates, and exact decision rule so another analyst can reproduce the check.
Common Mistake
- Wrong reasoning: “The global-null simulation estimated 4.7%, below 5%, so strong familywise error control has been verified.”
- Correction: The global-null result checks only the configuration in which every hypothesis is true. Strong control also concerns configurations with some false nulls, whose statistics can affect the path of a multiplicity procedure. Simulate relevant partial-null configurations and rely on the procedure’s theoretical justification for coverage beyond the configurations checked.
- Another warning: A simulated estimate of 5.1% is not automatically a demonstrated failure if its Monte Carlo uncertainty is large. Report the uncertainty, increase the number of replicates when needed, and investigate the implementation rather than making a conclusion from the rounded estimate alone.
Check Your Understanding
Answer each question, then compare with the brief solutions.
- Why does a global-null simulation alone not establish strong familywise error control?
- At information fractions 0.36 and 1.00, what is the canonical correlation between two looks for the same endpoint?
- In \(20{,}000\) simulated trials, 1,020 have at least one true null rejected. Calculate the estimated familywise error and its approximate Monte Carlo standard error.
- Why must the simulation preserve dependence across endpoints as well as across looks?
- Name two implementation diagnostics other than the overall familywise error estimate.
Solutions: (1) It evaluates only the configuration in which all hypotheses are true; false endpoints can affect later decisions, so partial-null configurations also matter. (2) The correlation is \(\sqrt{0.36/1.00}=0.60\). (3) The estimate is \(1{,}020/20{,}000=0.0510\). Its approximate standard error is \(\sqrt{0.0510(0.9490)/20{,}000}=0.00156\), or 0.156 percentage points. (4) Both forms of dependence affect the joint paths of statistics and therefore the chance that the full rule rejects a true null. (5) Examples include checking empirical means, variances and correlations; look-specific stopping frequencies; and rejection-sequence frequencies or boundary decisions on test inputs.