Malcolm Barrett
Malcolm Barrett
Thanks for your suggestions here and elsewhere. I will take them into account when I revisit this chapter soon > Actually, I'm not entirely sure how confounders fit into this...
The real problem here is that this sentence is making you think we mean something other than what we say. I agree it needs to be reworked, but to be...
Yes so your feedback is still helpful because the wording is confusing, so thanks. For positivity, there should be a non-zero chance of treatment for both groups. But yes, the...
One thing from #310 that might be good: prefer `ifelse()`/`if_else()` over `case_when()` when just a single condition The big one in this PR, though, is `ifelse()` vs. `if_else()`. I hold...
> shortcutting `TRUE/FALSE` arguments with integers (which I don't think is the best pedagogy) I agree with this and we should add explicit testing to our list (as you changed...
@LucyMcGowan can be the tie-breaker for `ifelse()` vs. `if_else()`. I'll be ok with either
`ifelse()` might be the easiest find-replace ever luckily. Identical syntax and no other use of the letters "ifelse"
@LucyMcGowan voted for `if_else()`, adding it to the checklist now and will submit a PR
Note: https://github.com/ropenscilabs/aeolus will auto wrap markdown lines
https://www.frontiersin.org/journals/genetics/articles/10.3389/fgene.2021.651812/full https://academic.oup.com/aje/article-abstract/193/8/1075/7639890?redirectedFrom=fulltext#google_vignette