Navigating the Data Pipes: An R Programming Journey with Mario Bros.

[This article was first published on Numbers around us - Medium, and kindly contributed to R-bloggers]. (You can report issue about the content on this page here)
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.

Welcome to the Mushroom Kingdom

In the vast and varied landscape of data analysis, navigating through complex datasets and transformation processes can often feel like an adventure through unknown lands. For those who embark on this journey using R, there’s a powerful tool at their disposal, reminiscent of the magical pipes found in the iconic Mushroom Kingdom of the Mario Bros. series: piping.

Just as Mario relies on green pipes to travel quickly and safely across the kingdom, data scientists and analysts use piping in R to streamline their data processing workflows. Piping allows for the output of one function to seamlessly become the input of the next, creating a fluid and understandable sequence of data transformations. This method not only makes our code cleaner and more readable but also transforms the coding process into an adventure, guiding data from its raw state to insightful conclusions.

The concept of piping in R, introduced through packages like magrittr and now embraced in base R with the |> operator, is a game-changer. It simplifies the way we write and think about code, turning complex sequences of functions into a straightforward, linear progression of steps. Imagine, if you will, entering a green pipe with your raw data in hand, hopping from one transformation to the next, and emerging with insights as clear and vibrant as the flag at the end of a Mario level.

In this journey, we’ll explore the tools and techniques that make such transformations possible, delve into the power-ups that enhance our piping strategies, and learn how to navigate the challenges and obstacles that arise along the way. So, let’s jump into that first green pipe and start our adventure through the data pipes of R programming.

Jumping Into the Green Pipe

Entering the World of R Piping

In the world of R programming, the journey through data analysis often begins with raw, unstructured data. Just as Mario stands at the entrance of a green pipe, pondering the adventures that lie ahead, so do we stand at the precipice of our data analysis journey, ready to transform our data into insightful conclusions. The tool that enables this seamless journey is known as piping. Piping, in R, is symbolized by operators such as %>% from the magrittr package and the native |> introduced in R version 4.1.0.

The Basics of Pipe Travel

To understand the power of piping, let’s start with a simple example using R’s built-in mtcars dataset. Imagine you want to calculate the average miles per gallon (MPG) for cars with different numbers of cylinders.

Without piping, the code might look fragmented and harder to read:

mean(subset(mtcars, cyl == 4)$mpg)

However, with the magic of the %>% pipe, our code transforms into a clear and linear sequence:

mtcars %>% 
  subset(cyl == 4) %>% 
  .$mpg %>% 

This sequence of operations, akin to Mario hopping from one platform to the next, is not only more readable but also easier to modify and debug.

Level Up: Exploring the magrittr and Base R Pipes

While the %>% operator from the magrittr package has been widely celebrated for its clarity and functionality, the introduction of the native |> pipe in base R offers a streamlined alternative. Let's compare how each can be used to achieve similar outcomes:

  • Using magrittr’s %>%:
mtcars %>% 
  filter(cyl == 6) %>% 
  select(mpg, wt) %>% 
  • Using base R’s |>:
mtcars |> 
  subset(cyl == 6, select = c(mpg, wt)) |>

Each pipe has its context and advantages, and understanding both allows us to choose the best tool for our coding journey.

The Power-Ups: Enhancing Your Journey

In the Mario Bros. universe, power-ups like mushrooms, fire flowers, and super stars provide Mario with the extra abilities he needs to navigate through the Mushroom Kingdom. Similarly, in the world of R programming, there are “power-ups” that enhance the functionality of our pipes, making our data analysis journey smoother and more efficient.

Magrittr’s Magic Mushrooms: Additional Features

The magrittr package doesn't just stop at the %>% pipe operator; it offers several other functionalities that can significantly power up your data manipulation game. These include the compound assignment pipe operator %<>%, which allows you to update a dataset in place, and the tee operator %T>%, which lets you branch out the pipeline for side operations. Think of these as the Super Mushrooms and Fire Flowers of your R scripting world, empowering you to tackle bigger challenges with ease.

  • Example of %<>%:
mtcars2 = mtcars 

mtcars %<>% 
  transform(mpg = mpg * 1.60934) 
  • Example of %T>%:

mtcars %T>% 
  plot(mpg ~ wt, data = .) %>% # We are generating plot "meanwhile", without changing process
  filter(cyl == 4) %>% 
  select(mpg, wt)

The Fire Flower: Filtering and Selecting Data

Just as the Fire Flower gives Mario the ability to throw fireballs, the dplyr package (which integrates seamlessly with magrittr’s piping) equips us with powerful functions like filter() and select(). These functions allow us to narrow down our data to the most relevant pieces, throwing away what we don't need and keeping what's most useful.

  • Filtering data:
mtcars %>% 
  filter(mpg > 20) %>% 
  select(mpg, cyl, gear)

# Keeps only cars with MPG greater than 20, selecting relevant columns.

This process of filtering and selecting is like navigating through a level with precision, avoiding obstacles and focusing on the goal.

Side Quest: Joining Data Frames

Our data analysis journey often requires us to merge different data sources, akin to Mario teaming up with Luigi or Princess Peach. The dplyr package provides several functions for this purpose, such as inner_join(), left_join(), and more, allowing us to bring together disparate data sets into a unified whole.

# Assuming we have another data frame, car_details, with additional information on cars.
mtcars %>% 
  inner_join(car_details, by = "model") 

# Combines data based on the "model" column.

Boss Level: Grouped Operations

Finally, much like facing a boss in a Mario game, grouped operations in R require a bit of strategy. Using the group_by() function from dplyr, we can perform operations on our data grouped by certain criteria, effectively handling what could otherwise be a daunting task.

mtcars %>% 
  group_by(cyl) %>% 
  summarise(avg_mpg = mean(mpg)) 

# Calculates the average MPG for cars, grouped by cylinder count.

Avoiding Goombas: Debugging Your Pipe

In the realms of the Mushroom Kingdom, Mario encounters various obstacles, from Goombas to Koopa Troopas, each requiring a unique strategy to overcome. Similarly, as we navigate through our data analysis pipeline in R, we’re bound to run into issues — our own version of Goombas and Koopas — that can disrupt our journey. Debugging becomes an essential skill, allowing us to identify and address these challenges without losing our progress.

Spotting and Squashing Bugs

Just as Mario needs to stay vigilant to spot Goombas on his path, we need to be observant of the potential errors in our pipeline. Errors can arise from various sources: incorrect data types, unexpected missing values, or simply syntax errors. To spot these issues, it’s crucial to test each segment of our pipeline independently, ensuring that each step produces the expected output.

Consider using the print() or View() functions strategically to inspect the data at various stages of your pipeline. This approach is akin to Mario checking his surroundings carefully before making his next move.


mtcars %>% 
  filter(mpg > 20) %>% 
  View()  # Inspect the filtered dataset

The ViewPipeSteps Tool: Your Map Through the Mushroom Kingdom

The ViewPipeSteps package acts like a map through the Mushroom Kingdom, providing visibility into each step of our journey. By allowing us to view the output at each stage of our pipeline, it helps us identify exactly where things might be going wrong.

To use ViewPipeSteps, you'd typically wrap your pipeline within the print_pipe_steps() function, which then executes each step interactively, printing the results so you can inspect the data at each point.



diamonds %>% 
  filter(color == "E", cut == "Ideal") %>% 
  select(carat, cut, price) %>%

1. diamonds
# A tibble: 53,940 × 10
   carat cut       color clarity depth table price     x     y     z
   <dbl> <ord>     <ord> <ord>   <dbl> <dbl> <int> <dbl> <dbl> <dbl>
 1  0.23 Ideal     E     SI2      61.5    55   326  3.95  3.98  2.43
 2  0.21 Premium   E     SI1      59.8    61   326  3.89  3.84  2.31
 3  0.23 Good      E     VS1      56.9    65   327  4.05  4.07  2.31
 4  0.29 Premium   I     VS2      62.4    58   334  4.2   4.23  2.63
 5  0.31 Good      J     SI2      63.3    58   335  4.34  4.35  2.75
 6  0.24 Very Good J     VVS2     62.8    57   336  3.94  3.96  2.48
 7  0.24 Very Good I     VVS1     62.3    57   336  3.95  3.98  2.47
 8  0.26 Very Good H     SI1      61.9    55   337  4.07  4.11  2.53
 9  0.22 Fair      E     VS2      65.1    61   337  3.87  3.78  2.49
10  0.23 Very Good H     VS1      59.4    61   338  4     4.05  2.39
# ℹ 53,930 more rows
# ℹ Use `print(n = ...)` to see more rows
2. filter(color == "E", cut == "Ideal")
# A tibble: 3,903 × 10
   carat cut   color clarity depth table price     x     y     z
   <dbl> <ord> <ord> <ord>   <dbl> <dbl> <int> <dbl> <dbl> <dbl>
 1  0.23 Ideal E     SI2      61.5    55   326  3.95  3.98  2.43
 2  0.26 Ideal E     VVS2     62.9    58   554  4.02  4.06  2.54
 3  0.7  Ideal E     SI1      62.5    57  2757  5.7   5.72  3.57
 4  0.59 Ideal E     VVS2     62      55  2761  5.38  5.43  3.35
 5  0.74 Ideal E     SI2      62.2    56  2761  5.8   5.84  3.62
 6  0.7  Ideal E     VS2      60.7    58  2762  5.73  5.76  3.49
 7  0.74 Ideal E     SI1      62.3    54  2762  5.8   5.83  3.62
 8  0.7  Ideal E     SI1      60.9    57  2768  5.73  5.76  3.5 
 9  0.6  Ideal E     VS1      61.7    55  2774  5.41  5.44  3.35
10  0.7  Ideal E     SI1      62.7    55  2774  5.68  5.74  3.58
# ℹ 3,893 more rows
# ℹ Use `print(n = ...)` to see more rows
3. select(carat, cut, price)
# A tibble: 3,903 × 3
   carat cut   price
   <dbl> <ord> <int>
 1  0.23 Ideal   326
 2  0.26 Ideal   554
 3  0.7  Ideal  2757
 4  0.59 Ideal  2761
 5  0.74 Ideal  2761
 6  0.7  Ideal  2762
 7  0.74 Ideal  2762
 8  0.7  Ideal  2768
 9  0.6  Ideal  2774
10  0.7  Ideal  2774
# ℹ 3,893 more rows
# ℹ Use `print(n = ...)` to see more rows
# A tibble: 3,903 × 3
   carat cut   price
   <dbl> <ord> <int>
 1  0.23 Ideal   326
 2  0.26 Ideal   554
 3  0.7  Ideal  2757
 4  0.59 Ideal  2761
 5  0.74 Ideal  2761
 6  0.7  Ideal  2762
 7  0.74 Ideal  2762
 8  0.7  Ideal  2768
 9  0.6  Ideal  2774
10  0.7  Ideal  2774
# ℹ 3,893 more rows
# ℹ Use `print(n = ...)` to see more rows

In this example, print_pipe_steps() would allow us to see the dataset after filtering and then again after selecting specific columns, helping us spot any issues at each stage.

You can also use another feature of this package, its addin. You just need to select pipe you want to check, find and click addin’s function “View Pipe Chain Steps” and voila!

Navigating Complex Pipes: When to Use Warp Pipes

Sometimes, our data processing tasks are so complex that they feel like navigating through Bowser’s Castle. In these situations, breaking down our pipeline into smaller, manageable segments can be incredibly helpful. This approach is similar to finding secret Warp Pipes in Mario that allow you to bypass difficult levels, making the journey less daunting.

For instance, if a particular transformation is complicated, consider isolating it into its own script or function. Test it thoroughly until you’re confident it works as expected, then integrate it back into your main pipeline. This method ensures that each part of your pipeline is robust and less prone to errors.

Bowser’s Castle: Tackling Complex Data Challenges

As we near the end of our journey in the Mushroom Kingdom of R programming, we face the ultimate test of our skills: Bowser’s Castle. This chapter represents the complex data challenges that often seem as daunting as the fire-breathing dragon himself. However, just as Mario uses his skills, power-ups, and a bit of strategy to rescue Princess Peach, we’ll employ advanced piping techniques, performance considerations, and the power of collaboration to conquer these challenges.

Advanced Piping Techniques

To navigate through Bowser’s Castle, Mario must leverage every skill and power-up acquired throughout his journey. Similarly, tackling complex data tasks requires a sophisticated understanding of piping and the ability to combine various R functions and packages seamlessly.

  • Using purrr for Functional Programming:

One way to enhance our piping strategies is by integrating the purrr package, which allows for functional programming. This approach can be particularly powerful when dealing with lists or performing operations on multiple columns or datasets simultaneously.


mtcars %>% 
  split(.$cyl) %>% 
  map(~ .x %>% summarise(avg_mpg = mean(mpg), avg_hp = mean(hp)))

   avg_mpg   avg_hp
1 26.66364 82.63636

   avg_mpg   avg_hp
1 19.74286 122.2857

  avg_mpg   avg_hp
1    15.1 209.2143

This example splits the mtcars dataset by cylinder count and then applies a summarization function to each subset, showcasing how purrr can work in tandem with dplyr and piping to handle complex data operations.

Boss Battle: Performance Considerations

In every final boss battle, efficiency is key. The same goes for our R scripts when facing large datasets or complex transformations. Here, the choice of tools and techniques can significantly impact performance.

  • Vectorization Over Loops: Whenever possible, use vectorized operations, which are typically faster and more efficient than loops.
  • data.table for Large Data and dtplyr as a Secret Power-Up: The data.table package is renowned for its speed and efficiency with large datasets. But what if you could harness data.table's power with dplyr's syntax? Enter dtplyr, a bridge between these two worlds, allowing you to write dplyr code that is automatically translated into data.table operations behind the scenes. To use dtplyr, you'll wrap your data.table in lazy_dt(), then proceed with dplyr operations as usual. The dtplyr package will translate these into data.table operations, maintaining the speed advantage without sacrificing the readability and familiarity of dplyr syntax.

# Convert to a lazy data.table
lazy_dt_cars <- mtcars %>% %>% 

# Perform dplyr operations
lazy_dt_cars %>% 
  group_by(cyl) %>% 
  summarise(avg_mpg = mean(mpg), avg_hp = mean(hp)) 

Source: local data table [3 x 3]
Call:   `_DT1`[, .(avg_mpg = mean(mpg), avg_hp = mean(hp)), keyby = .(cyl)]

    cyl avg_mpg avg_hp
  <dbl>   <dbl>  <dbl>
1     4    26.7   82.6
2     6    19.7  122. 
3     8    15.1  209. 

# Use to access results

This approach can significantly reduce computation time, akin to finding a secret shortcut in Bowser’s Castle.

The Final Power-Up: Collaboration and Community

Mario rarely faces Bowser alone; he often has allies. In the world of data science and R programming, collaboration and community are equally valuable. Platforms like GitHub, Stack Overflow, and RStudio Community are akin to Mario’s allies, offering support, advice, and shared resources.

Sharing your code, seeking feedback, and collaborating on projects can enhance your skills, broaden your understanding, and help you tackle challenges that might initially seem insurmountable.

Lowering the Flag on Our Adventure

As our journey through the Mushroom Kingdom of R programming comes to a close, we lower the flag, signaling the end of a thrilling adventure. Along the way, we’ve navigated through green pipes of piping with %>% and |>, powered up our data transformation skills with dplyr and purrr, and avoided the Goombas of bugs with strategic debugging and the ViewPipeSteps tool. We've collected coins of insights through data visualization and summarization, tackled the complex challenges of Bowser's Castle with data.table and dtplyr, and recognized the power of collaboration and community in our quest for data analysis mastery.

Our expedition has shown us that, with the right tools and a bit of ingenuity, even the most daunting datasets can be transformed into valuable insights, much like Mario’s quest to rescue Princess Peach time and again proves that persistence, courage, and a few power-ups can overcome any obstacle.

But every end in the Mushroom Kingdom is merely the beginning of a new adventure. The skills and techniques we’ve acquired are not just for one-time use; they are the foundation upon which we’ll build our future data analysis projects. The world of R programming is vast and ever-evolving, filled with new packages to explore, techniques to master, and data challenges to conquer.

So, as we bid farewell to the Mushroom Kingdom for now, remember that in the world of data science, every question answered and every challenge overcome leads to new adventures. Keep exploring, keep learning, and above all, keep enjoying the journey.

Thank you for joining me on this adventure. May your path through the world of R programming be as exciting and rewarding as a quest in the Mushroom Kingdom. Until our next adventure!

Navigating the Data Pipes: An R Programming Journey with Mario Bros. was originally published in Numbers around us on Medium, where people are continuing the conversation by highlighting and responding to this story.

To leave a comment for the author, please follow the link and comment on their blog: Numbers around us - Medium. offers daily e-mail updates about R news and tutorials about learning R and many other topics. Click here if you're looking to post or find an R/data-science job.
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.

Never miss an update!
Subscribe to R-bloggers to receive
e-mails with the latest R posts.
(You will not see this message again.)

Click here to close (This popup will not appear again)