-
Notifications
You must be signed in to change notification settings - Fork 10
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
TypeError: 'NonType object has no attribute '__getitem__' #8
Comments
Based on the fact that you have a target region @ 6:171054606-171055065, I'm guessing you are on hg19/Grch37 (Grch38 chr6 ends at 170805979). Are all of your input file parameters to annotate_windows on the same reference? Given failure at calc_window_mappability, it would specifically be one of the first three parameters (targets.bed, genome.fa, and/or mappability.bed). I'm curious if your chr9 offending region is also at the end. The error is likely the result of regions where one of your input files has a region not represented in the other(s). If it's not a reference mismatch problem, make sure that a) all BED regions match up and are contained in the genome.fa index, and b) that only standard chromosomes (1-22,X,Y) are represented. Sometimes having e.g. a decoy chromosome in one file could break this script, so make sure Thanks, |
Hi, I use such files: my target.bed: clamms.bed (from "data" folder): UCSC's mappability.bed part of the reference: hs37d5.fa.fai Which file is actually wrong?
and the last two printed variables, "
Thanks for any help |
Hi,
I try to use clamms to do CNV calling on our cohort of WES patients. At the annotate_windows.sh step I get the following error
Traceback (most recent call last): File "/media/Berechnungen/clamms/calc_window_mappability.py", line 54, in <module> while value[0] != window[0]: TypeError: 'NoneType' object has no attribute '__getitem__'
The script does its job until one specific entry in my regions.bed file. Here are the last lines processed:
6 170890177 170892276
6 170892593 170892835
6 170893143 170893314
6 170893387 170893780
6 170948694 170949624
The next lines would have been
6 171054606 171055065
7 182935 183108
7 183648 183814
7 192969 193804
7 193948 194180
When I delete the last entry of chromosome 6 (
6 171054606 171055065
) the script works until a position on chromosome 9. Is there any other way than deleting the error causing entrys to avoid this error?Thanks in advance
Stefan
The text was updated successfully, but these errors were encountered: