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

.n_occupied() was implemented differently in hashbits and hashtable #562

Closed
qingpeng opened this issue Jul 23, 2014 · 3 comments · Fixed by #652
Closed

.n_occupied() was implemented differently in hashbits and hashtable #562

qingpeng opened this issue Jul 23, 2014 · 3 comments · Fixed by #652
Assignees
Milestone

Comments

@qingpeng
Copy link
Contributor

as discussed in #429 and #491

Also,in load-graph.py, '--report-total-kmers' option will print .n_occupied() as "Total number of k-mers".
In .info file, .n_unique_kmers() is printed as number of "unique k-mers".
This is confusing. I will look into this.

@qingpeng qingpeng self-assigned this Jul 23, 2014
@mr-c
Copy link
Contributor

mr-c commented Jul 30, 2014

Thanks @qingpeng

@mr-c
Copy link
Contributor

mr-c commented Sep 1, 2014

Any progress?

@mr-c mr-c added this to the 1.2 milestone Sep 1, 2014
@mr-c
Copy link
Contributor

mr-c commented Nov 6, 2014

Upon further review I see that we only count unique k-mers in hashbits. n_occupied merely tells you the number of bins occupied in the first table.

I am going to implement a CountingHash.n_kmers() function and update the scripts to use it instead of n_occupied().

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants