Closed lbiernot closed 1 year ago
Hi there, I assume the conda package lacks r-digest, while it is available in the container. Might have slipped all tests.
Could you please test appending to your nextflow command -c env.config -resume
where env.config
contains:
process {
withName: DADA2_MERGE {
conda 'bioconda::bioconductor-dada2=1.22.0 conda-forge::r-digest=0.6.30'
}
}
disclaimer: I did not test this and I use singularity, so I'm not sure that works, but I hope so.
edit: according to https://nf-co.re/ampliseq/2.4.1/usage#updating-containers it seems rather conda =
@d4straub thank you. What I actually did is that I've created conda envs with proper dependencies beforehand and pointed ampliseq nextflow processes to use them but you've shown me the right direction.
Glad it worked!
I aim to make that work out of the box, so could you help me out and let me know what those proper dependencies
were? Was it as above, any other components?
@d4straub for the moment adding r-digest=0.6.30 to DADA2_MERGE seemed enough but I'm actually precreating conda environments:
channels:
- conda-forge
- bioconda
dependencies:
- bioconda::barrnap 0.9
name: barrnap
channels:
- conda-forge
- bioconda
dependencies:
- bioconductor-dada2 1.22.0
- r-digest 0.6.30
name: bioconductor-dada2
channels:
- conda-forge
- bioconda
dependencies:
- bioconductor-biostrings 2.58.0
name: biostrings
channels:
- conda-forge
- bioconda
dependencies:
- bioconda::cutadapt 3.4
name: cutadapt
channels:
- conda-forge
- bioconda
dependencies:
- bioconda::fastqc 0.11.9
name: fastqc
channels:
- conda-forge
- bioconda
dependencies:
- bioconda::itsx 1.1.3
name: itsx
channels:
- conda-forge
- bioconda
dependencies:
- bioconda::multiqc 1.13
name: multiqc
channels:
- conda-forge
- bioconda
dependencies:
- pandas 1.1.5
name: pandas
channels:
- conda-forge
- bioconda
dependencies:
- bioconda::picrust2 2.5.0
name: picrust2
channels:
- conda-forge
- bioconda
dependencies:
- conda-forge::python 3.8.3
name: python
channels:
- conda-forge
- bioconda
dependencies:
- bioconda::r-tidyverse 1.2.1
name: r-tidyverse
channels:
- conda-forge
- bioconda
dependencies:
- conda-forge::sed 4.7
name: sed
channels:
- conda-forge
- bioconda
dependencies:
- bioconda::vsearch 2.21.1
name: vsearch
I'm planning to update these environment yaml files to include all packages as resolved and installed by conda but I didn't have time to do it yet.
Thanks!
That conda managing seems a considerable amount of time invested there, that was supposed to be solved by the pipeline. Instead I would recommend testing out containers such as with singularity or docker that provide fixed environments, see https://nf-co.re/docs/usage/installation#pipeline-software
Hi again, would you have time to test with
nextflow pull nf-core/ampliseq
nextflow pull nf-core/ampliseq -r dev
nextflow run nf-core/ampliseq -r dev -profile conda <your params>
whether that is resolved?
I think I fixed all issues with conda in dev, will be in the next realese. Let me know if you come across any other issues (I hope not and it works smooth for you)!
Description of the bug
The pipeline fails on DADA2_MERGE step. It's irrelevant which input files I provide. The pipeline used to work literally until yestarday evening. We are always running it in a clean environment where no nextflow pipeline was run before. It implies that nextflow downloads nf-core/ampliseq every time.
It seems that R-package digest is missing in DADA2 environment.
Command used and terminal output
Relevant files
No response
System information
nextflow=21.10.6 Hardware: desktop Executor: local Container engine: we've tested it both in docker container and on non-virtualized OS. Profile used to run ampliseq pipeline on nextflow is always conda. OS: Debian Buster nf-core/ampliseq: 2.4.0 and 2.4.1 same issue