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

testrun for region chr1:1000-2000 takes ages #205

Open
robertzeibich opened this issue Aug 17, 2023 · 2 comments
Open

testrun for region chr1:1000-2000 takes ages #205

robertzeibich opened this issue Aug 17, 2023 · 2 comments

Comments

@robertzeibich
Copy link

robertzeibich commented Aug 17, 2023

I just wanted to try mosdepth on some of my smaller deletions:

mosdepth --by <(echo -e "chr1\11869\t12227") mosdepth-test-out --d4 -t 4 -f $FASTA $BAMFILE

The command takes for ages. Do you know why?

@robertzeibich
Copy link
Author

robertzeibich commented Aug 17, 2023

I got the following output for the following region:

mosdepth-test-out.regions.bed.gz
chr1 11869 12227 78.96

Is 78.96 good?

Goal: I am just trying to generate some extra information to interpret/filter my smaller deletions, insertions and duplications. If you have a better idea, please let me know.

@brentp
Copy link
Owner

brentp commented Aug 17, 2023

--by just tells mosdepth that you want extra information for those regions or that region. But it must still read the entire chromosome. It's built to be fast on whole-file operations, not on select regions.

I think you can use duphold along with visual plots to evaluate smaller deletions. Duphold will be less reliable the smaller the event, but there should still be signal.

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

No branches or pull requests

2 participants