-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Potential fix to allow QIIME2 with conda #835
Comments
Hi, So I tested this and the above label doesn't work
We can add |
Ofcourse, could just add |
thats unfortunately not acceptable because it doesnt fix the version.
that is better I think. I am not sure whether the https link or the envs dir would be better practice. |
yml file in ${projectDir}/envs/ seems safer, because the file at a random https adress could change or move at any time and will make the piepeline again unusable with conda. Copying will rely the pipeline only on bioconda, which seems a as better bet. |
Did you try including bioconda as a channel when you tried this? |
@SPPearce Yes I did, by creating an env file as mentioned in my reply to @d4straub . But with that version (2024.10.24) of qiime2 env I found a different issue while running the pipeline:
When I looked into the code, it was an issue with loading the phyloseq object. Though the latest version of biobase and phyloseq were in my env. I tried loading the phyloseq R library within the environment and got this error:
I'll try to first resolve this and if I'm unable to, I'll see which version of qiime2 works. |
Currently we use in ampliseq QIIME2 |
Yeah. I am running |
Why do you not just put that yml as the |
@SPPearce Because qiime is not a separate module; I thought since it's not required by every other file in the modules/local (like the dada2, barrnap, etc processes) it wouldn't make sense 🥲
|
Ok, that is a lot of local modules! Yeah, then what you've done seems fine. |
I'd forgotten that it is common for local modules to just be a .nf file on its own. |
Description of feature
Running QIIME2 with conda isnt allowed currently, beause no conda recipe was added to the pipeline. That might be a relict of the past, because QIIME2 org itself is maintaining and releasing a conda recipe at https://anaconda.org/qiime2/qiime2-amplicon. Potentially it works to add
qiime2/label/r2024.10::qiime2-amplicon
or such as conda package in QIIME2 processes hroughout the pipeline to make QIIME2 work with conda as well.The text was updated successfully, but these errors were encountered: