check fixes

R/runSimulation.R

@@ -4,7 +4,8 @@
 #' design conditions, and number of replications. Results can be saved as temporary files in case of
 #' interruptions and may be restored by re-running \code{runSimulation}, provided that the respective temp
 #' file can be found in the working directory. \code{runSimulation} supports parallel
-#' and cluster computing (with the \code{parallel} and \code{future} packages; see also
+#' and cluster computing (with the \code{\link[parallel]{parallel}} and
+#' \code{\link[future]{future}} packages; see also
 #' \code{\link{runArraySimulation}} for submitting array jobs to HPC clusters),
 #' global and local debugging, error handling (including fail-safe
 #' stopping when functions fail too often, even across nodes), provides bootstrap estimates of the
@@ -121,7 +122,7 @@
 #' @section A note on parallel computing:
 #'
 #' When running simulations in parallel (either with \code{parallel = TRUE}
-#' or when using the \code{\link{future}} approach with a \code{plan()} other than sequential)
+#' or when using the \code{\link[future]{future}} approach with a \code{plan()} other than sequential)
 #' R objects defined in the global environment will generally \emph{not} be visible across nodes.
 #' Hence, you may see errors such as \code{Error: object 'something' not found} if you try to use
 #' an object that is defined in the work space but is not passed to \code{runSimulation}.
@@ -482,7 +483,7 @@
 #'   is going wrong in the generate-analyse phases. Default is 50
 #'
 #' @param ncores number of cores to be used in parallel execution (ignored if using the
-#'   \code{future} package approach). Default uses all available minus 1
+#'   \code{\link[future]{future}} package approach). Default uses all available minus 1
 #'
 #' @param save logical; save the temporary simulation state to the hard-drive? This is useful
 #'   for simulations which require an extended amount of time, though for shorter simulations