如何结合Rscript、commandArgs()与knitr处理带YAML参数的.Rnw文件？

Absolutely, you can make this workflow work—you just need to tweak how you structure your scripts and trigger the compilation. The core issue with your initial approach is that running Rscript script.Rnw params.yaml tries to parse the entire .Rnw file as pure R code, which fails because of the LaTeX syntax at the top. Here's a clean, reliable solution:

1. Split Your Workflow into Two Parts #

Instead of trying to run the .Rnw file directly with Rscript, create a separate R "driver" script that handles command-line arguments, loads your YAML params, and then tells knitr to process the .Rnw file. This keeps your LaTeX/R report clean and avoids syntax conflicts.

Step 1: Create the Driver Script (e.g., compile_report.R) #

This script will be the one you run via Rscript, and it manages the entire pipeline:

#!/usr/bin/env Rscript
args <- commandArgs(trailingOnly = TRUE)

# Validate input
if (length(args) != 1) {
  stop("Usage: Rscript compile_report.R path/to/params.yaml", call. = FALSE)
}

# Load required packages
library(knitr)
library(yaml)
library(tinytex) # Optional but recommended for portable TeX support

# Load parameters from YAML and make them available to knitr
params <- yaml::yaml.load_file(args[1])
assign("params", params, envir = globalenv())

# Compile the .Rnw to PDF in one step
# tinytex handles pdflatex runs automatically (no need to call it multiple times)
render(
  input = "script.Rnw",
  output_format = "pdf_document",
  output_file = "project_report.pdf" # Customize your output filename here
)

Step 2: Adjust Your .Rnw File #

Remove the commandArgs() code from your .Rnw file—since the driver script already loads the params and makes them available globally, you can use the params variable directly:

\documentclass[12pt, a4paper]{article}
\usepackage[utf8]{inputenc}
\usepackage{hyperref}
\hypersetup{
 colorlinks = true, %Colours links instead of ugly boxes
 urlcolor = blue, %Colour for external hyperlinks
 linkcolor = blue, %Colour of internal links
 citecolor = blue %Colour of citations
}
\usepackage{caption}
\setlength{\parindent}{0pt}
\usepackage{authblk}
\usepackage[nomarkers, nolists]{endfloat} %Positions figures at the end of the document and add no list of names (requires that chunk have fig.cap option)
\usepackage{soul} % Allows underline lines to be broken (use \ul{} instead of \underline{})
\usepackage{helvet} %Set up Arial as font
\renewcommand{\familydefault}{\sfdefault}
\newcommand{\Rfunction}[1]{{\texttt{#1}}}
\newcommand{\Rpackage}[1]{{\textit{#1}}}
\title{\textbf{Report}}
\author{Author}
\date{\today}
\begin{document}
\maketitle
\begingroup
\hypersetup{linkcolor=black} % force independent link colours in table of contents
\tableofcontents
\endgroup
\begingroup
\hypersetup{linkcolor=black} % force independent link colours in list of figures
\listoffigures
\endgroup
\newpage
\section{Introduction}
This report blah blah blah
\newpage
\section{Results}
<<importing-lib, echo=FALSE, message=FALSE, cache=TRUE>>=
###################################################
# Use params passed from the compile driver script #
###################################################
setwd(params$workdir)

# Create required directories (cleaner with a loop)
result_paths <- c(
  file.path(params$workdir, "results", "edgeR"),
  file.path(params$workdir, "results", "gsea", "input_files")
)
for (path in result_paths) {
  if (!dir.exists(path)) {
    dir.create(path, recursive = TRUE)
  }
}

print(paste0("Hello from project: ", params$project_name)) # Example using a YAML param
@
\end{document}

2. Run the Workflow #

1. If you haven't already, install the required packages:

   install.packages(c("knitr", "yaml", "tinytex"))
   tinytex::install_tinytex() # Installs a portable TeX distribution (optional but great for consistency)
   

2. Make the driver script executable (optional, for Unix-like systems):

   chmod +x compile_report.R
   

3. Run the pipeline with your YAML params:

   # Option 1: Using Rscript
   Rscript compile_report.R params.yaml
   
   # Option 2: Direct execution (if you made it executable)
   ./compile_report.R params.yaml
   

Why This Works #

• The driver script acts as a middleman: it handles command-line input, loads your parameters, and then tells knitr to properly parse the .Rnw file (which knitr is designed to do—mixing LaTeX and R code).
• knitr::render() simplifies the process by automatically running pdflatex as many times as needed to generate correct tables of contents, figure lists, etc.
• Using tinytex ensures you have a consistent TeX environment across different machines, avoiding "missing package" errors.

Bonus: Alternative (No Driver Script) #

If you prefer to keep everything in the .Rnw file, you can use knitr::opts_knit$set() to pass parameters via the command line when calling knit, but the driver script approach is cleaner for most use cases. For example:

Rscript -e "library(knitr); library(yaml); params <- yaml.load_file('params.yaml'); knit('script.Rnw', envir = list2env(params))" && pdflatex script.tex && pdflatex script.tex

But this is harder to read and maintain compared to the driver script.

内容的提问来源于stack exchange，提问作者mf94