The analysis was run with R 4.6.2. renv.lock records 49 packages, including their required dependencies. It was checked against the installed library used to produce the results. A clean restore into a new isolated library has not been run.

Use R 4.6.2 for the closest reproduction. Install R, just, and renv before running the saved commands. On the maintained toolchain, R is managed by rig and R packages are installed through pak. If pak is already available, this command installs the recorded renv release in an interactive R session:

    pak::pkg_install("renv@1.3.1")

From the project root, run:

    just restore

The restore script reads the lockfile, installs its packages into this project's renv library, and generates .Rprofile plus renv/activate.R. Subsequent R sessions started in the project root activate that library automatically. Package versions come from renv.lock. The script does not snapshot or update the lockfile. Internet access and, where binaries are unavailable, an appropriate compiler toolchain are required.

If the project is inside Dropbox, create renv as an empty directory and apply and verify com.dropbox.ignored before running restore. A portable clone outside a synchronized folder needs no Dropbox-specific step. Keep renv/library and other generated package caches out of version control.

Then run:

    just check
    just simulation 400
    just analysis
    just figures

The supplied wrapper uses the macOS/BSD script command to provide R with a pseudo-terminal. The file paths and renv environment are portable; on a system with a different script command syntax, adapt bin/rscript-pty to that system before using the recipes. Do not run the scripts with --vanilla or --no-init-file after restoring: those options skip the project activation file.

Commit the generated .Rprofile, renv/activate.R, renv/settings.json, and renv/.gitignore with renv.lock when maintaining an activated project. The restored library itself is rebuildable and should remain untracked.
