-
Notifications
You must be signed in to change notification settings - Fork 6
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
Separate pipeline from pyrenew #208
Comments
Once the pipeline-description content is moved out of |
I made this issue with the intention of removing the pipeline folder and eventually putting the pipeline in a separate repository, but I'm not completely committed to that plan. Regardless, we have no pipeline at the moment, so I don't see the point of having a pipeline folder. |
Agree, for now.
There is probably a better way but something akin to what you have mentioned seems good. |
Additional context: it now seems like there will be multiple models (Flu and Covid) using PyRenew, so I think those should probably be separate projects / repos. Having both those pipelines and the package code all in one repo seems messy. |
At this point, I think separating the pipeline from pyrenew only amounts to removing the nearly-empty
pipeline
folder and references to it in thereadme
s.The text was updated successfully, but these errors were encountered: