-
Notifications
You must be signed in to change notification settings - Fork 19
Some questions about input file making #73
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 8000 of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi, pos contains the list of sites you want to impute. One potential source of that is after initial variant calling and filtering. If you have a VCF list of sites you can make the pos file using code something like the following, possibly changing the header to match what's asked for
The site "3 42331 A G,T" will not be accepted by STITCH as STITCH can only impute bi-allelic variants for now. So you could do "3 42331 A G" or "3 42331 A T" but not both G and T Best, |
Hi, Thanks for your answer, but I have another question: Best, |
HI, I have the same issue, how did you solve it. Thanks, |
I think in this instance, I would just split the file into one file per chromosome, and impute each chromosome seperately Something like
|
Hi, Thank you for your reply, and I also used the same way to deal with my files. Best, |
Hi Robbie,
I'm a little confused about pos files.
What did this file generate from those files? Is it a reference panel or a VCF file after variant calling?
But if it is generated from a VCF file after variant calling, is the site "3 42331 A G,T" removed?
Best
jennis
The text was updated successfully, but these errors were encountered: