Open paulgarias opened 2 years ago
Hi Paul,
This is a Flye error that seems to be linked to a high read coverage (1017) which could confuse Flye, it is similar to this issue: https://github.com/fenderglass/Flye/issues/128
Here are some suggestions from the author of Flye: I suggest to try two more runs (i) metagenome mode (ii) normal mode with --asm-coverage 50 to use the longest 50x reads for disjointig assembly.
Cam you try to rerun after modifying the nextflow.config file line 90 to reduce the coverage for initial disjointig assembly: flye_args = "--plasmids" => flye_args = "--plasmids --asm-coverage 50" or using the metagenome mode : flye_args = "--plasmids" => flye_args = "--plasmids --meta"
Hope this helps. Valentine
HI, I keep having a similar issue. I don't receive the Warning: Expected read coverage is 1017 as Paul. It seems that the assembly:flye step is expecting assembly.fasta as an input file, but in the directory of this file, there is draft_assembly.fasta. Do you think this might cause the problem? I am attaching flye log and nextflow log flye.log .nextflow.log .
@maddne No the assembly.fasta is an output file of the Flye step.
The error is here:
OSError: [Errno 30] Read-only file system
Work dir: /home/bio/micropipe/micropipe/work/36/fa4934df1db68825ea7799ce4a2f88
Tip: you can try to figure out what's wrong by changing to the process work dir and showing the script file named .command.sh
Aug-03 16:58:48.309 [Task monitor] DEBUG nextflow.Session - Session aborted -- Cause: Missing output file(s) assembly.fasta
expected by process assembly:flye (Eco1948)
Can you check the content of .command.sh and .command.run inside the work dir?
@vmurigneu yes I can check the content them. They seem to appear hidden and I cannot upload them directly, so I copied the content into a txt file error.txt .
@maddne have you checked that you have permission to write in the output folder? Did the previous steps of the pipeline generated expected output (trimming, filtering)?
Can you send the command line used and content of nextfow.config please
I assumed that I had problems with permission however I changed the permission to the output folder to drwxrwxrwx, but this wasn't the case, because it was able to write files there. The previous steps Trimming and filtering worked like a charm and produced output and HTML report. Here are some reports: Eco1948_porechop.log trace.txt nextflow_report.txt s
Here is my command nextflow main.nf --samplesheet /home/bio/micropipe/micropipe/samples5.csv --fastq /home/bio/micropipe/micropipe/bact5/ --outdir /home/bio/micropipe/micropipe/results123/ --datadir /home/bio/micropipe/micropipe/bact5/
nextflow.config file was downloaded as in your repo and I only changed the cache folder for singularity at line 3
@maddne can you post the nextflow.config file line 3 please?
would you please be able to post the .command.run inside the work dir /home/bio/micropipe/micropipe/work/36/fa4934df1db68825ea7799ce4a2f88
I am working with a student who is having this issue with their execution of nextflow
Looking for some guidance on how to proceed.
Best, Paul