{"id":2890,"date":"2023-02-01T02:57:23","date_gmt":"2023-02-01T02:57:23","guid":{"rendered":"http:\/\/optimumsportsperformance.com\/blog\/?p=2890"},"modified":"2023-02-01T13:54:03","modified_gmt":"2023-02-01T13:54:03","slug":"removing-columns-with-na-for-fluid-table-building-in-shiny","status":"publish","type":"post","link":"https:\/\/optimumsportsperformance.com\/blog\/removing-columns-with-na-for-fluid-table-building-in-shiny\/","title":{"rendered":"Removing columns with NA for fluid table building in shiny"},"content":{"rendered":"

One of the most frustrating aspects of building {shiny<\/strong>} apps is dealing with columns that have NAs when outputting tables. This is common in sport when dealing with players from different position groups who may have different stats that describe performance for those positions. Rather than writing a long series of if\/else<\/strong> statements, I prefer to streamline the process by dropping those columns prior to returning the table of data. Not only does this make the app run smoothly but it also is easier to debug or add additional table information without having to deal with a lot of nested if\/else <\/strong>statements.<\/p>\n

The full code is accessible on my GITHUB page<\/a><\/span><\/strong>.<\/p>\n

Load Packages & Simulate Data<\/strong><\/span><\/p>\n

\r\n## Removing columns with NA for fluid table building in shiny\r\n\r\n## packages ---------------------------------------------------\r\nlibrary(tidyverse)\r\nlibrary(shiny)\r\n\r\n## simulate data ----------------------------------------------\r\nd <- tribble(\r\n  ~player, ~position, ~stat1, ~stat2, ~stat3,\r\n  'Frank', 'Pitcher', 10, NA, 33,\r\n  'Tom', 'Batter', NA, 14, 12,\r\n  'Jeff', 'Batter', NA, 5, NA,\r\n  'Harold', 'Pitcher\/Batter', 12, 33, 9\r\n)\r\n\r\nd\r\n<\/pre>\n
\"\"<\/a><\/p>\n
We can see from our little data set that different players have different stats populated. We really don’t want our users to deal with having to see NA in the table output. So, we need to devise a way to drop the columns with NA’s once a specific player has been selected.<\/p>\n
Dropping Columns with NA in Base R<\/strong><\/span><\/p>\n
Let’s select on player and attempt to drop their columns with NA. In base R we will use the colSums() <\/strong>function to produce a count of the number of NA’s in each column.<\/p>\n
\r\n## remove columns with NA for Frank, using Base R --------------------------\r\n\r\nfrank <- d %>% \r\n  filter(player == 'Frank')\r\n\r\n# colSums() can be used to count the NA's in each column\r\ncolSums(is.na(frank))\r\n<\/pre>\n
\"\"<\/a><\/p>\n
We can see that stat2 has 1 NA while the other 4 columns are complete. We can use this information to retain those four columns and drop stat2.<\/p>\n
\r\nfrank[ , colSums(is.na(frank)) == 0]\r\n<\/pre>\n
\"\"<\/a><\/p>\n
Dropping Columns with NA in {dplyr}<\/span>
\n<\/strong><\/p>\n
We can perform a similar task using the\u00a0select_if()\u00a0<\/strong>function within the {dplyr<\/strong>} package and indicating that we want to select all columns without an NA.<\/p>\n
\r\nfrank %>%\r\n  select_if(~!is.na(.x))\r\n<\/pre>\n
\"\"<\/a><\/p>\n
Build a shiny app that fluidly retains the columns without NA<\/strong><\/span><\/p>\n
Now that we have a few strategies for removing columns with NA, we can build a {shiny<\/strong>} app that allows the user to select a player and then the server fluidly will drop the columns with NA so that we don’t need to use a messy if\/else <\/strong>chain.<\/p>\n
Notice that prior to dropping columns with NA I set the names of all of the columns in the table so that they look nicer when the table gets rendered. We can see from the figures that no matter which player is selected, the server intelligently drops columns with missing data, allowing the user to see only the statistics that are meaningful for the individual.<\/p>\n
\r\n# UI\r\nui <- fluidPage(\r\n  \r\n  sidebarPanel(\r\n    \r\n    selectInput(inputId = 'player',\r\n                label = "Select Player",\r\n                choices = sort(unique(d$player)),\r\n                selected = FALSE,\r\n                multiple = FALSE)\r\n    \r\n  ),\r\n  \r\n  mainPanel(\r\n    \r\n    tableOutput(outputId = 'tbl')\r\n  )\r\n)\r\n\r\n# Server\r\nserver <- function(input, output){\r\n  \r\n  # get selected player\r\n  dat_tbl <- reactive({ d %>%\r\n      filter(player == input$player)\r\n    \r\n  })\r\n  \r\n  # build table\r\n  output$tbl <- renderTable({ dat_tbl() %>%\r\n      setNames(c("Player", "Position", "Stat 1", "Stat 2", "Stat 3")) %>%\r\n      select_if(~!is.na(.x))\r\n    \r\n  })\r\n  \r\n}\r\n\r\n\r\n# deploy\r\nshinyApp(ui, server)\r\n<\/pre>\n
\"\"<\/a><\/p>\n
Wrapping Up<\/strong><\/span><\/p>\n
Instead of having users see columns with NA, make your renderTable() <\/strong>function fluid and automatically drop columns with missing values to improve the user experience.<\/p>\n
The full code is accessible on my GITHUB page<\/a><\/span><\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":"
One of the most frustrating aspects of building {shiny} apps is dealing with columns that have NAs when outputting tables. This is common in sport when dealing with players from different position groups who may have different stats that describe performance for those positions. Rather than writing a long series of if\/else statements, I prefer […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[45,43,42],"tags":[],"class_list":["post-2890","post","type-post","status-publish","format-standard","hentry","category-r-tips-tricks","category-sports-analytics","category-sports-science"],"_links":{"self":[{"href":"https:\/\/optimumsportsperformance.com\/blog\/wp-json\/wp\/v2\/posts\/2890","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/optimumsportsperformance.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/optimumsportsperformance.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/optimumsportsperformance.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/optimumsportsperformance.com\/blog\/wp-json\/wp\/v2\/comments?post=2890"}],"version-history":[{"count":3,"href":"https:\/\/optimumsportsperformance.com\/blog\/wp-json\/wp\/v2\/posts\/2890\/revisions"}],"predecessor-version":[{"id":2898,"href":"https:\/\/optimumsportsperformance.com\/blog\/wp-json\/wp\/v2\/posts\/2890\/revisions\/2898"}],"wp:attachment":[{"href":"https:\/\/optimumsportsperformance.com\/blog\/wp-json\/wp\/v2\/media?parent=2890"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/optimumsportsperformance.com\/blog\/wp-json\/wp\/v2\/categories?post=2890"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/optimumsportsperformance.com\/blog\/wp-json\/wp\/v2\/tags?post=2890"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}