The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
gui_render_report()
could attempt to write knitr’s intermediate .knit.md file
into the installed package library directory (the default location
rmarkdown::render() uses for intermediate files, based on
the input template’s own location), rather than into a writable
temporary directory. This is invisible on most systems since users
typically have write access to their own package library, but violates
CRAN policy against writing outside tempdir(), and fails
outright on systems where the library is mounted read-only (as CRAN’s
Debian check systems now do). Fixed by explicitly setting
intermediates_dir and knit_root_dir to a
session-specific temporary directory; the function’s actual output file
location (supplied by the caller, e.g. Shiny’s own temp path during a
download, or a user-chosen path) is unaffected by this change. Verified
by reproducing the exact failure as a non-root user against a
read-only-permissioned package library, then confirming the fix resolves
it under the same condition.biocharkit’s new TGA
module (requires biocharkit >= 0.3.0):
gui_tga_curve(),
gui_tga_stages(), gui_tga_stages_batch(),
gui_tga_kissinger() in R/logic.R, following
the same column-mapping/validation pattern as the rest of the app.DT, grDevices, and
rmarkdown usage moved into real, independently-tested
R/ functions (gui_datatable(),
gui_snapshot_png(), gui_render_report())
rather than being used only inside the Shiny app script.biocharkit::find_ftir_peaks()
(see that package’s NEWS) that affected the new automatic peak detection
feature.run_biocharkit_gui() launches a local Shiny app
wrapping the biocharkit package.gui_read_excel() /
gui_list_sheets(), with interactive column mapping (no
coding required) for every analysis.These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.