UpSetR icon indicating copy to clipboard operation
UpSetR copied to clipboard

when nsets set to 23, it takes too long to output pdf

Open 20182531027 opened this issue 3 years ago • 1 comments

I have 23 samples to find the differences among samples, when nsets was set to 10, 15, 19, it can soon formed result file; but when i adjust the nsets as 23, it has been seven days, but it still doesn't run out the result. will you be kind enough to tell me what's wrong with that? the UpSetR really makes me upset now. the code is as follow: upset(cq,sets.bar.color = "#56B4E9",order.by = "freq",empty.intersections = "on",nsets=23)

20182531027 avatar Apr 09 '22 16:04 20182531027

@20182531027 I had also observed speed problems as nsets increased. I fixed a few bottlenecks in PR #199, which drastically reduced the runtime for my use cases. You can install it locally with install_github() as below:

remotes::install_github("hms-dbmi/UpSetR#199")
## Downloading GitHub repo jdblischak/UpSetR@counter-rowsums

jdblischak avatar Nov 04 '25 16:11 jdblischak