Open kdm9 opened 9 years ago
I have no plans to do anything on hashtable.{cc,hh}
.
@kdmurray91 anything you do would be much appreciated!
Also fasta_dump_kmers_by_abundance
and fasta_count_kmers_by_position
have similar issues. There's quite a tight correlation between places which don't catch NoMoreReadsAvailable
and those that still use get_next_read
.
Ditto to output_fasta_kmer_pos_freq
Will split this into two PRs: ensuring NoMoreReadsAvailable
is caught I'll do as part of #1017. I'll make another PR consigning get_next_read
to history, as I have time, but hopefully before 2.0 :smile:
Also consume_fasta_and_traverse
Sounds great!
Ping @kdmurray91 :-)
Ahh, forgot about this. Is anyone (read @ctb) going to mind if this is a post-2.0 issue?
Already tagged post-2.0 :-)
This is largely for my own reference, stuff I've discovered during #1016 and #1017:
Hashtable::consume_fasta_and_tag
doesn't useimprint_next_read
, or catchNoMoreReadsAvailable
consume_fasta_and_tag_with_stoptags
consume_partitioned_fasta
Should I try and at least catch
NoMoreReadsAvailable
in these functions as part of #1017, @mr-c or @ctb? (also, is @Blahah working on this code [lib/hashtable.{cc,hh}
])Cheers, K
(P.S., I'll add to the above list)