-
Notifications
You must be signed in to change notification settings - Fork 0
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
Resource handler #73
Resource handler #73
Conversation
Example pipeline: uclahs-cds/pipeline-call-gSNP#189 Steps to setup:
# Run this from a directory that doesn't contain a nextflow.config file as that may cause issues since Nextflow will automatically try to load it from the working directory
nextflow run /hot/software/pipeline/pipeline-Nextflow-config/Nextflow/development/unreleased/yashpatel-generalized-resource-handler/converter_pipeline/main.nf --config_dir /path/to/config/dir The pipeline will find and convert all node configs into a single
|
I think that should be |
Ah yes, I've edited the comment! |
Does it make sense that I'm having a problem with this line in
Although I'm also getting 'multiply' errors for other tools/processes that don't have |
These all had this error, F16 --exclusive
|
@uclahs-cds/nextflow-wg This is ready to be added as the initial version. Issues found through testing with a few pipelines have been addressed and the basic processing is working to be able to reproduce the current configurations. Specific test case with call-gSNP here: |
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 is really slick - nicely done!
I added some tests for this with #74 (a PR into this PR), but I'm fine with merging this as-is and adding tests later.
…e-handler Add tests for resource handler
I have read the code review guidelines and the code review best practice on GitHub check-list.
I have reviewed the Nextflow pipeline standards.
The name of the branch is meaningful and well formatted following the standards, using [AD_username (or 5 letters of AD if AD is too long)]-[brief_description_of_branch].
I have set up or verified the branch protection rule following the github standards before opening this pull request.
I have added my name to the contributors listings in the
metadata.yaml
and themanifest
block in thenextflow.config
as part of this pull request, am listedalready, or do not wish to be listed. (This acknowledgement is optional.)
I have added the changes included in this pull request to the
CHANGELOG.md
under the next release version or unreleased, and updated the date.I have updated the version number in the
metadata.yaml
andmanifest
block of thenextflow.config
file following semver, or the version number has already been updated. (Leave it unchecked if you are unsure about new version number and discuss it with the infrastructure team in this PR.)I have tested the config being added or modified. Outline the tests below.
Closes #...