-
Notifications
You must be signed in to change notification settings - Fork 5
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
enable conda #120
enable conda #120
Conversation
|
@@ -110,7 +110,7 @@ profiles { | |||
podman.enabled = false | |||
shifter.enabled = false | |||
charliecloud.enabled = false | |||
channels = ['conda-forge', 'bioconda', 'defaults'] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why did this needed to be changed? It seemed at other locations it's still used as before?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to be a silent bug since dec 2022! I already posted this on slack: https://nfcore.slack.com/archives/CE5LG7WMB/p1714721754644179
Without the conda.
it is not considered for the creation of the environment! This is probably also an issue in nf-core/epitopeprediction! @jonasscheid
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
I tested -profile conda using the test_assembly_only test which should use most of the modules. Still some adjustments needed to be done to actually run the pipeline using conda.
PR checklist
nf-core lint
).nf-test test main.nf.test -profile test,docker
).nextflow run . -profile debug,test,docker --outdir <OUTDIR>
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).