Skip to content
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

implement project_modifiers.imply #342

Open
stolarczyk opened this issue Apr 8, 2020 · 2 comments
Open

implement project_modifiers.imply #342

stolarczyk opened this issue Apr 8, 2020 · 2 comments

Comments

@stolarczyk
Copy link
Member

stolarczyk commented Apr 8, 2020

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:

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)

@nsheff
Copy link
Contributor

nsheff commented Apr 8, 2020

One complexity: referring to things with looper.pipeline_interfaces, or implying structured attributes instead of just strings...

@nsheff
Copy link
Contributor

nsheff commented Apr 8, 2020

another thought: if we go this route, do you think you'd want amendments and imports to fall under project_modifiers ?

the it'd be:

project_modifiers:
  amend: ...
  imply: ...
  import: ...
sample_modifiers:
  append: ...
  imply: ...
  derive: ...
  ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants