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
Hi,
First, thank for you tools. I run the biser on a genome assembly with 25 chromosome-level scaffolds and 1983 short contigs (the longest contig is ~ 300kb and the shortest is ~2kb). The biser run a long time (> 2 Days) and used up the memory (> 1 Tb). However, it takes a very short time on other genome with only 194 contigs.
So I try to use the SEDEF to analysis the genomes with a high number of contigs. I observed that SEDEF also required a substantial amount of time for short contigs processing. For instance, after performing SEDEF translation, the group 22 (consisting of more than 800 contigs) and group 23 (with over 300 contigs) took more than 48 hours to complete processing.
Will a large number of short contigs significantly increase runtime? Should I filter out shorter contigs (e.g., < 10kb)? Could you please provide some suggestions?
Thank You
The text was updated successfully, but these errors were encountered:
Hi,
First, thank for you tools. I run the
biser
on a genome assembly with 25 chromosome-level scaffolds and 1983 short contigs (the longest contig is ~ 300kb and the shortest is ~2kb). Thebiser
run a long time (> 2 Days) and used up the memory (> 1 Tb). However, it takes a very short time on other genome with only 194 contigs.So I try to use the
SEDEF
to analysis the genomes with a high number of contigs. I observed thatSEDEF
also required a substantial amount of time for short contigs processing. For instance, after performingSEDEF
translation, the group 22 (consisting of more than 800 contigs) and group 23 (with over 300 contigs) took more than 48 hours to complete processing.Will a large number of short contigs significantly increase runtime? Should I filter out shorter contigs (e.g., < 10kb)? Could you please provide some suggestions?
Thank You
The text was updated successfully, but these errors were encountered: