Hi. This may be normal as I'm assembling a fairly large genome (2.2gbase expected, may be as high as 4.4g if the assembly is fully diploid) from Canu-corrected PacBio reads ... but I wondered how long to give the kmer index sorting before giving up? Flye-modules is currently the only significant user process on a dedicated 380MB/56core assembly machine. Its been running with 32 threads for about 9 hours in the step "sorting kmer index". Looking at other logs in the Issues I see this step taking about 20 mins.
Hi. This may be normal as I'm assembling a fairly large genome (2.2gbase expected, may be as high as 4.4g if the assembly is fully diploid) from Canu-corrected PacBio reads ... but I wondered how long to give the kmer index sorting before giving up? Flye-modules is currently the only significant user process on a dedicated 380MB/56core assembly machine. Its been running with 32 threads for about 9 hours in the step "sorting kmer index". Looking at other logs in the Issues I see this step taking about 20 mins.
Log:
[2020-06-24 16:40:32] root: INFO: Starting Flye 2.7.1-b1590 [2020-06-24 16:40:32] root: DEBUG: Cmd: /data/aplatts/miniconda2/envs/flye/bin/flye --pacbio-corr ../****.correctedReads.fasta --out-dir /storage/aplatts/Hex_blue/flye --threads 32 --iterations 2 -g 2.2g [2020-06-24 16:40:32] root: DEBUG: Python version: 3.7.6 | packaged by conda-forge | (default, Jun 1 2020, 18:57:50) [GCC 7.5.0] [2020-06-24 16:40:32] root: INFO: >>>STAGE: configure [2020-06-24 16:40:32] root: INFO: Configuring run [2020-06-24 16:56:05] root: INFO: Total read length: 166116567500 [2020-06-24 16:56:05] root: INFO: Input genome size: 2200000000 [2020-06-24 16:56:05] root: INFO: Estimated coverage: 75 [2020-06-24 16:56:05] root: INFO: Reads N50/N90: 21797 / 8056