Tutorials › Multiple Imputation by Chained Equations (MICE) › Diagnosing SMC-FCS Draws for Derived-Term Models

Passive Imputation and Substantive-Model-Compatible Methods · Tutorial 330 of 497

Diagnosing SMC-FCS Draws for Derived-Term Models

Learn to diagnose inefficient or implausible SMC-FCS draws without mistaking a low acceptance rate or an extreme imputation for proof that the model is wrong.

Advanced 12 min read

What You'll Learn

  • Calculate empirical SMC-FCS acceptance rates overall and for individual records or subgroups.
  • Interpret low or uneven rates as prompts for investigation, not automatic evidence of invalid imputations.
  • Compare imputed covariate values with observed values, units, support, and relevant conditional patterns.
  • Check that nonlinear derived terms are computed from the corresponding covariate draws.
  • Use worked examples to identify practical diagnostics and their limitations.

Why Diagnose SMC-FCS Draws?

Substantive-model-compatible fully conditional specification (SMC-FCS) is designed to make imputation draws reflect the substantive model, including nonlinear terms such as a quadratic effect. A run can nevertheless be inefficient or implemented incorrectly. Rejection sampling may accept few proposals, imputed covariate values may be implausible in context, or a derived term may not correspond to the covariate value from which it should be calculated. Each problem calls for a different check.

Diagnostics are evidence about the computation, not a guarantee of correct inference. A plausible-looking draw does not establish that the substantive model is correctly specified, that the missingness assumptions are appropriate, or that the imputation model captures relevant predictors. Conversely, a draw outside the observed sample range is not automatically an error. Assessment requires the model, units, support, and data context.

Definition: For a rejection-sampling step, the empirical acceptance rate is the number of accepted proposals divided by the number of proposals generated. The sampled covariate range is the range of values drawn for an incomplete covariate over a specified set of records and iterations. A derived term is a deterministic function of one or more covariates, such as \(X^2\) or \(X_1X_2\); in a completed data set it must equal that function evaluated at the corresponding completed covariate value or values.

Acceptance Rates: Efficiency and Warning Signs

In rejection sampling, a proposal is accepted with a probability chosen so that accepted values follow the desired target distribution. For instance, if a proposal density is \(q(x)\) and an unnormalized target density is \(g(x)\), a valid rejection rule requires a finite constant \(M\) such that \(g(x)\le Mq(x)\) wherever the target has support. The acceptance probability is \(g(x)/(Mq(x))\). This rule assumes that the proposal covers the target support and that the stated bound is valid. If either condition fails, the rejection sampler is not valid, regardless of its observed acceptance rate.

For \(N\) proposals with acceptance indicators \(A_j\), where \(A_j=1\) means proposal \(j\) was accepted and \(A_j=0\) otherwise, the empirical rate is

$$ \widehat r=\frac{1}{N}\sum_{j=1}^{N} A_j =\frac{\text{number accepted}}{\text{number proposed}}. $$

Under a fixed proposal and target, the expected acceptance probability is the proposal average of the acceptance rule. In the rule above, it is \(\int q(x)g(x)/(Mq(x))\,dx=Z/M\), where \(Z=\int g(x)\,dx\) is the normalizing constant. Thus a low rate can result from a proposal that poorly covers important target regions or from a conservative (loose) bound \(M\). It principally signals computational inefficiency. It does not, by itself, show that accepted draws have the wrong target distribution.

There is no universal acceptance-rate threshold that separates acceptable from unacceptable SMC-FCS runs. Record the number of proposals and accepted draws, and examine rates by incomplete record, iteration, and relevant covariate or outcome patterns. A pooled rate may hide records for which almost all proposals are rejected. Also verify that the implementation uses the intended target and a valid acceptance rule; a seemingly high rate cannot certify either.

Worked Example: Interpreting an Overall Acceptance Rate

Suppose a hypothetical SMC-FCS run generates 500 proposals for an incomplete exposure value, and 94 are accepted. The empirical rate is

$$ \widehat r=\frac{94}{500}=0.188=18.8\%. $$

The run accepts about 19 proposals per 100 generated. This indicates that many proposals are being discarded, so generating enough draws may require substantial computation. It does not establish that the accepted values are biased: that conclusion depends on whether the target, proposal support, and rejection rule are correct.

