-
Notifications
You must be signed in to change notification settings - Fork 95
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
Issue with the detection of deletions that I see are visible #504
Comments
Are you using short or long-read sequencing? How long is your deletion? If the deletion is more than 60% of the length of your region in -f file, it won't align and will be discarded. You can change this behavior with the parameter --default_min_aln_score. CRISPRessoWGS will only include reads that completely span the region in your -f file. It does this by chopping all reads down to start and end at the regions in your -f file. Unfortunately, if the start or end is deleted, the read may not be included. Could this be the case? Is the deletion completely in your -f region or does it overlap? Alternatively, you can try this branch: https://github.com/pinellolab/CRISPResso2/tree/wgs-whole-region-deleted which allows for analysis when the start or end (or the whole region) is deleted. We're still testing this branch, so if you have any feedback, that would be great. Otherwise, these are the steps I'd take to debug:
Feel free to reach out if you need additional help or want to walk through this together - [email protected]. |
Hi @kclem , thank you for the response. Here is a segment of the reads -- there are more below that are not visible in this screenshot. They are short reads and the reads do span the whole region - however the deletion extends past the target region. I am using BAMs not fastqs also as my input. Thank you! The red indicates the target region, and the deletions seen in the ifrst few reads are not being counted). All these reads where in the ANALYZED_REGIONS folder for the associated region so they seemed to make it in the ANALYZED_REGIONS/*.bam, but when I look and the "deletions" stats in the SUMMARY txt file, I only see a deletion of 1 |
Hi @tanyasarkjain, Yes, it looks like the reads are being discarded because they deletions are not contained within the region. Can you expand your window to include the bases surrounding the deletion? Are you able to try this branch which allows these types of reads? https://github.com/pinellolab/CRISPResso2/tree/wgs-whole-region-deleted |
Well the deletions start within the region, but they do extend outward -- is this not counted? Are there no extra parameters I can include to allow crispressoWGS to consider deletions that extend beyond the window? If I expand the window, some reads that extend across the current region of interest are disregarded as those reads may not span the new window which is larger, which is why I don't want to just expand the window. Im having trouble trying out that branch when I try to clone the repo checkout and install it using setup.py, im getting error messages. Also, on another note - i have 15,000 locations I want to look at. Is there a way to parallelise crispresso WGS? |
|
I am okay with the deletions that extend beyond the the region not citing the correct deletion length - I am more interested in if there is a deletion or not. Does Crispresso (for amplicons) work in the exact same way? I am having trouble with the installation for this branch. I was running python setup.py install and was getting the below error message. Running this on my HPC which has python 3.11 installed. My cluster does not have 3.8 installed
|
@tanyasarkjain Could you check to see if |
Installed it but unfortunately still getting errors when i run python setup.py install:
|
Thanks for trying that! I would try next to install |
Numpy was already installed with version 2.1.3 |
Thank you, which version of CRISPResso are you trying to install? There was a recent breaking change between the numpy versions. If you aren't on the current master branch, I would recommend pulling that and trying to install it that way. |
I am trying to install wgs-whole-region-deleted because of the aforementioned reasons where deletions in the current master branch version aren't calculated in the way that's ideal for my analysis |
Sorry about that, I see the issue! Could you try this branch https://github.com/edilytics/CRISPResso2/tree/wgs-whole-region-deleted-v2.3.1 which has fix you are looking for and is compatible with numpy v2.1.3? Alternatively, you could try installing numpy 1.26.4 while still using the branch you are on. Please let me know if either of these options work! |
Thanks - I will try that. To clarify how the ANALYZED_REGIONS are produced -- is it correct that the reads are trimmed to all which span the region of interest? So those BAMS in ANALYZED_REGIONS should contain all those reads? |
Yes, ANALYZED_REGIONS contains reads that spanned the region of interest, but trimmed to only contain the sequence in the region of interest (not the whole read) |
Is that correct? When looking at the reads on IGV they extend beyond my 23 bp regions of interest I put, making it seem like the read was not trimmed. (see above screenshot) |
Was the screenshot above from your ANALYZED_REGIONS bam file? I though the IGV screenshot above in your third was raw data. |
yes it was |
Describe the bug
Hi I am running:
CRISPRessoWGS -b "reads.bam -f vegfa.tsv -r hg38.fa --name "output" --exclude_bp_from_right 0 --exclude_bp_from_left 0 --quantification_window_size 10 --min_frequency_alleles_around_cut_to_consider 0.001
Expected behavior
Visually looking at the produced ANALYZED_REGIONS folder, I can see there is a deletion that goes into the target site in my tsv, (the target site is 20bp) however, the deletions are not being counted when I look at the indels, perhaps because it goes beyond the target region. However, even after extending --quantification_window_size 10, and the target location to span the entirety of the deletion, it is still not being identified. Is there another parameter I should be running?
The text was updated successfully, but these errors were encountered: