-
Notifications
You must be signed in to change notification settings - Fork 7
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
Making looper approachable for a new project #466
Comments
I started a PR to polish the I've also created a PR to begin staging documentation changes for Looper 2.0.0 here: pepkit/pepspec#34 The combination of these two PRs should close this issue with a 2.0.0 release. |
Prompt user to create pipeline interface if it doesn't exist to make this even easier. |
Have tutorial remind user that they add additional pipeline interfaces if desired. Or add another loop to keep adding them. |
|
for tutorials, we have: hello looper, but we need: tutorial on "your own project" (looper init tutorial). |
Ok, I've added some improvements to the |
I find the current documentation on how to configure a new project with looper to be really difficult. There are basically 2 problems:
It needs to be intuitive enough that we don't need so much documentation, and then, whatever minimal documentation remains needs to actually be correct.
Documentation
Just a few things I notice at first glance:
https://pep.databio.org/looper/pipestat/
Getting started
I propose a new
looper init
utility that walks you through the process of creating a new looper project. I'll push an example script that will do this. I have it basically working, but I haven't been able to finish the pipestat configuration, which is too complex. It's not clear to me how looper and pypiper should share pipestat configuration. It seems like I should just configure pipestat, I guess in the.looper.yaml
file, and that should be it.looper init
and it will walk you through creating a config correctly.The text was updated successfully, but these errors were encountered: