VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Why Mathematics? | Multi-Arm Multi-Stage Trials: Dropping Arms, Shared Controls and Efficient Comparisons

Why is mathematics important when several treatments can be evaluated against one control and weak options can stop early? Multi-arm multi-stage trials share control information and apply planned interim boundaries so resources move toward promising comparisons without losing error control.

Did You Know? Three separate 1:1 trials needing 100 participants per arm use 300 control participants. One four-arm trial with three experimental arms and one shared control uses 100 controls in the simplest equal-size illustration, reducing the total from 600 to 400.

Full chapter index

Chapters 1–7 · Understand the question
  1. The multi-arm question
  2. A shared control
  3. The simple efficiency calculation
  4. Why the arithmetic is only illustrative
  5. Stages
  6. An illustrative boundary set
  7. Three illustrative decisions
Chapters 8–14 · Reproduce the example
  1. Dropping is not proof of zero effect
  2. Familywise Type I error
  3. Dunnett correlation
  4. Strong error control
  5. Selecting a limited number
  6. Research implementation
  7. Outcome timing
Chapters 15–21 · Check assumptions
  1. Safety boundaries
  2. Changing standard of care
  3. Allocation ratios
  4. Estimation after selection
  5. Stagewise combination
  6. Missing and delayed data
  7. Simulation
Chapters 22–28 · Explore applications
  1. Expected sample size
  2. Education example
  3. Governance
  4. Diagnostics
  5. Validation plan
  6. Limits
  7. Communication
Chapters 29–42 · Study and verify
  1. Final decision
  2. A spreadsheet workflow
  3. A coding workflow
  4. Applications and careers
  5. A student investigation
  6. Common misconceptions
  7. Connection to recent mathematics articles
  8. Guidance for students and parents
  9. Practice questions
  10. Frequently asked questions
  11. A reporting checklist
  12. Correlation is an asset and a duty
  13. A final MAMS audit
  14. Useful next reading

CHAPTER 1 OF 42 · Understand the question

1. The multi-arm question

Back to contents

Several treatments, doses or programmes may be ready at once. Comparing each with a common control under one coordinated design can reduce duplication and answer more questions.

Contents · Next chapter

CHAPTER 2 OF 42 · Understand the question

2. A shared control

Back to contents

Participants randomised to control can contribute to several contemporaneous treatment comparisons. The correlations this creates are useful and must appear in multiplicity calculations.

Contents · Previous chapter · Next chapter

CHAPTER 3 OF 42 · Understand the question

3. The simple efficiency calculation

Back to contents

Three experimental groups of 100 each plus one shared control of 100 total 400. Three separate equal trials require 300 experimental and 300 control participants, totalling 600.

Contents · Previous chapter · Next chapter

CHAPTER 4 OF 42 · Understand the question

4. Why the arithmetic is only illustrative

Back to contents

Optimal allocation may put more participants in control, outcomes can be delayed, and eligibility may differ. The valid comparison uses control participants who are eligible and concurrent with the relevant arm.

Contents · Previous chapter · Next chapter

CHAPTER 5 OF 42 · Understand the question

5. Stages

Back to contents

At each planned interim analysis, every active comparison is assessed against a lack-of-benefit, efficacy or safety boundary. The next stage retains the arms allowed by the rule.

DesignExperimental participantsControl participantsTotal
Three separate 1:1 trials300300600
One four-arm trial300100400
Separate trials versus one shared control.

Contents · Previous chapter · Next chapter

CHAPTER 6 OF 42 · Understand the question

6. An illustrative boundary set

Back to contents

Suppose stage one drops an arm below z=0.5, continues values from 0.5 to 2.5 and permits early efficacy above 2.5. Actual boundaries require design-specific calibration.

Contents · Previous chapter · Next chapter

CHAPTER 7 OF 42 · Understand the question

7. Three illustrative decisions

Back to contents

Arm A at z=0.4 drops for lack of benefit, B at 1.6 continues, and C at 2.7 crosses the illustrative efficacy boundary.

Contents · Previous chapter · Next chapter

CHAPTER 8 OF 42 · Reproduce the example

8. Dropping is not proof of zero effect

Back to contents

The rule says the arm lacks enough promise for this design and remaining resources. It does not establish equivalence or rule out every worthwhile effect.

ArmZ statisticRule
A0.4Drop for lack of benefit
B1.6Continue
C2.7Cross early efficacy boundary
Illustrative interim decisions.

Contents · Previous chapter · Next chapter

CHAPTER 9 OF 42 · Reproduce the example

9. Familywise Type I error

Back to contents

With several null hypotheses and repeated looks, unadjusted 0.05 tests inflate the chance of at least one false positive. Boundaries must protect the chosen family.

Contents · Previous chapter · Next chapter

CHAPTER 10 OF 42 · Reproduce the example

10. Dunnett correlation

Back to contents

Comparisons sharing one control are positively correlated. Dunnett-type methods can use that correlation and be less conservative than treating tests as independent.

Contents · Previous chapter · Next chapter

CHAPTER 11 OF 42 · Reproduce the example

11. Strong error control

Back to contents

Control should hold across configurations where some treatments work and others do not, not only the global null where every arm is ineffective.

Contents · Previous chapter · Next chapter

CHAPTER 12 OF 42 · Reproduce the example

12. Selecting a limited number

Back to contents

A resource cap may allow only the best one or two arms to continue. The selection rule and final critical value must be prespecified and simulated.

Contents · Previous chapter · Next chapter

CHAPTER 13 OF 42 · Reproduce the example

13. Research implementation

Back to contents

The MAMS R package paper describes group-sequential multi-arm designs, treatment selection and conditional-error modifications. Read the Journal of Statistical Software paper.

Contents · Previous chapter · Next chapter

CHAPTER 14 OF 42 · Reproduce the example

14. Outcome timing

Back to contents

A short-term interim outcome can accelerate dropping, but its relationship to the definitive outcome must be credible. Otherwise a useful arm may be discarded.

Contents · Previous chapter · Next chapter

CHAPTER 15 OF 42 · Check assumptions

15. Safety boundaries

Back to contents

Shared efficacy infrastructure does not mean shared safety profiles. Each treatment needs appropriate exposure, monitoring and adverse-event interpretation.

Contents · Previous chapter · Next chapter

CHAPTER 16 OF 42 · Check assumptions

16. Changing standard of care

Back to contents

If control treatment evolves, comparisons across stages may no longer target the same effect. Versioning, concurrent comparison and sensitivity analysis become essential.

Contents · Previous chapter · Next chapter

CHAPTER 17 OF 42 · Check assumptions

17. Allocation ratios

Back to contents

Equal arm sizes are not always optimal. More control participants can improve several contrasts simultaneously, while too few on an experimental arm harms its precision.

Contents · Previous chapter · Next chapter

CHAPTER 18 OF 42 · Check assumptions

18. Estimation after selection

Back to contents

The surviving arm tends to look better because it was selected. Naive estimates and confidence intervals may be biased or have poor coverage.

Contents · Previous chapter · Next chapter

CHAPTER 19 OF 42 · Check assumptions

19. Stagewise combination

Back to contents

Combination tests or conditional-error methods can support valid modifications when their stagewise assumptions and hypotheses are preserved.

Contents · Previous chapter · Next chapter

CHAPTER 20 OF 42 · Check assumptions

20. Missing and delayed data

Back to contents

Every interim cutoff should list outcomes available, pending and missing. Operational decisions must not selectively wait for favourable late results.

Contents · Previous chapter · Next chapter

CHAPTER 21 OF 42 · Check assumptions

21. Simulation

Back to contents

Simulate all null and alternative configurations, recruitment, shared control, correlation, stopping, selection, missingness and final estimation.

Contents · Previous chapter · Next chapter

CHAPTER 22 OF 42 · Explore applications

22. Expected sample size

Back to contents

An effective design may keep the same maximum sample but use fewer participants on average by dropping weak arms. Show expected size by effect scenario.

Contents · Previous chapter · Next chapter

CHAPTER 23 OF 42 · Explore applications

23. Education example

Back to contents

A school network might compare three tutoring formats with usual support. A shared control saves pupils, but schools, terms and assessment timing must remain comparable.

Contents · Previous chapter · Next chapter

CHAPTER 24 OF 42 · Explore applications

24. Governance

Back to contents

An independent monitoring group should receive unblinded comparisons and implement decisions through a reproducible charter, limiting information released to sites.

Contents · Previous chapter · Next chapter

CHAPTER 25 OF 42 · Explore applications

25. Diagnostics

Back to contents

Report arm entry, information time, z paths, boundaries, control overlap, correlation, selection probability, familywise error, power and expected sample.

Contents · Previous chapter · Next chapter

CHAPTER 26 OF 42 · Explore applications

26. Validation plan

Back to contents

Reproduce 600 versus 400, simulate correlated z statistics and verify rejection under global null and mixed-effect scenarios.

Contents · Previous chapter · Next chapter

CHAPTER 27 OF 42 · Explore applications

27. Limits

Back to contents

MAMS designs do not make treatments interchangeable, eliminate multiplicity or guarantee faster answers. Shared control is valuable only when scientifically comparable.

Contents · Previous chapter · Next chapter

CHAPTER 28 OF 42 · Explore applications

28. Communication

Back to contents

Publish every prespecified and actual arm decision, including negative arms. Avoid presenting a selected winner as if it came from a single fixed comparison.

Contents · Previous chapter · Next chapter

CHAPTER 29 OF 42 · Study and verify

29. Final decision

Back to contents

Use MAMS when several mature questions share a credible control and common infrastructure. Complexity is justified only when efficiency and learning improve together.

Contents · Previous chapter · Next chapter

CHAPTER 30 OF 42 · Study and verify

30. A spreadsheet workflow

Back to contents

Track arm, stage, information fraction, estimate, SE, boundary, control window, decision and final claim in one auditable matrix.

Contents · Previous chapter · Next chapter

CHAPTER 31 OF 42 · Study and verify

31. A coding workflow

Back to contents

Use validated MAMS software and independent simulation. Test ties, arm drops, missing stages, correlation matrices and every mixed null configuration.

Contents · Previous chapter · Next chapter

CHAPTER 32 OF 42 · Study and verify

32. Applications and careers

Back to contents

Clinical trialists, agricultural researchers, policy evaluators and product teams use multi-arm designs to compare several options efficiently.

Contents · Previous chapter · Next chapter

CHAPTER 33 OF 42 · Study and verify

33. A student investigation

Back to contents

Simulate three treatments and one shared control. Compare separate trials, fixed multi-arm and two-stage MAMS designs across mixed effects.

Contents · Previous chapter · Next chapter

CHAPTER 34 OF 42 · Study and verify

34. Common misconceptions

Back to contents

A shared control is not historical control, dropping is not equivalence, the winning arm is selected, and per-comparison error is not familywise error.

Contents · Previous chapter · Next chapter

CHAPTER 35 OF 42 · Study and verify

35. Connection to recent mathematics articles

Back to contents

The alpha-spending guide covers repeated looks. The futility guide explains lack-of-benefit decisions.

Contents · Previous chapter · Next chapter

CHAPTER 36 OF 42 · Study and verify

36. Guidance for students and parents

Back to contents

Students should draw one control node connected to every active arm and label which controls are concurrent. Parents can ask whether school comparisons share the same term and eligibility.

Contents · Previous chapter · Next chapter

CHAPTER 37 OF 42 · Study and verify

37. Practice questions

Back to contents

  • Reproduce the sample saving.
  • Apply three boundaries.
  • Add an arm-selection cap.
  • Change the control standard.
  • Simulate familywise error.

Contents · Previous chapter · Next chapter

CHAPTER 38 OF 42 · Study and verify

38. Frequently asked questions

Back to contents

### Does every arm need its own control? A valid shared control can serve several comparisons.

### Is a dropped arm ineffective? Not proven.

### Can the best arm be selected? Yes, with a valid rule.

### Are ordinary intervals enough? Selection may require adjustment.

Contents · Previous chapter · Next chapter

CHAPTER 39 OF 42 · Study and verify

39. A reporting checklist

Back to contents

Report arms and hypotheses, shared-control eligibility, allocation, stages and boundaries, multiplicity, selection, interim cutoffs, simulations, all decisions and adjusted estimation.

Contents · Previous chapter · Next chapter

CHAPTER 40 OF 42 · Study and verify

40. Correlation is an asset and a duty

Back to contents

Shared controls reduce duplication because comparisons share information; the same correlation must appear in error control and uncertainty.

Contents · Previous chapter · Next chapter

CHAPTER 41 OF 42 · Study and verify

41. A final MAMS audit

Back to contents

Confirm every control participant belongs to the relevant comparison period, all stopping rules were followed and negative arms remain visible.

Contents · Previous chapter · Next chapter

CHAPTER 42 OF 42 · Study and verify

42. Useful next reading

Back to contents

Continue through the Mathematics Learning Hub. Recalculate the central worked example, identify the assumptions and explain which claim the result can and cannot support.

Contents · Previous chapter · Mathematics Learning Hub

Extended practice laboratory

Practice case 1: Count experimental arms

Setup: Start from the article’s multi-arm multi-stage design mechanism for case 1. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the estimand and design, verify the statistical identity, state one diagnostic, record units and compare one defensible alternative with clear reasoning. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 2: Define shared control

Setup: Start from the article’s multi-arm multi-stage design mechanism for case 2. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the estimand and design, verify the statistical identity, state one diagnostic, record units and compare one defensible alternative with clear reasoning. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 3: Set allocation ratio

Setup: Start from the article’s multi-arm multi-stage design mechanism for case 3. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the estimand and design, verify the statistical identity, state one diagnostic, record units and compare one defensible alternative with clear reasoning. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 4: Calculate total sample

Setup: Start from the article’s multi-arm multi-stage design mechanism for case 4. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the estimand and design, verify the statistical identity, state one diagnostic, record units and compare one defensible alternative with clear reasoning. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 5: Set stage-one boundary

Setup: Start from the article’s multi-arm multi-stage design mechanism for case 5. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the estimand and design, verify the statistical identity, state one diagnostic, record units and compare one defensible alternative with clear reasoning. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 6: Set final boundary

Setup: Start from the article’s multi-arm multi-stage design mechanism for case 6. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the estimand and design, verify the statistical identity, state one diagnostic, record units and compare one defensible alternative with clear reasoning. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 7: Drop futile arm

Setup: Start from the article’s multi-arm multi-stage design mechanism for case 7. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the estimand and design, verify the statistical identity, state one diagnostic, record units and compare one defensible alternative with clear reasoning. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 8: Continue promising arm

Setup: Start from the article’s multi-arm multi-stage design mechanism for case 8. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the estimand and design, verify the statistical identity, state one diagnostic, record units and compare one defensible alternative with clear reasoning. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 9: Stop successful arm

Setup: Start from the article’s multi-arm multi-stage design mechanism for case 9. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the estimand and design, verify the statistical identity, state one diagnostic, record units and compare one defensible alternative with clear reasoning. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 10: Protect familywise error

Setup: Start from the article’s multi-arm multi-stage design mechanism for case 10. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the estimand and design, verify the statistical identity, state one diagnostic, record units and compare one defensible alternative with clear reasoning. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 11: Use Dunnett correlation

Setup: Start from the article’s multi-arm multi-stage design mechanism for case 11. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the estimand and design, verify the statistical identity, state one diagnostic, record units and compare one defensible alternative with clear reasoning. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 12: Add arm selection

Setup: Start from the article’s multi-arm multi-stage design mechanism for case 12. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the estimand and design, verify the statistical identity, state one diagnostic, record units and compare one defensible alternative with clear reasoning. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 13: Cap survivors

Setup: Start from the article’s multi-arm multi-stage design mechanism for case 13. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the estimand and design, verify the statistical identity, state one diagnostic, record units and compare one defensible alternative with clear reasoning. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 14: Add outcome delay

Setup: Start from the article’s multi-arm multi-stage design mechanism for case 14. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the estimand and design, verify the statistical identity, state one diagnostic, record units and compare one defensible alternative with clear reasoning. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 15: Add safety stop

Setup: Start from the article’s multi-arm multi-stage design mechanism for case 15. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the estimand and design, verify the statistical identity, state one diagnostic, record units and compare one defensible alternative with clear reasoning. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 16: Change control standard

Setup: Start from the article’s multi-arm multi-stage design mechanism for case 16. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the estimand and design, verify the statistical identity, state one diagnostic, record units and compare one defensible alternative with clear reasoning. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 17: Calculate concurrent control

Setup: Start from the article’s multi-arm multi-stage design mechanism for case 17. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the estimand and design, verify the statistical identity, state one diagnostic, record units and compare one defensible alternative with clear reasoning. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 18: Estimate treatment contrast

Setup: Start from the article’s multi-arm multi-stage design mechanism for case 18. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the estimand and design, verify the statistical identity, state one diagnostic, record units and compare one defensible alternative with clear reasoning. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 19: Adjust confidence interval

Setup: Start from the article’s multi-arm multi-stage design mechanism for case 19. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the estimand and design, verify the statistical identity, state one diagnostic, record units and compare one defensible alternative with clear reasoning. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 20: Add missingness

Setup: Start from the article’s multi-arm multi-stage design mechanism for case 20. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the estimand and design, verify the statistical identity, state one diagnostic, record units and compare one defensible alternative with clear reasoning. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 21: Simulate global null

Setup: Start from the article’s multi-arm multi-stage design mechanism for case 21. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the estimand and design, verify the statistical identity, state one diagnostic, record units and compare one defensible alternative with clear reasoning. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 22: Simulate mixed effects

Setup: Start from the article’s multi-arm multi-stage design mechanism for case 22. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the estimand and design, verify the statistical identity, state one diagnostic, record units and compare one defensible alternative with clear reasoning. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 23: Audit arm decisions

Setup: Start from the article’s multi-arm multi-stage design mechanism for case 23. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the estimand and design, verify the statistical identity, state one diagnostic, record units and compare one defensible alternative with clear reasoning. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 24: Name limits

Setup: Start from the article’s multi-arm multi-stage design mechanism for case 24. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the estimand and design, verify the statistical identity, state one diagnostic, record units and compare one defensible alternative with clear reasoning. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.

Practice case 25: Write conclusion

Setup: Start from the article’s multi-arm multi-stage design mechanism for case 25. Task: Change the named quantity, recompute the dependent result and compare with the original.

Check: Preserve the estimand and design, verify the statistical identity, state one diagnostic, record units and compare one defensible alternative with clear reasoning. Show the arithmetic, name the response and predictor units, and separate the numerical result from the claim it supports. Then vary one defensible assumption, calculate again and explain whether the conclusion changed because of the data, the fitted model or the validation purpose. Finish with one compact table or graph that could reveal a failure hidden by the summary.