Skip to content
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

Group and subgroup make more sense than row and col. #9

Open
mbcann01 opened this issue Dec 13, 2019 · 0 comments
Open

Group and subgroup make more sense than row and col. #9

mbcann01 opened this issue Dec 13, 2019 · 0 comments
Labels
question Further information is requested

Comments

@mbcann01
Copy link
Member

mbcann01 commented Dec 13, 2019

Row and column make sense for a contingency table, but not so much for a frequency table (click here to see the difference).

For a frequency table, we should use group and outcome. Or possibly just use the variable names as column headers?

Handing code if we want to grab the group variable names for some reason:

mtcars %>% 
  group_by(am) %>% 
  group_vars()

Or the group levels

mtcars %>% 
  group_by(am) %>% 
  group_keys()
@mbcann01 mbcann01 added the question Further information is requested label Jun 17, 2021
@mbcann01 mbcann01 removed this from To do in Bug fixes and enhancements Jul 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
Status: Develop Next
Development

No branches or pull requests

1 participant