Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • ONT_pilot_gitlab ONT_pilot_gitlab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 13
    • Issues 13
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Wiki
    • Wiki
  • External wiki
    • External wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ESB
  • ONT_pilot_gitlabONT_pilot_gitlab
  • Issues
  • #112

Closed
Open
Created Dec 02, 2020 by Valentina Galata@valentina.galataMaintainer

Report/Figure: saving upsetr plots

Currently, the UpSetR plots are not saved to PDF (only in the rendered HTML report).

Use print(...) when creating plots to save them to PDF:

pdf(...)
print(UpSetR::upset(...))
dev.off()

Also, the plot object can be saved as the other plots and plotted later using print(...). At the moment, the plotting function is called in the rMarkdown files and the rendering script.

Edited Jan 12, 2021 by Valentina Galata
Assignee
Assign to
Time tracking