A useful next check is to tabulate acceptance by record and iteration, then inspect proposal and accepted-value distributions. If most rejections occur for records with outcome patterns that concentrate the target in a narrow region, the proposal may be inefficient for those records. If the rate is unexpectedly high, check the acceptance calculation as well as its efficiency: omitting a likelihood contribution, for example, can produce an easy-to-accept but incorrect draw.

Covariate Ranges and Conditional Plausibility

For each incomplete continuous covariate, examine the values actually sampled, not just the final minimum and maximum. Summaries such as quantiles, histograms, and plots by iteration or record can reveal concentration at bounds, long tails, gaps, or abrupt changes. Compare draws with observed values, known measurement limits, units, and scientifically possible values. Where relevant, compare them within important outcome or covariate patterns rather than relying only on a marginal summary.

The observed minimum and maximum are sample extremes, not necessarily the support of the population. A draw just beyond an observed extreme may be reasonable under the imputation model. A draw outside a genuine physical or design limit, such as a negative duration that cannot be negative, warrants investigation. Likewise, a range consistent with the observed data does not prove the conditional distribution is appropriate. Check whether the location, spread, and tails of the draws are credible given the modeled predictors.

For nonlinear substantive models, range checks have an additional purpose: the substantive effect can be especially sensitive to values in the tails. For a quadratic term, a few large absolute values of \(X\) can have substantial influence because \(X^2\) grows rapidly. Inspect the covariate scale and the derived-term scale together, and determine whether those values are plausible under the model and in the application.

Worked Example: Checking a Quadratic Term Against the Covariate Range

In a hypothetical analysis, the observed exposure \(X\) ranges from \(-2.1\) to \(2.4\) units. Across imputed records, sampled values range from \(-3.0\) to \(3.4\). The substantive model includes \(X^2\). A draw of \(X=3.4\) therefore implies

$$ X^2=(3.4)^2=11.56\text{ units}^2. $$

The value \(3.4\) is beyond the observed sample maximum, but that fact alone does not make it invalid. The diagnostic question is whether it is within the covariate’s plausible support and whether the imputation model assigns it credible probability. The squared value, 11.56 units squared, also deserves attention because it can strongly affect a quadratic predictor.

Suppose 2 of 200 imputed values exceed 2.4. That is \(2/200=0.0100\), or 1.00% of those draws. This small fraction is a summary, not a pass/fail threshold. Inspect which records receive these values, their predictors and outcomes, and whether the model and known measurement limits make the tail plausible. If values outside a genuine bound appear, investigate support restrictions, coding, units, and the proposal. Do not simply truncate draws at the observed maximum: that changes the distribution unless the maximum is a genuine support boundary and the model accounts for it.

Derived-Term Behavior and Chain Monitoring

A derived term must be calculated from the completed covariates for the same record and the same iteration. If an imputed \(X\) is paired with a separately imputed \(X^2\), the identity can fail, and the substantive model is no longer using the claimed quadratic term. The basic check is direct: for each completed record, calculate \(X^2\) from \(X\) and compare it with the stored term. For an interaction, compare the stored term with the product of the corresponding covariate values. Differences should be zero apart from any explicitly justified numerical rounding.

Identity checks do not establish that the distribution of \(X\) is appropriate. Inspect the distribution of \(X^2\) as well: it is nonnegative, and its shape is determined by the distribution of \(X\). For an interaction \(X_1X_2\), check the product against both inputs, since unusual combinations can arise even when each marginal range looks ordinary. Plot derived terms against their source covariates when useful, and review summaries across iterations to see whether the chain settles into a stable range rather than drifting or showing persistent changes.

A trace plot displays a sampled value or summary against iteration. Persistent drift, long stretches with little variation, or large abrupt shifts can indicate poor exploration or an unstable computation. A trace that looks stable is reassuring but not conclusive; a run may appear steady while exploring only part of the relevant distribution. Where draws are highly dependent, a large raw number of iterations can also overstate how much independent information the chain contains. Use such plots alongside acceptance, range, and deterministic-identity checks rather than treating any single display as a verdict.

Worked Example: Finding a Derived-Term Mismatch

Consider a hypothetical completed record with \(X=-1.5\) units and a stored quadratic term of \(2.10\) units squared. The required identity gives

$$ X^2=(-1.5)^2=2.25\text{ units}^2. $$

The difference between the stored value and the required value is \(2.10-2.25=-0.15\) units squared. This is not a rounding discrepancy at the displayed precision. The derived term is inconsistent with the covariate draw, so the completed record does not contain the intended quadratic model input.

The appropriate response is to trace how the term was created and updated. It may have been calculated from an earlier value of \(X\), imputed independently, or carried over from a different iteration. Recalculate it deterministically from the completed \(X\) value and repeat the identity check across all records and imputations. Recalculation corrects this identity error; it does not, by itself, show that the imputation distribution for \(X\) is adequate.

A Practical Diagnostic Sequence

Use several checks together. First confirm that each derived term is computed from the matching covariate draws. Then summarize the sampling process and the covariate draws, investigate patterns that appear concentrated in particular records or iterations, and assess whether the algorithm’s assumptions and support are credible.

1
Check deterministic identities.
For every completed record, recompute each derived term from its source covariates and compare the result with the stored term.
2
Summarize proposals and acceptance.
Calculate accepted divided by proposed draws overall and by record or relevant pattern. Retain denominators so that rates based on very different numbers of proposals are distinguishable.
3
Inspect covariate draws.
Compare ranges, quantiles, and tails with units, genuine support limits, observed data, and conditional context. Examine the derived-term scale where nonlinear effects are present.
4
Review behavior across iterations.
Use plots and summaries to look for drift, prolonged stagnation, or abrupt shifts, and investigate patterns rather than relying on one pooled statistic.
5
Investigate and rerun when indicated.
Check coding, the target and proposal support, the rejection bound, and model plausibility. If a proposal is inefficient, consider a more suitable proposal or valid sampling strategy, then repeat the diagnostics.

Common Pitfalls and Limits

A useful comparison is with passive imputation of a derived term. Passive calculation makes the deterministic identity explicit, but does not by itself ensure that the imputed covariate distribution respects the substantive model. SMC-FCS targets compatibility with that model, but its draws still require implementation and plausibility checks. Neither a low acceptance rate nor an identity check alone answers whether one approach is adequate for a particular analysis.

A common mistake is to treat a low acceptance rate as proof that the accepted draws are invalid, or to treat an observed-range exceedance as an automatic error. The correction is to separate efficiency from validity: investigate the sampling rule and proposal for the first issue, and assess support and conditional plausibility for the second. Similarly, a perfect derived-term identity proves only that the transformation was applied consistently; it does not validate the imputation model.

Diagnostics cannot repair an incorrect substantive model, omitted predictors, incompatible data assumptions, or a missingness process that is inadequately represented. Acceptance rates can also vary naturally across records, and finite runs make empirical rates noisy. Document what was checked, the scale and units used, where any warnings arose, and what changes followed. A rerun should be evaluated afresh rather than declared successful merely because a single rate improved.

Check Your Understanding

Answer each question, then compare your reasoning with the solutions.

  1. A run accepts 72 of 400 proposals. Calculate the empirical acceptance rate and state one conclusion it supports and one conclusion it does not support.
  2. An exposure has observed values from 0.4 to 8.0 units. One imputed value is 8.6 units. What information is needed before calling the draw invalid?
  3. For a completed record, \(X=-2.2\) and the stored term \(X^2\) is 4.84. Does the identity check pass? Give the expected value and units if \(X\) is measured in years.
  4. Two groups each have 200 proposals. Group A accepts 80 and Group B accepts 20. Calculate both group rates and the pooled rate. Why should the pooled rate not be the only diagnostic?

Solutions. (1) \(72/400=0.180\), or 18.0%. This supports the conclusion that the observed rejection step is computationally inefficient enough to investigate; it does not establish that accepted draws are biased or invalid. (2) Check whether 8.0 is a genuine support limit or only the observed sample maximum, then review units, measurement limits, the record’s predictors and outcome, and the model’s plausible tail behavior. The exceedance alone is insufficient. (3) The expected term is \((-2.2)^2=4.84\) years squared, so the identity passes. (4) Group A has \(80/200=40.0\%\); Group B has \(20/200=10.0\%\). The pooled rate is \((80+20)/(200+200)=100/400=25.0\%\). It hides the much lower rate in Group B, which may indicate that proposals are less efficient for that group or that its sampling behavior needs closer examination.

Clinical Biostats