Hi David,
This question comes up pretty frequently on list. The last time I
answered it was here:
https://groups.google.com/d/msg/stacks-users/BJxvnQ79OG0/XKLw1L3wHgAJ
The output for the different Stacks export files (sumstats, genepop,
structure, VCF, etc) should all be identical with some small variation
possible due to different rules in the exported file format.
The loci printed in each formatted file is provided, so all it takes is
a little UNIX to find which loci are different between files if there
are any differences at all. As far as I know there are no bugs in the
Stacks output in terms of exporting the same loci.
At the very least, you need to identify which loci are in one file but
not the other.
The web interface will allow you to view each locus and see the
different genotypes by eye. You can compare what you see in the web
interface for a particular locus with what you find in the exported file.
If you can find an inconsistency, i.e. provide a test case, I will look
for a bug, but the likelihood of a bug is small (but not zero).
Best,
julian
David wrote:
> Hey guys,
>
> any progress on this? I have the same problem with STACKS 1:34... for me
> it's a minor difference (~2%) but it's a difference and I can't explain it!
> Any help appreciated!
>
> Cheers,
> David
>
>
>
>
> On Tuesday, February 16, 2016 at 12:08:35 AM UTC-5, Eleanor Bors wrote:
>
> Hi Kerin-
>
> Did you ever make progress figuring out the root of the
> discrepancies? I have a similar issue--I'm seeing a difference in
> the number of loci in (1) structure, (2) genepop, and (3) sumstats
> output files from the /populations/ programs. There are up to 2x as
> many loci in the summary statistics file than the others.
> Unfortunately this may be affecting my summary statistics
> calculations using different downstream programs.
>
> I have been running /populations /with the --write_single_snp flag
> and at first I thought that the difference in the # of loci in my
> sumstats file was because it contained loci that had more than 1 SNP
> while the other formats didn't. I /think/ I found a good way to