⚠️ pandoc
“file not found in resource path” when rendering Rmd on HPC (e.g., generating HTML reports with eyeris::bidsify()
)
#225
shawntz
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
This note is for users rendering R Markdown on HPC environments where
pandoc
is centrally installed (e.g., via shared software modules) and encounter errors like the one below when generating HTML reports usingeyeris::bidsify()
:This issue is especially likely when using
--self-contained
HTML rendering withrmarkdown::render()
, which is the methodeyeris::bidsify()
uses to generate its HTML reports.Cause
In many HPC setups,
pandoc
is an older version (e.g.,v2.7.3
), and files like CSS, JS, or figures referenced from within a package or user directory are not accessible or get dropped during the rendering pipeline.In my own testing, I’ve frequently encountered this issue when:
--self-contained
flag (as set by default inrmarkdown::render()
)For example, on Stanford’s Sherlock HPC, users are encouraged to load software via shared modules, yet the only available
pandoc
version isv2.7.3
, which is quite outdated 😭.Solution / Workaround
pandoc
, which at the time of this writing isv3.1.11.1
:eyeris
commands. This ensures the R Markdown render engine uses your locally installed version ofpandoc
:And voilà, the
eyeris
HTML reports should now generate on your headless HPC setup! Hope this helps anyone else running into similar issues with pandoc rendering in constrained environments.If you encounter related problems or discover cleaner workarounds, feel free to comment here so others can benefit. 🧠💡
This issue is being left open as a searchable note but is not something that requires a fix within the package itself.
Beta Was this translation helpful? Give feedback.
All reactions