-
Notifications
You must be signed in to change notification settings - Fork 12
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
CRAM support #11
Comments
Hi @ppararaj , Thank you for your interest in our tool. We don't currently have support for CRAM files and we don't have immediate plans to add this support (at least for now). What we do plan is to add an options for users to provide coverage counts from 3rd party tools and then just apply our GC and mappability correction (hoping to post updates here soon: #12 ). An (often superior) alternative to the coverage correction offered by fragCounter is using dryclean. Dryclean works well with uncorrected read depth counts. There are many tools that offer fast coverage depth computations, for example: megadepth If you are using fragCounter because you wish to use JaBbA, then you can use a tool of your choice for coverage depth calculation and supply that as input for JaBbA (with or without dryclean processing). |
We're working with @mskilab on a meta-analysis of lymphomas. This is a show-stopper for us at the moment. Any thoughts on when this new functionality will become available? |
Hi Ryan- I think cram support should be pretty easy to implement. I think can have it by Monday?
Marcin
…________________________________
From: rdmorin ***@***.***>
Sent: Thursday, July 8, 2021 11:53 AM
To: mskilab/fragCounter
Cc: Marcin Imielinski Laboratory; Mention
Subject: Re: [mskilab/fragCounter] CRAM support (#11)
We're working with @mskilab<https://github.com/mskilab> on a meta-analysis of lymphomas. This is a show-stopper for us at the moment. Any thoughts on when this new functionality will become available?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#11 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AC73JEIZRCYNN4LLAIYSNB3TWXCWVANCNFSM477N3RIA>.
|
That would be great. Thanks Marcin! |
hi all - just added cram support and pushed to master --> please give it a spin and let us know! You will need to reinstall mskilab/bamUtils as well. Best-Marcin |
Hello, |
Great
…On Sat, Jul 10, 2021 at 12:12 PM Prasath Pararajalingam < ***@***.***> wrote:
Hello,
I've tested the new feature on a some GRCh37 CRAM files and it appear to
work without issue. Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC73JEOO5RCV4LGD5RG6VUDTXBWOPANCNFSM477N3RIA>
.
|
Hello,
Thanks for the software. I was able to successfully run this on a several BAM files, but I was wondering if there are plans to include support for CRAM format?
I receive the following error when trying to run a CRAM file and looks like a modification of bamUtils will be required:
The text was updated successfully, but these errors were encountered: