You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just wanted to make note that currently in the assignTaxonomy function there is an error that results in a memory overflow if you input a a very small sequence. I noticed this because I accidentally was making synthetic reads and included a sequence that was only 4 base pairs long.
When I ran the command I kept getting out of memory errors and eventually was able to track it down to not filtering out very small reads. However, afterward I tested running the command with just my small 4 base pair long sequence and was able to reproduce the bug.
Well I know this isn't a common issue and probably isn't a priority I wanted to highlight it incase others run into it or if there is a simple fix for this in the future.
Thanks for continuing to support this software!
Cheers,
Jacob Nearing
The text was updated successfully, but these errors were encountered:
Thanks. Any sequence less than the kmer size (8) will break the code. There is a check for short sequences on the reference database size, but I guess there isn't one on the query sequence side. That should be added.
Hi Ben and team,
I just wanted to make note that currently in the assignTaxonomy function there is an error that results in a memory overflow if you input a a very small sequence. I noticed this because I accidentally was making synthetic reads and included a sequence that was only 4 base pairs long.
When I ran the command I kept getting out of memory errors and eventually was able to track it down to not filtering out very small reads. However, afterward I tested running the command with just my small 4 base pair long sequence and was able to reproduce the bug.
Well I know this isn't a common issue and probably isn't a priority I wanted to highlight it incase others run into it or if there is a simple fix for this in the future.
Thanks for continuing to support this software!
Cheers,
Jacob Nearing
The text was updated successfully, but these errors were encountered: