Pipeline principles and best-practice #216
Replies: 5 comments
-
If this is true why do we feel comfortable designing |
Beta Was this translation helpful? Give feedback.
-
Some notes: I think the first thing is what we might want from a good pipeline?
Now we could do much of this manually but ideally we would have tools to cover as much as possible. From what we have seen in the julia ecosystem it looks like none of the tools do all the things we might like but that some combination of |
Beta Was this translation helpful? Give feedback.
-
I think good check pointing (that may not be what we actually have) is aware of all the things that go into it so that it can' |
Beta Was this translation helpful? Give feedback.
-
I think this is part of the issue but the actual main issue with this approach is global variables |
Beta Was this translation helpful? Give feedback.
-
I think this is a good discussion item rather than an issue |
Beta Was this translation helpful? Give feedback.
-
There are a number of potential problems with the analysis pipeline as currently defined in the PR #213 .
This issue is trying to bring together a best-practice guide for making an analysis pipeline:
Tensions:
EpiData
object rather than re-declaring with parameters from inside the loop over specifications seems to open up an opportunity to have bugs such as accidentally passing in a mis-specified object.Any link to a decent analysis pipeline best practice guide?
Beta Was this translation helpful? Give feedback.
All reactions