
Assess whether recovery-simulation results are ready to use
Source:R/api-simulation.R
assess_mfrm_recovery.RdConverts the numerical output from simulate_mfrm_recovery() into a
reviewer-facing adequacy checklist. The goal is not to impose one universal
pass/fail rule; it is to make the main user questions explicit: Did the runs
finish? Did the fitted models converge? Are uncertainty summaries available?
Are coverage and Monte Carlo precision plausible? If practical RMSE or bias
limits are supplied, which parameter groups need follow-up? For
GPCM, which slope-regime generator condition frames the recovery evidence?
This only reads an existing simulation result. It does not generate data,
refit models, add replications or repair unavailable uncertainty estimates.
Usage
assess_mfrm_recovery(
x,
min_reps = 30,
min_success_rate = 0.95,
min_convergence_rate = 0.95,
min_se_available = 0.8,
coverage_target = 0.95,
coverage_tolerance = 0.05,
max_mcse_rmse_ratio = 0.25,
max_rmse = NULL,
max_abs_bias = NULL,
top_n = 6,
digits = 3,
...
)
# S3 method for class 'mfrm_recovery_assessment'
plot(
x,
y = NULL,
type = c("status", "metrics"),
metric = c("rmse", "bias", "coverage", "se_available", "mcse_rmse"),
draw = TRUE,
...
)Arguments
- x
For
assess_mfrm_recovery(), output fromsimulate_mfrm_recovery(). Forplot.mfrm_recovery_assessment(), output fromassess_mfrm_recovery().- min_reps
Minimum replication count expected before treating the simulation for inferential use.
- min_success_rate
Minimum acceptable proportion of replications that generated data and produced a fitted model.
- min_convergence_rate
Minimum acceptable proportion of replications whose fitted model reported convergence.
- min_se_available
Minimum acceptable proportion of all expected targets with matching structural standard errors in each parameter group, including targets in failed fits. Unknown target counts give
not_available. Set toNULLto skip this check.- coverage_target
Nominal coverage target, usually
0.95.- coverage_tolerance
Absolute tolerance around
coverage_target.- max_mcse_rmse_ratio
Maximum acceptable Monte Carlo SE of RMSE divided by RMSE. Set to
NULLto skip this precision check.- max_rmse
Optional practical RMSE limit. Use a scalar for all parameter groups or a named vector/list with names such as
"facet","step","slope","Rater", or"facet:Rater:logit".- max_abs_bias
Optional practical absolute-bias limit. Naming follows
max_rmse. Mean-aligned location groups and complete identified log-slope blocks have zero average bias by construction and remainnot_assessed.- top_n
Number of next-action lines retained in the compact output.
- digits
Digits used by the print method.
- ...
For
assess_mfrm_recovery(), unused arguments must be empty; unknown assessment options are rejected rather than silently ignored. For the plot method, reserved for S3 generic compatibility.- y
Reserved for S3 generic compatibility.
- type
Assessment plot route.
"status"summarizes checklist status counts;"metrics"plots a parameter-group assessment metric colored by its status.- metric
Metric used when
type = "metrics". Supported values are"rmse","bias","coverage","se_available", and"mcse_rmse".- draw
If
TRUE, print theggplotobject. IfFALSE, return theggplotobject invisibly without drawing (tables and notes viaplot_data()).
Value
An object of class mfrm_recovery_assessment with:
overview: compact run-level status.checklist: reviewer-facing adequacy checks.condition_review: generator-condition metadata, includingGPCMslope-regime interpretation and generated score-category support when available.condition_reporting_notes: reporter-facing generator-condition caveats separated from parameter-recovery conclusions.diagnostic_reporting_notes: reporter-facing fit/separation caveats retained as diagnostic context rather than recovery criteria.diagnostic_review: optional fit/separation operating-characteristic context when retained bysimulate_mfrm_recovery().metric_review: parameter-group metric checks.uncertainty_review: coverage / SE availability interpretation with expected/available counts, coverage MCSE and unavailable reasons.reading_order: recommended first-read order for the summary, condition, plot, and row-level recovery outputs.next_actions: short action list sorted by severity.thresholds: thresholds used for the assessment.
Details
RMSE and bias adequacy depends on the substantive scale and the use case, so
the function does not mark them as failed unless the user supplies
max_rmse or max_abs_bias. Without those limits, the corresponding rows are
marked not_assessed and the next action asks the user to set practical
thresholds when a decision depends on the metric.
BiasBasis explains groups whose mean bias is fixed at zero by identification;
even a supplied bias limit cannot turn that identity into recovery evidence.
Threshold names are matched from the most specific group to its type or
default; see max_rmse for examples.
Metrics are recomputed from row-level evidence. Coverage is conditional on
the available centered facet intervals, not all planned targets.
uncertainty_review retains counts, CoverageAvailabilityRate,
McseCoverage95 and CIReasons alongside its descriptive checklist.
See simulate_mfrm_recovery() for the estimands, independent-trial MCSE,
unsupported interval groups and handling of legacy saved results. Checklist
tolerances do not replace the Monte Carlo uncertainty or qualify an estimator.
The condition_review table is generator metadata for interpreting the
recovery run. For GPCM, GPCMSlopeRegime, StressLevel, and
generated score-category support describe the data-generating condition;
they are not model-fit tests and they are not literature-derived adequacy
cut points. condition_reporting_notes turns those generator conditions
into reporter-facing caveats, such as high-dispersion slope stress or sparse
generated score support.
The optional diagnostic_review table is available when
simulate_mfrm_recovery() was called with include_diagnostics = TRUE.
It summarizes fit and separation operating characteristics as diagnostic
context only. Its availability fields do not mean that fit or separation
values are adequate, and those rows do not enter the recovery adequacy
status. diagnostic_reporting_notes should be read first when drafting
fit/separation language because it separates zero separation/reliability,
absolute fit-ZSTD flags, and df-sensitive ZSTD flags from recovery criteria.
plot.mfrm_recovery_assessment() is a user-facing review aid. Use
type = "status" first to see where checklist attention is needed, then
type = "metrics" to inspect the parameter groups behind RMSE, bias,
coverage, standard-error availability, or Monte Carlo precision statuses.
The intended reading order is summary(recovery_review), then
condition_reporting_notes and condition_review, then
diagnostic_reporting_notes and diagnostic_review, then the status plot,
then the metric plot, then the row-level recovery table for the parameter
groups that need follow-up. When draw = FALSE, the plot data also include
reading_order, guidance, condition/diagnostic handoff tables, and
user-facing plot tables such as section_status for status plots and
metric_review for metric plots.
Examples
# Long-running workflow; run explicitly when needed.
# example("assess_mfrm_recovery", run.dontrun = TRUE)
if (FALSE) { # \dontrun{
rec <- simulate_mfrm_recovery(
n_person = 12,
n_rater = 2,
n_criterion = 2,
reps = 1,
maxit = 30,
seed = 123
)
assess_mfrm_recovery(rec, min_reps = 1, max_rmse = 1)
# Read the GPCM generator condition separately from recovery adequacy.
gpcm_spec <- build_mfrm_sim_spec(
n_person = 14,
n_rater = 2,
n_criterion = 2,
raters_per_person = 2,
model = "GPCM",
step_facet = "Criterion",
slope_facet = "Criterion",
slopes = c(0.85, 1.15),
assignment = "crossed"
)
gpcm_rec <- suppressWarnings(simulate_mfrm_recovery(
sim_spec = gpcm_spec,
reps = 1,
fit_method = "MML",
quad_points = 5,
maxit = 12,
include_diagnostics = TRUE,
include_person = FALSE,
seed = 456
))
gpcm_review <- assess_mfrm_recovery(
gpcm_rec,
min_reps = 1,
max_rmse = c(slope = 2),
max_abs_bias = c(slope = 1),
min_se_available = NULL,
max_mcse_rmse_ratio = NULL
)
gpcm_review$condition_reporting_notes[, c(
"ConditionArea", "ReportingAttention", "ConditionFinding"
)]
gpcm_review$condition_review[, c(
"Model", "GPCMSlopeRegime", "StressLevel", "ScoreSupportStatus"
)]
gpcm_review$diagnostic_reporting_notes[, c(
"Facet", "ReportingAttention", "DiagnosticFinding"
)]
summary(gpcm_review)$reading_order
} # }