Closed joergFLI closed 2 years ago
hi @joergFLI
Can you make sure the previous steps generated the expected output? ie check the files in the folder 2_assembly and 3_polishing_long_reads.
Can you post the content of /home/software/micropipe/work/9c/4e9530b090e3cb82616fbca91e3204/.command.sh?
Your error looks very similar to this one: https://github.com/Nextomics/NextPolish/issues/88 but you dont seem to have a typo in the file name. In the /work folder, files are expected to be links to raw data.
Dear vmurigneu,
for two samples all previous steps worked fine including flye polishedLR files with appropriate genome size. One sample has a file flye_racon_4.fasta but not flye_polishedLR. I cannot find a log for medakka. command.sh looks like this:
!/bin/bash -ue
set +eu ls 110712RA1944_S13_L001_R1_001.fastq.gz 110712RA1944_S13_L001_R2_001.fastq.gz > sgs.fofn echo -e "task = 1212 genome = consensus.fasta sgs_fofn = sgs.fofn multithread_jobs = 40" > nextpolish.cfg nextPolish nextpolish.cfg if [[ "1212" == "1212" ]] || [[ "1212" == "best" ]] ; then cat 01.kmer_count/polish.ref.sh.work/polish_genome/genome.nextpolish.part.fasta > 12RA1944_flye_polishedLR_SR_1.fasta cat 03.kmer_count/polish.ref.sh.work/polish_genome/genome.nextpolish.part.fasta > 12RA1944_flye_polishedLR_SR_2.fasta // rm -r 00.score_chain 01.kmer_count 02.score_chain 03.kmer_count elif [[ "1212" == "12" ]]; then cat 01.kmer_count/polish.ref.sh.work/polish_genome/genome.nextpolish.part.fasta > 12RA1944_flye_polishedLR_SR_2.fasta // rm -r 00.score_chain 01.kmer_count fi rm input.sgspart.fastq.gz cp .command.log nextpolish.log nextPolish --version 2> nextpolish_version.txt
Yes, I've seen this https://github.com/Nextomics/NextPolish/issues/88 but the file name seems correct and the link also has the correct target.
@joergFLI I am a little bit confused by the two lines starting //
in the paste above, as it also seems to be the last error in the original code block you pasted.
Are you please able to verify that lines 632 and 635 in your local 'main.nf' match those in the 'main' branch of this repo?
Just a reminder that in bash, you comment lines out with #
and not //
if that is the intent.
@thomcuddihy Also wonder why there was a //
in lines 632 and 635. To be sure, I used git pull to have the latest original code. Now commands.sh looks fine but the db_split error in NextPolish remains. The file nextPolish.sh.e does not exist this time.
The Problem might be quality of Illumina data. After installing NextPolish v1.3.1 from GIT and running using 3_polishing_long_reads as genome input, it says:
Too many[0.190859] reads contains N base, please do QC first.
When I trim reads using trim-galore both NextPolish and Micropipe work fine. Just wonder why I did not receive the same helpful error message.
Unfortunately as Nextflow involves multiple layers (container handling, data handling, process code e.g.), it sometimes does not immediately provide the lowest level of error stacks.
Instead one may need to investigate the contents of the process .command.log
file for more details (e.g. /home/software/micropipe/work/9c/4e9530b090e3cb82616fbca91e3204/.command.log
)
Hi, _nextpolish.log says
And the log /home/software/micropipe/work/9c/4e9530b090e3cb82616fbca91e3204/00.score_chain/01.db_split.sh.work/db_split0/nextPolish.sh.e says
However, file 110712RA1944_S13_L001_R1_001.fastq.gz does exist. Its basically a link to the raw data.
Thanks