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
[1] "Cool Category.A: Drug X"
[1] "Cool Category.B: Placebo"
[1] " .C: Combination"
[1] "A: Drug X"
[1] "C: Combination"
[1] "Cool Category.A: Drug X"
[1] "Cool Category.B: Placebo"
[1] " .C: Combination"
[1] "A: Drug X"
[1] "C: Combination"
[1] "Cool Category.A: Drug X"
[1] "Cool Category.B: Placebo"
[1] " .C: Combination"
[1] "A: Drug X"
[1] "C: Combination"
Cool Category
A: Drug X B: Placebo C: Combination A: Drug X C: Combination
————————————————————————————————————————————————————————————————————————————————————————
A
myfun 36 (29.8%) 33 (31.1%) 45 (34.9%) some other stuff some other stuff
B
myfun 41 (33.9%) 40 (37.7%) 38 (29.5%) some other stuff some other stuff
C
myfun 44 (36.4%) 33 (31.1%) 46 (35.7%) some other stuff some other stuff
Note I was able to monkey-hack something together here, but having access to the full path, either in pasted form in cur_col_id or preferably, imo, in a separate list column, would be a cleaner solution more in line with all of the o ther path-based interactions rtables supports
The text was updated successfully, but these errors were encountered:
I think the path is available here: .spl_context$cur_col_split_val or .spl_context$cur_col_split. We could discuss having a .spl_context_rows and .splt_context_cols (and maybe making it an object with rows and cols getter/setters) but at the moment I do not know if it is worth the added complexity
@Melkiades unfortunately the current split and value are not sufficient. In the example I put above (which I can now say is a set of relative risk columns, since I found out that came from public FDA specs), I effectively need to know whether the current column split has a parent split or not.
Currently the
cur_col_id
in the split context is pasted together from only the values of the column path the tabulation machinery is currently at.This information is incomplete, particularly in cases where there are different facets in column space based on the same variable, e.g,
gives us
Note I was able to monkey-hack something together here, but having access to the full path, either in pasted form in
cur_col_id
or preferably, imo, in a separate list column, would be a cleaner solution more in line with all of the o ther path-based interactionsrtables
supportsThe text was updated successfully, but these errors were encountered: