systemPipeShiny
Bioc currentsystemPipeShiny: An Interactive Framework for Workflow Management and Visualization
Release Lineage
Entered 3.12 · Oct 28, 2020
Current · Requires R 4.6
Description
systemPipeShiny (SPS) extends the widely used systemPipeR (SPR) workflow environment with a versatile graphical user interface provided by a Shiny App. This allows non-R users, such as experimentalists, to run many systemPipeR’s workflow designs, control, and visualization functionalities interactively without requiring knowledge of R. Most importantly, SPS has been designed as a general purpose framework for interacting with other R packages in an intuitive manner. Like most Shiny Apps, SPS can be used on both local computers as well as centralized server-based deployments that can be accessed remotely as a public web service for using SPR’s functionalities with community and/or private data. The framework can integrate many core packages from the R/Bioconductor ecosystem. Examples of SPS’ current functionalities include: (a) interactive creation of experimental designs and metadata using an easy to use tabular editor or file uploader; (b) visualization of workflow topologies combined with auto-generation of R Markdown preview for interactively designed workflows; (d) access to a wide range of data processing routines; (e) and an extendable set of visualization functionalities. Complex visual results can be managed on a 'Canvas Workbench’ allowing users to organize and to compare plots in an efficient manner combined with a session snapshot feature to continue work at a later time. The present suite of pre-configured visualization examples. The modular design of SPR makes it easy to design custom functions without any knowledge of Shiny, as well as extending the environment in the future with contributions from the community.
None published for Bioconductor
Test coverage
Line coverage
–
Expression
–
Tests / Examples
–
Functions
122 16 exported
Complexity
4.9 avg / 58 max
Call network
122 nodes / 133 edges
Test coverage is not measured for Bioconductor packages; nodes fall back to a neutral fill.
Call graph
Open call graph →Lowest coverage
Per-function coverage is not measured for this package yet.
Code
Structure
Lines of code
16,697
Files
180
Compiled share
0%
Has compiled src
No
Language breakdown
API
Exported functions
19
Internal functions
106
Testing
Has tests
Yes
Test-to-code ratio
0.03
testthat edition
3
Docs
Roxygen coverage
100%
Health & Security signals
Informational signals; not verdicts.
on.exit coverage
46.2%
Unsafe pattern score
5
Dep constraint coverage
17.1%
Secret pattern count
0
Bundled 3rd-party code
2 items
Portability & License
Min R version
4.0.0
System requirements
–
C++ standard
–
License
GPL (>= 3)
License flags
SPDX valid, OSI approved
History
Versions
12
First release
2021-03-15
Latest release
2026-04-28
Avg cadence
181 days
Cold removal rate
–
Dep drift
4
LOC over versions
Per-file churn detail lives in the source pipeline: https://github.com/r-observatory/bioc-code-metrics.
Documentation
- Help pages
- 16
- Examples that run
- 94%15 run in a plain check (8 of them under a condition) · 1 hold no code
- Exported functions with examples
- 100%
- Documented parameters
- 97%
- Return-value docs
- 81%
- Help pages citing references
- 0%
- systemPipeShiny HTML
Repository practices
5 development-tooling and community-health practices detected across 3 families in the upstream repository
Checks run against github.com/systempiper/systempipeshiny on 2026-10-21.
The R CMD check workflow runs on Linux, macOS and Windows
GitHub Pages site last deployed 2021-02-17
Topics
People
- Le Zhang author maintainer
- Daniela Cassol author
- Thomas Girke author
- Gordon Mosher author
- Ponmathi Ramasamy author
- Jianhai Zhang author
Cite
Cite this package
Run in R for the authors' entry:
citation("systemPipeShiny")The package provides a citation file, so citation() returns the authors' own entry.
It points to 10.7490/f1000research.1118073.1.
Cite the R Observatory
For a number measured here: a download total, a coverage figure, an archival date.
From data release v2026-10-25, which the citation names so these numbers can be found later. More on citing and the projects behind them.