Closed marinachen closed 1 year ago
Hi @marinachen I've never seen this error before and I cannot reproduce this. This is the test sample, right? Can you try running it again and see perhaps the error disappears? If not, can you follow the "Tip" in the last line, go to the workdir /net/hutlab12/srv/export/hutlab12_nobackup/share_root/users/mchen/pb-16S-nf/work/2e/98738f98210e9901351a8d63d1e403
and type bash .command.run
and see if the command is able to complete?
Thanks.
Hi @proteinosome thank you for the suggestion! Yes this was the test sample step. It indeed disappears when I re-ran it, surprisingly.. I will try to run through your example ATCC mock community data to see if this or something else may occur.
I have another question that I see others have brought up in other issues before regarding the dag.overwrite problem (please see below). I'm currently just doing what you said about deleting or renaming the report_results folder every time before re-running, but do wonder if there's a better solution now? Thank you!
N E X T F L O W ~ version 22.10.6
Launching `main.nf` [maniac_brenner] DSL2 - revision: 4df4423694
DAG file already exists: /net/hutlab12/srv/export/hutlab12_nobackup/share_root/users/mchen/pb-16S-nf/report_results/dag.html -- enable `dag.overwrite` in your config file to overwrite existing DAG files
Hi @marinachen good to hear that.
For the DAG issue, the most straightforward way is to add overwrite = true
into the DAG scope in the config file nextflow.config
. E.g. it looks like this after modifying. I will probably set this as default in the next release.
dag {
enabled = true
file = "report_$params.outdir/dag.html"
overwrite = true
}
Hi,
I'm running this on HPC with singularity. I can't tell what caused this termination at the denoise step. I was following the documentation and everything before the test sample step works fine for me. Please help! Thank you!