--- title: "What rcicr stores" output: rmarkdown::html_vignette vignette: > %\VignetteIndexEntry{What rcicr stores} %\VignetteEngine{knitr::rmarkdown} %\VignetteEncoding{UTF-8} --- ```{r, include = FALSE} knitr::opts_chunk$set(collapse = TRUE, comment = "#>") fields <- function(...) { rows <- matrix(c(...), ncol = 2, byrow = TRUE) data.frame(field = rows[, 1], description = rows[, 2]) } table_of <- function(x, header = c("Field", "What it is")) { x$field <- paste0("`", x$field, "`") knitr::kable(x, col.names = header, row.names = FALSE) } ``` Two objects outlive the R session that made them: the `.Rdata` file that `generateStimuli2IFC()` writes, and the classification image that `generateCI()` returns, which you may save yourself. This vignette lists everything in both. Its tables are checked against freshly generated objects every time the package is built, so they describe the version you have installed. ```{r setup} library(rcicr) ``` ## The stimulus `.Rdata` file The file is the only link between generating stimuli and analysing responses. Without it, a stimulus set can only be regenerated from the seed together with every generation setting; `vignette("recipes", package = "rcicr")` shows how, and how to check the result against the stimulus PNGs. Keep it with your response data and with anything you publish. `generateStimuli2IFC()` writes one file per call, named `