-
Notifications
You must be signed in to change notification settings - Fork 8
IndexError: string index out of range #4
Comments
Thanks for the report. Can you please post the output of
and the output snpflip posts to stdout including the error message? Thanks, Endre |
Hi, I'm getting the same error as @M-Saleem
Here is the output from
Here is the output from
In case it is also helpful, here are all of the headings in my fasta file:
|
Might it be that the MT chromosome is called something else in your fasta? If you could send me the bim, I could debug it :) |
Thanks for reporting this btw! |
Hi Endre! Thanks for getting back to me. I think my problem was more related to missing data - I upped my missing data filter and everything was solved. Regarding the chromosome naming - is there any way to tell the program that 23 = X, 24 = Y, and 26 = MT? |
I should have a flag for such a map-file. A bit busy now, but will keep this issue open as a reminder. Glad to hear it worked for you :) |
Hi Endre, just wanted to provide an update. I was working further with the dataset and found the same problem, even after removing the missing data. Based on this data, the index out of range error might have something to do with the treatment of MT data. As an illustration:
This isn't actually a problem for me, as we're not analyzing the MT genome and I can just as easily remove it before running snpflip. But, I thought I'd post this for clarification. Thanks for the great program! |
Great work. Thanks. Ill give snpflip an update after I finish my PhD :) |
Hi there I have the same error but I have not been able to fix it by following the solutions suggested.
Info of my .bim file
and the headings of my .fa file
|
Would love to try to help. Could you send me the bim and fa or are they confidential? |
Hi Endre,
Sadly I can not send you the .bim file and the .fa file is quite big. You
can get the .fa file from the checkVCF tool page
https://github.com/zhanxw/checkVCF.
Would that help?
…On Mon, 10 Sep 2018 at 17:13, Endre Bakken Stovner ***@***.***> wrote:
Would love to try to help. Could you send me the bim and fa or are they
confidential?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAwULArOj7TIjeEH1G-w9x9vWSnUpsv_ks5uZhEkgaJpZM4RzqCI>
.
|
Yeah, but I do not use this software anymore because I haven't had use for
it. I'll keep this issue open as a todo, but I have lots I need to finish
before fixing this. It's not like I have a paper on SNPflip or anything :)
On Tue, Sep 11, 2018 at 2:00 AM Rodrigo Cánovas <[email protected]>
wrote:
… Hi Endre,
Sadly I can not send you the .bim file and the .fa file is quite big. You
can get the .fa file from the checkVCF tool page
https://github.com/zhanxw/checkVCF.
Would that help?
On Mon, 10 Sep 2018 at 17:13, Endre Bakken Stovner <
***@***.***>
wrote:
> Would love to try to help. Could you send me the bim and fa or are they
> confidential?
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#4 (comment)
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AAwULArOj7TIjeEH1G-w9x9vWSnUpsv_ks5uZhEkgaJpZM4RzqCI
>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQ9I0mA6UaXpVmbCmLSJA5RcesIt96_5ks5uZv0IgaJpZM4RzqCI>
.
|
I had the same issue, but I finally found out that I used a different genome reference. Once I switched to the right one it worked properly. |
Hi there I have the same error but I have not been able to fix it by following the solutions suggested. My fa.files |
I have the other issue. For example 1.3482100000000001 should be 1.348209 |
Get this error when using human_g1k_v37.fasta. Is there a log file that I can check the cause of this error?
The text was updated successfully, but these errors were encountered: