Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Duplicate arc appears for each junction using example_run.sh #97

Open
britney-chu opened this issue Jan 17, 2024 · 1 comment
Open

Duplicate arc appears for each junction using example_run.sh #97

britney-chu opened this issue Jan 17, 2024 · 1 comment
Labels

Comments

@britney-chu
Copy link

britney-chu commented Jan 17, 2024

Hello,
I have recently cloned the most recent version of ggsashim (1.1.5) and created a conda environment with the env-r3.4.1.yml file. I then ran example_run.sh . It returned an error that I was missing pysam (I guess this doesn't come with the conda environment). After installing Pysam (v0.16.0.1) I ran example_run.sh again and it created a plot with two arcs for each junction, one above and one below.
my_ggsashimi_1_17.pdf

Any ideas of how to fix this?
Thanks!

@oliverking
Copy link

I likewise got duplicate arcs for the first plot in example_run.sh (the one with -O set but not -A), using both conda and the pre-built docker container. Based on a quick attempt to isolate the problem it seemed that the data.table aggregation commands that construct multi-sample labels for arcs in -O mode result in multiple rows for each arc since rows are not being collapsed along the "count" column when -A is not set (i.e., when "%(args.aggr)s" == ""):

junctions = setNames(junctions[,.(max(y), max(yend),round(%(args.aggr)s(count)),paste(jlabel,collapse=",")), keyby=.(x,xend)], names(junctions))

junctions = setNames(junctions[,.(max(y), max(yend),round(%(args.aggr)s(count)),paste(jlabel,collapse=",")), keyby=.(x,xend)], names(junctions))

I made an attempt to fix this issue in the fork at https://github.com/oliverking/ggsashimi, and this seems to work for the example plots, but I caution that I have not tested this change thoroughly, and have also not read though all the code, so don't know whether these changes might cause problems in other contexts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants