Creates named argument lists for sim_trend_stack() by crossing temporal,
spatial, signal and noise conditions. It separates experimental design from
data generation so the complete scenario grid can be inspected and retained.
Usage
simulation_design(..., constants = list(), prefix = "scenario", verbose = TRUE)Value
A named list of argument lists suitable for the scenarios
argument of benchmark_methods(), with classes
"sptrends_simulation_design" and "sptrends" for unified
printing, summaries, and plotting.
Details
Function type: Benchmarking function – defines simulation scenarios; it does not generate data or perform inference.
Typical use
Define the factors that should vary, add shared settings through constants,
and pass the returned list to benchmark_methods().
Methodological details
Experimental design
Every combination is retained. This makes comparisons across spatial and
temporal dependence explicit and prevents methods from being evaluated on
accidentally different scenario sets. Values that must remain grouped,
such as a two-number signal_size, should be wrapped in a list.
Computational considerations
This function only constructs argument lists. Memory use grows with the
product of the numbers of supplied factor levels; data generation remains
deferred to benchmark_methods().
Limitations
A full factorial design can become unnecessarily large. Users should vary
scientifically relevant factors and keep fixed settings in constants.
Quality assurance
Tests verify factorial completeness, deterministic ordering, grouped
values, validation failures, metadata retention and S3 presentation. The
complete external simulation-cycle validation passed all 33 prespecified
controls; see inst/validation/ for the retained protocol and results.
See also
sim_trend_stack(), benchmark_methods()
Other validation functions:
benchmark_methods(),
benchmark_summary(),
compare_detections(),
plot_detection_comparison()
