Skip to content
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

summary stats vs actual alignments #99

Open
wbsimey opened this issue Mar 27, 2018 · 1 comment
Open

summary stats vs actual alignments #99

wbsimey opened this issue Mar 27, 2018 · 1 comment
Assignees

Comments

@wbsimey
Copy link

wbsimey commented Mar 27, 2018

Hello,
I am getting different results from the summary stats code vs phyluce_align_get_only_loci_with_min_taxa code. Your tutorial shows the same numbers for both at 75% matrix, 913 alignments.
Is this expected? I noticed that you use the ".floor" method in the phyluce_align_get_only_loci_with_min_taxa code. Perhaps this is the difference?

The following table holds my numbers for ABySS. The velvet assemblies are even further off (I can't get Trinity to work on Ubuntu 16 with Java 1.8 even after installing the latest Trinity and editing python.conf).

Matrix % summary stats phyluce_get_loci
65% 914 alignments 847 alignments
75% 720 alignments 551 alignments
85% 398 alignments 194 alignments
@brantfaircloth
Copy link
Member

The numbers in summary stats are estimates (and the floor is what makes the difference). I need to fix this at some point...

@brantfaircloth brantfaircloth self-assigned this Mar 28, 2018
@brantfaircloth brantfaircloth added this to the 2.0 milestone Mar 28, 2018
@brantfaircloth brantfaircloth removed this from the 2.0 milestone Feb 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants