Is there a way to specify where the conda environments during this command should be stored? Currently they are always written to the current directory (which I like to switch depending on the project). For example, the parameter --cachedir from the singularity runs could be used for that (tried parameter with conda, didn't change anything).
/work_beegfs/sunam162/NEXTFLOW/nextflow run /work_beegfs/sunam162/NEXTFLOW/MUFFIN/main.nf --output /work_beegfs/sunam162/NEXTFLOW/MUFFIN/test_out --cpus 10 -profile slurm,conda,test
Also, could you make singularity respect the --cpu parameter? In the readme you wrote, that I need to edit the configs/containers.config for that, but that only lists the versions per default, so no clue what to add there. And when I tried with --cpu 10, spades ran with 24 threads, not 10.
Hello!
Is there a way to specify where the conda environments during this command should be stored? Currently they are always written to the current directory (which I like to switch depending on the project). For example, the parameter --cachedir from the singularity runs could be used for that (tried parameter with conda, didn't change anything).
/work_beegfs/sunam162/NEXTFLOW/nextflow run /work_beegfs/sunam162/NEXTFLOW/MUFFIN/main.nf --output /work_beegfs/sunam162/NEXTFLOW/MUFFIN/test_out --cpus 10 -profile slurm,conda,testAlso, could you make singularity respect the --cpu parameter? In the readme you wrote, that I need to edit the configs/containers.config for that, but that only lists the versions per default, so no clue what to add there. And when I tried with --cpu 10, spades ran with 24 threads, not 10.