We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Say peppy offered a project_modifiers.imply, which is exactly the same as the sample_modifiers version but operates on a project. Then, I could do:
project_modifiers.imply
sample_modifiers
name: global looper pipeline interfaces pep_config: 2.0.0 project_modifiers: imply: if: pep_type: [ATAC, ATAC-seq, DNAse, blah, blah, blah] then: looper.pipeline_interfaces: [x.yaml, y.yaml, z.yaml]
Originally posted by @nsheff in pepkit/looper#244 (comment)
The text was updated successfully, but these errors were encountered:
One complexity: referring to things with looper.pipeline_interfaces, or implying structured attributes instead of just strings...
looper.pipeline_interfaces
Sorry, something went wrong.
another thought: if we go this route, do you think you'd want amendments and imports to fall under project_modifiers ?
amendments
imports
project_modifiers
the it'd be:
project_modifiers: amend: ... imply: ... import: ... sample_modifiers: append: ... imply: ... derive: ... ...
No branches or pull requests
Say peppy offered a
project_modifiers.imply
, which is exactly the same as thesample_modifiers
version but operates on a project. Then, I could do:Originally posted by @nsheff in pepkit/looper#244 (comment)
The text was updated successfully, but these errors were encountered: