Summarize a design-simulation study
Usage
# S3 method for class 'mfrm_design_evaluation'
summary(object, digits = 3, ...)Arguments
- object
Output from
evaluate_mfrm_design().- digits
Number of digits used when printing the summary. Returned numeric tables retain full precision for plotting and design decisions.
- ...
Reserved for generic compatibility.
Value
An object of class summary.mfrm_design_evaluation with components:
overview: run-level overviewdesign_summary: aggregated design-by-facet metrics, with design-variable alias columns when applicablesparse_review: compact planned-missingness and rater-link review counts when sparse linked designs are activeademp: simulation-study metadata carried forward from the original objectfacet_names: public facet labels carried from the simulation specificationdesign_variable_aliases: accepted public aliases for design variablesdesign_descriptor: role-based design-variable metadataplanning_scope: explicit record of the current planning contractplanning_constraints: explicit record of mutable/locked design variablesplanning_schema: structured planning metadatastructural_design_review: deterministic structural review of the named-facet design grid; it reports design bookkeeping rather than simulation performancenotes: short interpretation notes
Details
The summary emphasizes condition-level averages that are useful for practical design planning, especially:
convergence rate
separation and reliability by facet
severity recovery RMSE
mean misfit rate
Reps, ConvergenceRate, and McseConvergenceRate use all recorded
replications for each design, including fit and diagnostic failures.
Only a recorded Converged = TRUE counts as converged. AvailableReps
counts the replications with returned results for that facet; performance
means still use the available metric values. Designs with no returned
facet results have no performance-summary rows and cannot be recommended.
To update an older saved summary, call summary() again on the original
evaluation object; no simulation or refitting is needed. Rebuilding also
restores full precision when an older summary stored rounded metrics.
It also withholds legacy PCM/GPCM recovery metrics whose step-location truth
coordinates were not verified; those require a new evaluation for corrected
recovery, while other diagnostic metrics remain. RecoveryAvailableReps
reports the number of finite trial RMSEs. Mean-aligned bias is zero by
construction; see evaluate_mfrm_design() for the comparison target.
MaxRatings and MaxRatingsPerRater are the largest total rating count
and individual rater workload across all recorded replications, including
failed runs. A rating is one generated person-rater-criterion row; weights
do not multiply workload. A maximum is NA when any replication lacks
that count, including older evaluations without per-rater workload records.
MaxRaterComponents and MaxCriterionComponents give the largest
Person-facet component count across all recorded assignments; a missing
count makes its maximum NA. DisconnectedReps counts replications with
a recorded disconnection in either graph. Zero known disconnections does
not establish connectedness when records are missing. Sparse-design
summaries also use all run records, including failures.
Examples
# Supplementary workflow: run explicitly to keep routine checks brief.
# example("summary.mfrm_design_evaluation", run.dontrun = TRUE)
if (FALSE) { # \dontrun{
# One saved replication illustrates output structure, not precise rates.
# Regeneration recipe: examples/simulation-results.R in the package.
saved <- readRDS(system.file("examples", "simulation-design.rds",
package = "mfrmr", mustWork = TRUE))
# Inspect saved$generation_warnings and the result's run/status tables.
sim_eval <- saved$result
s <- summary(sim_eval)
s$overview
head(s$design_summary)
} # }
