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

kmerdb profile sort order returns improperly sorted col2, col3 #113

Open
MatthewRalston opened this issue Feb 3, 2024 · 0 comments
Open
Assignees
Labels
bug Something isn't working good first issue Good for newcomers invalid This doesn't seem right
Milestone

Comments

@MatthewRalston
Copy link
Owner

The sort order is correct for col4 (i.e. descending counts) and col1 (fixed row number).

  • Col 2 should be the index number of the sort (so... it should be the original unsorted k-mer id, since sort order is descending by count, not by id.) Indeed it seems

  • col 3 should be just the k-mer id. (e.g. row 0 below: it should read [0, 65523, 65523, 1977, ...]

  • Upon inspection, row 3 sort order is mangled.

Suggestion: remove col 3 so new column order is

  • row number (fixed, ascending, 0 - 4^k)
  • k-mer id
  • count
  • frequency
========================

0	65523	700	1977	0.00048300326888403523
1	12	1395	1972	0.00048178171281705487
2	12288	330	1922	0.00046956615214725127
3	53247	34	1920	0.0004690775297204591
4	768	546	1849	0.00045173143356933796
5	65343	6046	1833	0.0004478224541550008
6	192	14642	1824	0.00044562365323443613
7	65331	659	1779	0.0004346296486316129
8	65487	201	1773	0.00043316378135123645
9	16380	1763	1768	0.0004319422252842561
10	51	1483	1768	0.0004319422252842561
11	3072	447	1762	0.00043047635800387964
12	65484	1	1756	0.00042901049072350324
13	49164	646	1738	0.00042461288888237395
14	48	270	1737	0.00042436857766897787
15	13311	95	1722	0.00042070390946803677
16	64767	533	1715	0.000418993730974264
@MatthewRalston MatthewRalston added bug Something isn't working good first issue Good for newcomers invalid This doesn't seem right labels Feb 3, 2024
@MatthewRalston MatthewRalston added this to the V0.7 stable? milestone Feb 3, 2024
@MatthewRalston MatthewRalston self-assigned this Feb 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

1 participant