Answers.Body: <p>Think removing everything &lt; 0.05 from <code>1000g2015aug_all</code> column of ANNOVAR annotation file helps with this</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-03-16T14:43:35.283Z
Answers.Text: It's quite rude to add and accept only your own answer after people have attempted to help you, especially when your answer is incomplete and will not help others that may have the same question. I think I will stay away from your future questions and not attempt to help you, as you seem to do this a lot (evident from your pattern on biostars, where you also ignored others' help and only accepted your own half-baked answers)
Answers.UserDisplayName: Ram RS
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-03-16T19:59:42.247Z
Answers.Text: @RamRS you are not answering this OP's question only, but many other future users'. Keep answering, time and number of votes will point to the right answer.
Answers.UserDisplayName: zx8754
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-03-13T13:51:18.597Z
Answers.LastActivityDate: 2020-03-13T13:51:18.597Z
Answers.UserDisplayName: Zizogolu
Answers.Body: <p>Use VEP, ANNOVAR or snpEff to annotate your VCF file (I'd recommend combining your VCFs into a single file if they're single sample VCFs or are all comprised of samples from the same experiment/cohort). You can annotate the VCF file with 1000g (among a ton of other annotation sources). Once done, you can use <code>bcftools view</code> to subset the VCF as required.</p>
  
  <p>Or, you can subset the standalone 1000g VCF and pick regions with your frequency threshold, then you can use that regions file to subset your VCF file(s).</p>
  
  <p>Remember to left-align and normalize (and split multi-allelic records in) your VCF files so all comparisons can be done accounting for chr, pos, ref and alt fields.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-03-12T19:33:50.283Z
Answers.LastActivityDate: 2020-03-12T19:33:50.283Z
Answers.UserDisplayName: Ram RS
Body: <p>I have 15 .vcf files. I need to remove `common variants in the 1000 genomes database' appearing in at least 0.5% of the population</p>
  
  <p>Do you know from where I may start?</p>
  
  <p>Thank you so much</p>
  
Tags: <vcf><wgs><1000genomes>
Title: Removing common variants in the 1000 genomes database from .vcf
ThreadText: # Removing common variants in the 1000 genomes database from .vcf
  
  (Asked by: username_0 on 2020-03-12)
  
  I have 15 .vcf files. I need to remove `common variants in the 1000 genomes database' appearing in at least 0.5% of the population
  
  Do you know from where I may start?
  
  Thank you so much
  
  **Tags:** vcf, wgs, 1000genomes
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2020-03-12. Score: 4 | Accepted answer
  
  Use VEP, ANNOVAR or snpEff to annotate your VCF file (I'd recommend combining your VCFs into a single file if they're single sample VCFs or are all comprised of samples from the same experiment/cohort). You can annotate the VCF file with 1000g (among a ton of other annotation sources). Once done, you can use `bcftools view` to subset the VCF as required.
  
  Or, you can subset the standalone 1000g VCF and pick regions with your frequency threshold, then you can use that regions file to subset your VCF file(s).
  
  Remember to left-align and normalize (and split multi-allelic records in) your VCF files so all comparisons can be done accounting for chr, pos, ref and alt fields.
  
  
  ---
  
  ### Answer by username_0 on 2020-03-13. Score: -3
  
  Think removing everything < 0.05 from `1000g2015aug_all` column of ANNOVAR annotation file helps with this
  
  > **Comments:**
  > **username_1**: It's quite rude to add and accept only your own answer after people have attempted to help you, especially when your answer is incomplete and will not help others that may have the same question. I think I will stay away from your future questions and not attempt to help you, as you seem to do this a lot (evident from your pattern on biostars, where you also ignored others' help and only accepted your own half-baked answers)  
  > **username_2**: @username_1 you are not answering this OP's question only, but many other future users'. Keep answering, time and number of votes will point to the right answer.  
  
  ---
  
  