-
Notifications
You must be signed in to change notification settings - Fork 13
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
Problem opening input.bcf -- No debug log #30
Comments
Note, I tried the same thing with a |
Trying this command instead:
Which is even weirded, since the |
Apologies for the confusing error message. AKT requires indexed files so if you best, Jared |
Hmh, It might be that I converted to bcf poorly, since I got different error after doing that. However, I tried converting my original file (
However upon running:
(Same issue if I use Is this to be expected if my It does contains 150 or so SNPs that are Y-chromosome haplogroup related, so I assumed this would be correct. Or might there be something wrong with he way I did my indexing ? |
What reference genome are you using? You need this to be consistent with the version in |
I am using a VCF I got from datnte's lab ~10 months ago. Is there a standard way to check the "versioning" on those ? I'm not to familiar with the file format to be honest, every time I think I understand how it works something pops up and I realize I don't. |
I seem to have gotten matches on some (130 sties) with Do you have any further documentation that explains the difference between the files and why matches might be found only on some of those ? Anyway, thanks for all the help, hopefully I can handle the rest from here :) |
I converted a vcf to bcf and tried running your tool with the following command:
./akt pca -W data/wgs.grch37.vcf.gz input.bcf
The only logs I get are:
Is see no debug option to make this message more verbose and figure out what the issue is, does a flag for verbose output exist ?
I don't believe the problem is permission related, here's the
stats
output forinput.bcf
:The text was updated successfully, but these errors were encountered: