Closed zhanxw closed 1 year ago
Firstly, please check file integrity with md5sum
after downloading the file. This should be the cause.
md5sum -c gtdb.kmcp.tar.gz.md5.txt
Then, for the search command you paste:
kmcp search --load-whole-db --threads 32 \
--db-dir /home2/xzhan9/data/reference/kmcp/gtdb.kmcp \
-1 data/SRR12397805_1.fastq.gz \
-2 data/SRR12397805_2.fastq.gz \
--out-file kmcp/SRR12397805.out \
--log kmcp/SRR12397805.log
I'd recommend add an extension of .gz
to the output file, so it would save a lot of space.
-out-file kmcp/SRR12397805.out .gz
kmcp search -h:
-o, --out-file string ► Out file, supports and recommends a ".gz" suffix ("-" for
stdout). (default "-")
I see, it is indeed a bug that occurs when searching using paired-end reads with one read shorter than the value of -m/--min-query-len
(30 by default).
Thank you. I will test and report back here.
kmcp search
now works perfectly.
I also take your advice to reduce output file sizes.
Thank you for developing kmcp.
Let's make it open, will close it after the release of the next stable version.
I used the latest
kmcp
(downloaded from GitHub) and GTDB database (downloaded from WeTransfer) to align FASTQ files. The command line waskmcp search --load-whole-db --threads 32 --db-dir /home2/xzhan9/data/reference/kmcp/gtdb.kmcp -1 data/SRR12397805_1.fastq.gz -2 data/SRR12397805_2.fastq.gz --out-file kmcp/SRR12397805.out --log kmcp/SRR12397805.log
kmcp
crashed on two machines (both have >128G memory).The input files,
SRR12397805_1.fastq.gz
andSRR12397805_2.fastq.gz
, were downloaded from NCBI SRA.The error messages were:
panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x7b1256]
.This crash bug happened randomly, as sometimes
kmcp search
can work perfectly fine.More relevant outputs: