Closed ericvdtoorn closed 9 months ago
Hmm, I'm not sure of the exact reason. According to the error message, some input files might be truncated.
# check corrupted files
for f in SRR6468718.kmcp_humgut@*.tsv.gz; do \
gzip -t $f; \
done;
It's still running, but upon rechecking the logs I see that the last one wasn't done:
==> SRR6468718.kmcp_humgut@9.log <==
23:11:51.022 [INFO] -------------------- [main parameters] --------------------
23:11:51.022 [INFO] minimum query length: 30
23:11:51.022 [INFO] minimum matched k-mers: 10
23:11:51.022 [INFO] minimum query coverage: 0.550000
23:11:51.022 [INFO] minimum target coverage: 0.000000
23:11:51.022 [INFO] -------------------- [main parameters] --------------------
23:11:51.022 [INFO]
23:11:51.022 [INFO] searching ...
23:11:51.028 [INFO] reading sequence file: SRR6468718_1.fastp.fq.gz
23:25:33.126 [INFO] reading sequence file: SRR6468718_2.fastp.fq.gz
Also adding the output of running:
# check corrupted files
> for f in SRR6468718.kmcp_humgut@*.tsv.gz; do \
gzip -t $f; \
done;
gzip: SRR6468718.kmcp_humgut@9.tsv.gz: unexpected end of file
So that's the reason. You need to wait until all searching are done before merging :)
When merging the results of a number of
kmcp search
runs, I get the following output:It does produce the out-file, attached the header: