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

Error running Shorah.py, and seeking for help #61

Open
JingniHe opened this issue Jun 1, 2019 · 2 comments
Open

Error running Shorah.py, and seeking for help #61

JingniHe opened this issue Jun 1, 2019 · 2 comments
Assignees

Comments

@JingniHe
Copy link

JingniHe commented Jun 1, 2019

Hi, recently, I tried to use your tool " ShoRAH" to generate global reconstruction haplotypes, but I ran into some problems.

So I try to run the tool on Linux by using the command “./shorah.py -b sorted.bam -f ref.fa -w 48”. I generated the sorted bam file using BWA and SAMTOOLS, and the length of my read is 100.

At beginning, it would generate lots of files like this:
image

But then, it would run into an error showed as following:
Capture

It seems like something wrong with the codes, but I don't know how to fix this.

I sincerely hope for you suggestions and help. Thank you very much, and have a good day!

@DrYak DrYak self-assigned this Jun 21, 2019
@DrYak
Copy link
Member

DrYak commented Sep 3, 2019

Hello, could you please try with the empty_window branch mentionned in pull request #62 for issue #53 ?

(Or alternatively try the branch allocaholic ?)

We've fixed lots of bugs in these branches, perhaps it helps ?

@DrYak
Copy link
Member

DrYak commented Nov 1, 2019

Small update, there's an alpha release which contains these fixes in the releases

It has successfully worked around lots of the bugs one of our user was having.

Among other it also fixes a bug which is triggered by dot in the file name. From the blurred error message you've posted, I think this is what is happening in your case.

If you do not want to use alpha code, you can circumvent this specific bug by renaming your sequence from K03455.1 to K034455_1.

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