-
Notifications
You must be signed in to change notification settings - Fork 11
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
REF: group-timepoints to create Dist1D[nestedOrdered] #78
Conversation
Linked to qiime2/q2-stats#21 |
Validator for Dist1D[Nested] here: qiime2/q2-stats#22 |
Thanks @lizgehret for taking a look at this. Let me know if you need any clarification! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
overall this lgtm @cherman2, just a couple of stray print statements that could be removed!
Thanks @lizgehret, |
Whoah, not sure what happened to CI here - setup & lint shouldn't be running twice. @cherman2 can you try pushing up another commit (maybe just fixing the lint error) to see if this was just a stochastic issue? |
Seems like that fixed it @lizgehret |
Hmm, this is interesting - your TypeMap looks identical to your T_subject, T_dependence one (which seems like it mirrors the use-case for this one). Were you getting these failures locally as well? |
I don't remember getting these failures when I marked the PR ready for review but I am getting them locally. Seems like the subject map is doing a check that I am not doing. I think the check is on line 230 of _engraftment.py edit: yup that was it |
New error and explanation... I apparently didn't hook up group to engraftment pipeline, so when we pass group into grouptimes in the pipeline it errors. I will fix this but It might take me a minute since this isn't as minor of an edit and im OOO. |
Gotcha, that makes sense - just ping me when you're ready for another round of review! |
Alright, I remembered why engraftment didn't get hooked up. I don't have the stats I need to use the pipeline effectively yet. So for now I think |
Roger that @cherman2, are you planning to do that in a separate PR? Or add to this one? |
Hi @lizgehret, |
SLAP! |
@lizgehret, This PR is ready for you! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this all generally lgtm @cherman2 - couple of super minor comments and then this will be ready to merge!
Co-authored-by: Liz Gehret <[email protected]>
Thanks @lizgehret |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, LGTM! 🚀
No description provided.