Choose your reading route
eduKateSG · Why Mathematics? · Survival Quantile Regression for Reliability: Lifetime Percentiles, Censoring, Covariate Effects and Time-Scale Decisions
Start with the question, audit the worked example, or jump to the assumptions and practice. Every chapter stays open for uninterrupted reading.
Understand the question
Define the quantity and follow the mechanism.Route 2 · Chapters 6–10
Reproduce the example
Audit the numbers one step at a time.Route 3 · Chapters 11–15
Check assumptions
See where design and calibration matter.Route 4 · Chapters 16–20
Explore applications
Connect the method to a concrete investigation.Route 5 · Chapters 21–25
Study and verify
Practise, inspect failure cases and read further.
Full chapter index · Practice and checking · Mathematics Learning Hub
Why mathematics is important becomes clear when engineers care about a lifetime percentile rather than an average or hazard ratio. Survival quantile regression models how a chosen conditional percentile of lifetime changes with load, design or environment while accounting for censoring. It can describe early-failure, median and long-life behaviour separately.
This guide develops conditional quantiles, check loss, censoring adjustments, percentile-specific coefficients, curve crossing and validation. Quantile models speak directly in time units, but high percentiles require enough follow-up and low percentiles require enough failures. A fitted percentile is a population statement, not a guaranteed replacement date for one component.
Full chapter index
Chapters 1–5 · Understand the question
Chapters 6–10 · Reproduce the example
Chapters 11–15 · Check assumptions
Chapters 16–20 · Explore applications
Chapters 21–25 · Study and verify
Different decisions target early failures, median life or long-life performance. The 10th percentile can guide conservative warranty discussion. This is the central mathematical mechanism in why model lifetime percentiles. Write the quantities and assumptions before using software, then reproduce the calculation or geometric argument in a small example. A mean can hide tail behaviour. Choose the percentile before analysis. The useful habit is to keep the physical question, the probability model and the numerical method in separate columns so that a correct computation is not mistaken for complete evidence.
Did You Know? A result can be numerically stable and still answer the wrong question if the failure event, denominator or transformation changes. Test one nearby case and predict the direction of change before recalculating. Save inputs, intermediate values and units so a second reader can audit the path.
For practice, turn the example into a sensitivity check. Change one defensible input while holding the others fixed, compare the new result with the original and explain why it moved. Then construct a counterexample in which the shortcut fails. End with two sentences: what the mathematics supports, and what remains uncertain.
Start with the operational question behind conditional quantile definition. Q_T(tau|x) is the time by which proportion tau of comparable lifetimes have ended under the conditional distribution. In the illustrative case, Median life uses tau=0.5. Draw the relevant graph, density, boundary or timeline before calculating; the picture should use the same variables and sign convention as the equations. Survival probability notation reverses the tail perspective. State failure-quantile convention.
A student should be able to rebuild the result without hidden settings. Record the sampling rule or optimisation criterion, the exact failure definition, and the evidence used for every distribution or parameter. Compare a transparent baseline with the advanced method. If they disagree, investigate the mechanism before deciding which answer is more credible.
This chapter belongs to a larger decision, so translate the number carefully. State one action the evidence permits and one action it does not. A parent or educator can ask which school ideas are doing the work: algebra organises relationships, probability represents uncertainty, calculus describes local change, and computing repeats the documented rules at scale.
Treat time-scale interpretation as a model-checking problem rather than a vocabulary exercise. A coefficient can represent a change in a lifetime percentile on an additive or transformed time scale. A design indicator may add 120 hours to the fitted median. Recompute the example from the raw values and label every unit. Interpretation depends on the link and transformation. Translate back to original units.
The strongest check uses evidence the model did not choose for itself. Hold out later observations, an independent simulation set or a known-answer benchmark. Report errors where decisions are sensitive, especially near the failure boundary, instead of relying on one global accuracy score. A method that performs well on easy safe cases can still fail at the rare cases that motivated the analysis.
Now change one assumption and make a directional prediction before running the calculation. If the result moves the opposite way, inspect the sign convention, transformation, density ratio or constraint. This prediction-first routine develops transferable problem-solving skills because it connects symbolic work to a testable expectation.
The mathematics of check loss without censoring becomes useful only when its mechanism is explicit. Ordinary quantile regression minimises asymmetric absolute loss rho_tau(u). Consider the worked illustration: Positive and negative residuals receive weights determined by tau. Preserve the original inputs, calculate step by step and compare with a second method whenever an analytic or high-budget reference exists. It is not least squares. Plot the loss shape.
There are three uncertainties to keep apart. Sampling or numerical uncertainty comes from finite computation. Parameter uncertainty comes from estimating inputs. Model-form uncertainty comes from simplified physics, distributions or dependence. Reducing the first does not automatically reduce the other two. A credible report names all three and shows which one drives the decision.
For a practical investigation, create a small reproducible notebook or spreadsheet with a frozen data sheet, formula sheet, diagnostics sheet and decision note. Another student should be able to change one input and obtain the same update without guessing what the model meant.
Primary source: https://doi.org/10.1198/016214503000000954. Read it for the method and its assumptions; do not transfer its performance claims automatically to another model.
Use why censoring complicates quantiles to practise sensitivity analysis. A censored unit reveals only that lifetime exceeds its observed time. A unit operating at cutoff may lie above several quantiles. Before accepting the result, identify the quantity that would change the conclusion most. Treating censoring time as failure biases lifetimes downward. Use censoring-aware methods.
A simple baseline is essential. It reveals whether the advanced method is improving accuracy or only adding complexity. Compare model calls, wall time, uncertainty and failure-mode coverage under one declared budget. Repeat stochastic calculations with several seeds; a favourable single run is not evidence of dependable efficiency.
Students can extend the example by adding correlation, a second failure mode or a modest measurement error. Explain which part of the formula changes and which remains fixed. This exercise shows how mathematics transfers from a clean textbook case to engineering and computing without pretending that the classroom model is a certified design tool.
Build a small counterexample for portnoy’s recursive approach. Portnoy develops censored regression quantiles using recursively reweighted estimation analogous to Kaplan–Meier ideas. The initial example is: Weights evolve as the quantile process advances. Then create a nearby case where the usual shortcut becomes unreliable. Algorithm details and assumptions matter. Record software method.
Counterexamples are positive learning tools. They reveal the conditions that make a method work and help students recognise when a software output deserves a pause. Keep the counterexample small enough to plot or enumerate. Check sign, support, bounds and conservation of probability before adding complexity.
When writing the conclusion, separate a documented fact from an interpretation and from an illustrative scenario. Cite the primary method paper for the factual mechanism, use the local calculation for the illustration, and label any recommendation as conditional on the stated model. This keeps career and engineering advice age-appropriate and honest.
Connect percentile-specific covariate effects to a real decision while protecting the boundary between calculation and judgement. Load can affect early failures more strongly than median failures. Coefficients beta(tau) vary across tau. First verify the arithmetic, then translate it into an allowed action and an action the evidence does not support. Testing many quantiles can produce noisy stories. Use planned quantiles and bands.
The audit should include the original question, input provenance, failure convention, algorithm settings, convergence or stopping rule, and a sensitivity result. For an adaptive method, also preserve the sequence of choices. For an optimisation, preserve every constraint. For Bayesian updating, preserve the prior and observation model. These records turn a result into something another person can challenge and improve.
A final transfer question is useful: where else would the same mathematical idea appear? Density ratios appear in survey correction and machine learning, probabilistic constraints in planning, and conditional probability in medical testing. The context changes, but transparent assumptions and reproducible checks remain valuable.
If fitted log median life difference is 0.20, the time ratio is exp(0.20)≈1.221. A reference median of 1000 hours corresponds to about 1221 hours under that coefficient. This is the central mathematical mechanism in a simple worked interpretation. Write the quantities and assumptions before using software, then reproduce the calculation or geometric argument in a small example. This does not imply every unit lasts 22.1% longer. Use conditional population language. The useful habit is to keep the physical question, the probability model and the numerical method in separate columns so that a correct computation is not mistaken for complete evidence.
Did You Know? A result can be numerically stable and still answer the wrong question if the failure event, denominator or transformation changes. Test one nearby case and predict the direction of change before recalculating. Save inputs, intermediate values and units so a second reader can audit the path.
For practice, turn the example into a sensitivity check. Change one defensible input while holding the others fixed, compare the new result with the original and explain why it moved. Then construct a counterexample in which the shortcut fails. End with two sentences: what the mathematics supports, and what remains uncertain.
Start with the operational question behind additive lifetime model. Q_T(tau|x)=x beta(tau) gives direct time differences when appropriate. In the illustrative case, A 50-hour coefficient shifts the chosen percentile by 50 hours. Draw the relevant graph, density, boundary or timeline before calculating; the picture should use the same variables and sign convention as the equations. Predictions can become negative outside observed covariates. Check support.
A student should be able to rebuild the result without hidden settings. Record the sampling rule or optimisation criterion, the exact failure definition, and the evidence used for every distribution or parameter. Compare a transparent baseline with the advanced method. If they disagree, investigate the mechanism before deciding which answer is more credible.
This chapter belongs to a larger decision, so translate the number carefully. State one action the evidence permits and one action it does not. A parent or educator can ask which school ideas are doing the work: algebra organises relationships, probability represents uncertainty, calculus describes local change, and computing repeats the documented rules at scale.
Treat log-time model as a model-checking problem rather than a vocabulary exercise. Model log lifetime to preserve positive predictions and interpret exponentiated coefficients as time ratios. A negative coefficient shortens the percentile multiplicatively. Recompute the example from the raw values and label every unit. Back-transformation changes additive interpretation. Report both scales.
The strongest check uses evidence the model did not choose for itself. Hold out later observations, an independent simulation set or a known-answer benchmark. Report errors where decisions are sensitive, especially near the failure boundary, instead of relying on one global accuracy score. A method that performs well on easy safe cases can still fail at the rare cases that motivated the analysis.
Now change one assumption and make a directional prediction before running the calculation. If the result moves the opposite way, inspect the sign convention, transformation, density ratio or constraint. This prediction-first routine develops transferable problem-solving skills because it connects symbolic work to a testable expectation.
The mathematics of relationship to accelerated failure time becomes useful only when its mechanism is explicit. An AFT model often assumes one time ratio shifts all quantiles similarly; quantile regression allows effects to vary by percentile. Consider the worked illustration: Different beta(tau) reveal distribution-shape changes. Preserve the original inputs, calculate step by step and compare with a second method whenever an analytic or high-budget reference exists. Flexible effects need more data. Compare a simple AFT baseline.
There are three uncertainties to keep apart. Sampling or numerical uncertainty comes from finite computation. Parameter uncertainty comes from estimating inputs. Model-form uncertainty comes from simplified physics, distributions or dependence. Reducing the first does not automatically reduce the other two. A credible report names all three and shows which one drives the decision.
For a practical investigation, create a small reproducible notebook or spreadsheet with a frozen data sheet, formula sheet, diagnostics sheet and decision note. Another student should be able to change one input and obtain the same update without guessing what the model meant.
Use relationship to cox regression to practise sensitivity analysis. Cox models hazard ratios, while quantile regression models lifetime percentiles directly. Crossing hazards can still permit interpretable time quantiles. Before accepting the result, identify the quantity that would change the conclusion most. Neither method dominates every dataset. Choose by estimand and support.
A simple baseline is essential. It reveals whether the advanced method is improving accuracy or only adding complexity. Compare model calls, wall time, uncertainty and failure-mode coverage under one declared budget. Repeat stochastic calculations with several seeds; a favourable single run is not evidence of dependable efficiency.
Students can extend the example by adding correlation, a second failure mode or a modest measurement error. Explain which part of the formula changes and which remains fixed. This exercise shows how mathematics transfers from a clean textbook case to engineering and computing without pretending that the classroom model is a certified design tool.
A second primary source is https://doi.org/10.1146/annurev-statistics-042720-020233. Compare the problem definition, estimator and validation rather than quoting one result in isolation.
Build a small counterexample for estimable quantile range. Censoring and follow-up determine which percentiles are supported. The initial example is: Heavy right censoring may prevent reliable high-failure-time quantiles. Then create a nearby case where the usual shortcut becomes unreliable. Software can return unstable extrapolations. Publish the supported range.
Counterexamples are positive learning tools. They reveal the conditions that make a method work and help students recognise when a software output deserves a pause. Keep the counterexample small enough to plot or enumerate. Check sign, support, bounds and conservation of probability before adding complexity.
When writing the conclusion, separate a documented fact from an interpretation and from an illustrative scenario. Cite the primary method paper for the factual mechanism, use the local calculation for the illustration, and label any recommendation as conditional on the stated model. This keeps career and engineering advice age-appropriate and honest.
Connect crossing quantile curves to a real decision while protecting the boundary between calculation and judgement. Separately fitted quantiles can cross, violating distribution ordering. A predicted 75th percentile should not fall below the median. First verify the arithmetic, then translate it into an allowed action and an action the evidence does not support. Crossing may signal noise or misspecification. Use constraints or rearrangement.
The audit should include the original question, input provenance, failure convention, algorithm settings, convergence or stopping rule, and a sensitivity result. For an adaptive method, also preserve the sequence of choices. For an optimisation, preserve every constraint. For Bayesian updating, preserve the prior and observation model. These records turn a result into something another person can challenge and improve.
A final transfer question is useful: where else would the same mathematical idea appear? Density ratios appear in survey correction and machine learning, probabilistic constraints in planning, and conditional probability in medical testing. The context changes, but transparent assumptions and reproducible checks remain valuable.
Splines or interactions can represent nonlinear load effects at each quantile. Temperature may shorten low percentiles sharply only above a threshold. This is the central mathematical mechanism in time-varying and nonlinear covariates. Write the quantities and assumptions before using software, then reproduce the calculation or geometric argument in a small example. Complexity multiplies across quantiles. Use regularisation and validation. The useful habit is to keep the physical question, the probability model and the numerical method in separate columns so that a correct computation is not mistaken for complete evidence.
Did You Know? A result can be numerically stable and still answer the wrong question if the failure event, denominator or transformation changes. Test one nearby case and predict the direction of change before recalculating. Save inputs, intermediate values and units so a second reader can audit the path.
For practice, turn the example into a sensitivity check. Change one defensible input while holding the others fixed, compare the new result with the original and explain why it moved. Then construct a counterexample in which the shortcut fails. End with two sentences: what the mathematics supports, and what remains uncertain.
Start with the operational question behind uncertainty intervals. Bootstrap or asymptotic methods quantify coefficient and predicted-quantile uncertainty. In the illustrative case, Tail quantiles usually have wider intervals. Draw the relevant graph, density, boundary or timeline before calculating; the picture should use the same variables and sign convention as the equations. Naive resampling can mishandle clustering. Resample at the unit level.
A student should be able to rebuild the result without hidden settings. Record the sampling rule or optimisation criterion, the exact failure definition, and the evidence used for every distribution or parameter. Compare a transparent baseline with the advanced method. If they disagree, investigate the mechanism before deciding which answer is more credible.
This chapter belongs to a larger decision, so translate the number carefully. State one action the evidence permits and one action it does not. A parent or educator can ask which school ideas are doing the work: algebra organises relationships, probability represents uncertainty, calculus describes local change, and computing repeats the documented rules at scale.
Treat clustered and recurrent data as a model-checking problem rather than a vocabulary exercise. Multiple components from one batch or repeated events from one machine create dependence. Batch-level resampling can preserve shared manufacturing effects. Recompute the example from the raw values and label every unit. Ordinary independent formulas understate uncertainty. Identify clusters.
The strongest check uses evidence the model did not choose for itself. Hold out later observations, an independent simulation set or a known-answer benchmark. Report errors where decisions are sensitive, especially near the failure boundary, instead of relying on one global accuracy score. A method that performs well on easy safe cases can still fail at the rare cases that motivated the analysis.
Now change one assumption and make a directional prediction before running the calculation. If the result moves the opposite way, inspect the sign convention, transformation, density ratio or constraint. This prediction-first routine develops transferable problem-solving skills because it connects symbolic work to a testable expectation.
The mathematics of model diagnostics becomes useful only when its mechanism is explicit. Check residual patterns, censoring distribution, crossing, calibration and coverage by percentile. Consider the worked illustration: About half of comparable lifetimes should fall below a well-calibrated median prediction. Preserve the original inputs, calculate step by step and compare with a second method whenever an analytic or high-budget reference exists. In-sample proportions can mislead. Use held-out units.
There are three uncertainties to keep apart. Sampling or numerical uncertainty comes from finite computation. Parameter uncertainty comes from estimating inputs. Model-form uncertainty comes from simplified physics, distributions or dependence. Reducing the first does not automatically reduce the other two. A credible report names all three and shows which one drives the decision.
For a practical investigation, create a small reproducible notebook or spreadsheet with a frozen data sheet, formula sheet, diagnostics sheet and decision note. Another student should be able to change one input and obtain the same update without guessing what the model meant.
Use quantile calibration to practise sensitivity analysis. For predicted tau quantiles, observed failure proportions before those times should align with tau after accounting for censoring. Calibration can be assessed in covariate groups. Before accepting the result, identify the quantity that would change the conclusion most. Poor support weakens the check. Report denominators.
A simple baseline is essential. It reveals whether the advanced method is improving accuracy or only adding complexity. Compare model calls, wall time, uncertainty and failure-mode coverage under one declared budget. Repeat stochastic calculations with several seeds; a favourable single run is not evidence of dependable efficiency.
Students can extend the example by adding correlation, a second failure mode or a modest measurement error. Explain which part of the formula changes and which remains fixed. This exercise shows how mathematics transfers from a clean textbook case to engineering and computing without pretending that the classroom model is a certified design tool.
Build a small counterexample for decision interpretation. Use low percentiles for conservative planning only with costs and consequences. The initial example is: A 10th-percentile life can inform an inspection window. Then create a nearby case where the usual shortcut becomes unreliable. It is not a guaranteed safe life. Add uncertainty and failure severity.
Counterexamples are positive learning tools. They reveal the conditions that make a method work and help students recognise when a software output deserves a pause. Keep the counterexample small enough to plot or enumerate. Check sign, support, bounds and conservation of probability before adding complexity.
When writing the conclusion, separate a documented fact from an interpretation and from an illustrative scenario. Cite the primary method paper for the factual mechanism, use the local calculation for the illustration, and label any recommendation as conditional on the stated model. This keeps career and engineering advice age-appropriate and honest.
Connect practice activity to a real decision while protecting the boundary between calculation and judgement. Fit hand-calculated uncensored medians for two groups, then reason how one censored long-lived unit affects evidence. Compare additive and log-time interpretations. First verify the arithmetic, then translate it into an allowed action and an action the evidence does not support. Hand work cannot replace censored estimation. Keep percentiles ordered.
The audit should include the original question, input provenance, failure convention, algorithm settings, convergence or stopping rule, and a sensitivity result. For an adaptive method, also preserve the sequence of choices. For an optimisation, preserve every constraint. For Bayesian updating, preserve the prior and observation model. These records turn a result into something another person can challenge and improve.
A final transfer question is useful: where else would the same mathematical idea appear? Density ratios appear in survey correction and machine learning, probabilistic constraints in planning, and conditional probability in medical testing. The context changes, but transparent assumptions and reproducible checks remain valuable.
Quantile regression connects percentages, ordered data, absolute loss, logarithms and conditional statements. Ask why median and mean answer different questions. This is the central mathematical mechanism in parent and educator guidance. Write the quantities and assumptions before using software, then reproduce the calculation or geometric argument in a small example. Use a sorted dot plot first. Translate coefficients into hours. The useful habit is to keep the physical question, the probability model and the numerical method in separate columns so that a correct computation is not mistaken for complete evidence.
Did You Know? A result can be numerically stable and still answer the wrong question if the failure event, denominator or transformation changes. Test one nearby case and predict the direction of change before recalculating. Save inputs, intermediate values and units so a second reader can audit the path.
For practice, turn the example into a sensitivity check. Change one defensible input while holding the others fixed, compare the new result with the original and explain why it moved. Then construct a counterexample in which the shortcut fails. End with two sentences: what the mathematics supports, and what remains uncertain.
Start with the operational question behind common misconceptions. A 90th survival percentile can be confused with a 90th failure-time quantile, censoring is not failure and one percentile does not describe the full distribution. In the illustrative case, Quantile effects can differ. Draw the relevant graph, density, boundary or timeline before calculating; the picture should use the same variables and sign convention as the equations. Crossing predictions are invalid. Define tau carefully.
A student should be able to rebuild the result without hidden settings. Record the sampling rule or optimisation criterion, the exact failure definition, and the evidence used for every distribution or parameter. Compare a transparent baseline with the advanced method. If they disagree, investigate the mechanism before deciding which answer is more credible.
This chapter belongs to a larger decision, so translate the number carefully. State one action the evidence permits and one action it does not. A parent or educator can ask which school ideas are doing the work: algebra organises relationships, probability represents uncertainty, calculus describes local change, and computing repeats the documented rules at scale.
Treat when quantile regression is unsuitable as a model-checking problem rather than a vocabulary exercise. Extreme censoring, sparse tails, dynamic repairs or tiny samples may make target quantiles unidentified. Few failures cannot support early and late percentile stories. Recompute the example from the raw values and label every unit. Complex algorithms do not create information. Narrow the estimand.
The strongest check uses evidence the model did not choose for itself. Hold out later observations, an independent simulation set or a known-answer benchmark. Report errors where decisions are sensitive, especially near the failure boundary, instead of relying on one global accuracy score. A method that performs well on easy safe cases can still fail at the rare cases that motivated the analysis.
Now change one assumption and make a directional prediction before running the calculation. If the result moves the opposite way, inspect the sign convention, transformation, density ratio or constraint. This prediction-first routine develops transferable problem-solving skills because it connects symbolic work to a testable expectation.
Continue with the Mathematics Learning Hub, the eduKate Mathematics Learning System, the approach to learning mathematics, the Singapore Mathematics curriculum overview, the cross-subject learning approach and the previous reliability article. Each destination has its own role: subject navigation, learning method, school-to-advanced progression, or continuity with the latest reliability mechanism.
The mathematics of research and next reading becomes useful only when its mechanism is explicit. Portnoy develops censored regression quantiles, while Peng reviews quantile regression for survival data and its assumptions. Consider the worked illustration: Read censoring and support conditions before using software defaults. Preserve the original inputs, calculate step by step and compare with a second method whenever an analytic or high-budget reference exists. Clinical examples do not automatically validate engineering transfer. Reproduce uncensored quantiles first.
There are three uncertainties to keep apart. Sampling or numerical uncertainty comes from finite computation. Parameter uncertainty comes from estimating inputs. Model-form uncertainty comes from simplified physics, distributions or dependence. Reducing the first does not automatically reduce the other two. A credible report names all three and shows which one drives the decision.
For a practical investigation, create a small reproducible notebook or spreadsheet with a frozen data sheet, formula sheet, diagnostics sheet and decision note. Another student should be able to change one input and obtain the same update without guessing what the model meant.
Quick answers
What should I calculate first? Start with the estimand or failure event, then a simple baseline.
Does the advanced method guarantee accuracy? No. It needs input, numerical and model checks.
Which school mathematics matters? Algebra, graphs, probability, functions and careful units all contribute.
How can a student practise safely? Use fictional or open benchmark data and preserve every intermediate value.
What makes a career claim responsible? Describe how the mathematics is used without promising admission, salary or employment.
Extended practice laboratory
Practice case 1: Why model lifetime percentiles
Setup: Use this chapter’s illustrative case: The 10th percentile can guide conservative warranty discussion.
Task: Choose the percentile before analysis.
Checking target: A mean can hide tail behaviour.
Practice case 2: Conditional quantile definition
Setup: Use this chapter’s illustrative case: Median life uses tau=0.5.
Task: State failure-quantile convention.
Checking target: Survival probability notation reverses the tail perspective.
Practice case 3: Time-scale interpretation
Setup: Use this chapter’s illustrative case: A design indicator may add 120 hours to the fitted median.
Task: Translate back to original units.
Checking target: Interpretation depends on the link and transformation.
Practice case 4: Check loss without censoring
Setup: Use this chapter’s illustrative case: Positive and negative residuals receive weights determined by tau.
Task: Plot the loss shape.
Checking target: It is not least squares.
Practice case 5: Why censoring complicates quantiles
Setup: Use this chapter’s illustrative case: A unit operating at cutoff may lie above several quantiles.
Task: Use censoring-aware methods.
Checking target: Treating censoring time as failure biases lifetimes downward.
Practice case 6: Portnoy’s recursive approach
Setup: Use this chapter’s illustrative case: Weights evolve as the quantile process advances.
Task: Record software method.
Checking target: Algorithm details and assumptions matter.
Practice case 7: Percentile-specific covariate effects
Setup: Use this chapter’s illustrative case: Coefficients beta(tau) vary across tau.
Task: Use planned quantiles and bands.
Checking target: Testing many quantiles can produce noisy stories.
Practice case 8: A simple worked interpretation
Setup: Use this chapter’s illustrative case: A reference median of 1000 hours corresponds to about 1221 hours under that coefficient.
Task: Use conditional population language.
Checking target: This does not imply every unit lasts 22.1% longer.
Practice case 9: Additive lifetime model
Setup: Use this chapter’s illustrative case: A 50-hour coefficient shifts the chosen percentile by 50 hours.
Task: Check support.
Checking target: Predictions can become negative outside observed covariates.
Practice case 10: Log-time model
Setup: Use this chapter’s illustrative case: A negative coefficient shortens the percentile multiplicatively.
Task: Report both scales.
Checking target: Back-transformation changes additive interpretation.