Hi Ella,
What I meant is that the -V and -W options are not made to work
together. I would recommend just using --min_maf. In which sense are
your results using this method 'weird' ?
Best,
Nicolas
Ella wrote on 04/17/2017 03:19 PM:
> Hi Nicolas,
>
> Thank you for the quick reply. I think I might have been a little
> unlcear in my post, I'm not running with a vcf file as the whitelist.
> I've just taken the ID column from the VCF file (so, locus ID), to
> make the whitelist. The first few lines of my whitelist look like
>
> 13_65
> 51_9
> 126_17
> 257_35
> 582_31
> etc...
>
> I ran populations using the built in -maf, but got strange results.
> Since I have had problems with this filter in older versions of
> stacks, and have had success filtering for -maf using vcf tools (and
> then creating a whitelist using locus ID from the recoded vcf file,
> which I have then used to re-run populations), I want to compare the
> results that I get using both the built in and external approaches.
>
> Do these locus ids look normal (i.e., is there always an underscore in
> them now), or is this due to having denovo-aligned data? My vcf files
> generated in older versions of stacks, using reference-aligned data,
> do not have underscores, and thus match exactly with locus ids that
> are in the other stacks output files (i.e., matches, alleles, etc...).
>
> With thanks,
> Ella