Open karl616 opened 6 years ago
Hi Karl,
I am sorry for the late reply but I did not see this message at all...
Your proposal sounds interesting, even more since there are plans to directly support bioconda in Nextflow (nextflow-io/nextflow#493).
For now we could test by using this workaround.
I would really appreciate if you share the bioconda environment file. About kentUtils
, I can confirm the required tools are the ones you identified (BTW, at some point only bedGraphToBigWig
will be needed).
Thanks
Yes, that looks very interesting.
For now we could test by using this workaround.
I think that is what I'm doing momentarily:
~/miniconda2/bin/conda create env -f grape-nf_environment.yaml.gz source ~/miniconda2/bin/activate grape-nf nextflow run -qs 1 -without-docker -w $outputFolder/work grape-nf --index $outputFolder/readIndex.tsv --genome $genomeFasta --annotation $transcriptAnnotation --steps mapping,bigwig,quantification --genomeIndex $genomeIndex $extraOptions source ~/miniconda2/bin/deactivate
This works with the attached environment:
This is a complete environment with all dependencies. Secondly, I wasn't able to add gtfToGenePred and genePredToBed with the correct versions. I tried to add them to bioconda, but get a compile error I'm not able to solve. The environment also contains nextflow; something that could also be put to question. Either how, it is a place to start.
Hi, I spent some time adding missing software versions to bioconda, which I have learned to know as an easy way to set up/install bioinoformatic software. I'm still running tests, but I think it seems to work just fine.
All recipes provided by bioconda is also provided as docker/singularity containers through biocontainers. There are also possibilities to generate multitool containers. Not sure if it is interesting, but it would relieve you of providing the docker images.