You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@asyakhl what is the historical reason for the naming of the lefser() blockCol argument? This name, and the help for the argument:
character(1) Optional column name in colData(relab) indicating the blocks, usually a factor with two levels (e.g., c("adult", "senior"); default NULL).
implies that it is a blocking variable (ie https://en.wikipedia.org/wiki/Blocking_(statistics) ). However, in LEfSe, the two grouping variables define main groups and subgroups for pairwise comparisons, not a blocking variable. Also, why would subgoups usually have two levels?
I think this causes confusion by users trying to use it to define blocking variables (ie, see `blockCol = "patient" in #47). I'm hesitant to rename the variable and break existing code, but we should make it much clearer in documentation how this argument is used and that it doesn't refer to a blocking variable in the statistical sense.
The text was updated successfully, but these errors were encountered:
@lwaldron I don't remember the historical reason for this kind of naming. We should deprecate groupCol and blockCol and change it to class and subclass to avoid confusion with blocking variable. There can be more than two levels of subgroups! @shbrief I started PR to clarify man for blockCol.
@asyakhl what is the historical reason for the naming of the lefser()
blockCol
argument? This name, and the help for the argument:implies that it is a blocking variable (ie https://en.wikipedia.org/wiki/Blocking_(statistics) ). However, in LEfSe, the two grouping variables define main groups and subgroups for pairwise comparisons, not a blocking variable. Also, why would subgoups usually have two levels?
I think this causes confusion by users trying to use it to define blocking variables (ie, see `blockCol = "patient" in #47). I'm hesitant to rename the variable and break existing code, but we should make it much clearer in documentation how this argument is used and that it doesn't refer to a blocking variable in the statistical sense.
The text was updated successfully, but these errors were encountered: