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

Possible overflow in ws.ls() #128

Open
jonwright99 opened this issue May 28, 2020 · 1 comment
Open

Possible overflow in ws.ls() #128

jonwright99 opened this issue May 28, 2020 · 1 comment

Comments

@jonwright99
Copy link
Contributor

Running ws.ls() on a wheat size dataset gives a truncated output without the kmer counter details;

Correct output (not wheat);
SDG Workspace
SequenceDistanceGraph SDG: 1024254 nodes, 1349282 links
Distance Graphs: 0
Paired Read Datastores: 1
Paired Reads Datastore pe: 168907918 reads
Paired Reads Mapper: 0 mapped reads, 0 unmapped
Linked Read Datastores: 0
Long Read Datastores: 0
Kmer Count Datastores: 1
KmerCounter pcrf_reads: index with 260546793 31-mers
Counts: 2
sdg: 543119471 total 31-mers
pcrf_reads: 28252065131 total 31-mers

Output for wheat;
SDG Workspace
SequenceDistanceGraph SDG: 19116679 nodes, 26420231 links
Distance Graphs: 0
Paired Read Datastores: 1
Paired Reads Datastore ei_pe: 3390968002 reads
Paired Reads Mapper: 0 mapped reads, 0 unmapped
Linked Read Datastores: 0
Long Read Datastores: 0
Kmer Count Datastores: 1

@jonwright99
Copy link
Contributor Author

I think this is a bug in the code. 'Kmer Count Datastores' uses the same value as 'Paired Read Datastores' in workspace::ls()

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

No branches or pull requests

1 participant