-
Notifications
You must be signed in to change notification settings - Fork 8
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
Manhattan plots fail #25
Comments
Hi @Ax3man, Thank you for reporting this issue. You are right about the Would you mind sharing your SAM file output generated during I will also make the necessary changes regarding Best, |
Hi Kivanc, I'm getting the same error, I checked for the SAM output as you suggested and there wasn't one. All of log files in that directory were empty, except kmers_align.bowtie2.log, which read:
I'm assuming this is why the Manhattan plot isn't working, since the Manhattan plot error message is talking about an empty Series. Not sure why the SAM output isn't being created or why the Manhattan step is running without it, I will let you know if I track it down. Thanks, Cedar |
I've generated the SAM output, here are the first few lines:
I think the problem is that the regex in the |
Hi @cedarwarman, I had the same issue today and was able to continue making Manhattan plots by replacing this line:
with name = chromosome_name and it will let you go on with your own chromosome names. If you have many smaller contigs that you want to leave out, you'll have to tweak the regex yourself.
|
Hi Kivanc,
I've updated kGWASflow and tried to run the analysis including aligning the kmers. Unfortunately, generating the Manhattan plot yields errors, with unhelpful logs:
I don't really care about the manhattan plots, I can make those myself, but turning them off here didn't do anything. I tried to check, and as far as I can tell, that option does not appear to be used anywhere? Shouldn't the manhattan rule have an if statement like here?
I'll just continue without the aligned kmers, but thought I would let you know.
The text was updated successfully, but these errors were encountered: