R Language
- Getting started with R Language
- Awesome Book
- Awesome Community
- Awesome Course
- Awesome Tutorial
- Awesome YouTube
- *apply family of functions (functionals)
- .Rprofile
- Aggregating data frames
- Analyze tweets with R
- ANOVA
- Arima Models
- Arithmetic Operators
- Bar Chart
- Base Plotting
- Bibliography in RMD
- boxplot
- caret
- Classes
- Cleaning data
- Code profiling
- Coercion
- Color schemes for graphics
- Column wise operation
- Combinatorics
- Control flow structures
- Creating packages with devtools
- Creating reports with RMarkdown
- Creating vectors
- Data acquisition
- Data frames
- data.table
- Date and Time
- Date-time classes (POSIXct and POSIXlt)
- Debugging
- Distribution Functions
- dplyr
- Expression: parse + eval
- Extracting and Listing Files in Compressed Archives
- Factors
- Fault-tolerant/resilient code
- Feature Selection in R -- Removing Extraneous Features
- Formula
- Fourier Series and Transformations
- Functional programming
- Generalized linear models
- Get user input
- ggplot2
- GPU-accelerated computing
- Hashmaps
- heatmap and heatmap.2
- Hierarchical clustering with hclust
- Hierarchical Linear Modeling
- I/O for database tables
- I/O for foreign tables (Excel, SAS, SPSS, Stata)
- I/O for geographic data (shapefiles, etc.)
- I/O for raster images
- I/O for R's binary format
- Implement State Machine Pattern using S4 Class
- Input and output
- Inspecting packages
- Installing packages
- Introduction to Geographical Maps
- Introspection
- JSON
- Linear Models (Regression)
- Lists
- lubridate
- Machine learning
- Matrices
- Meta: Documentation Guidelines
- Missing values
- Modifying strings by substitution
- Natural language processing
- Network analysis with the igraph package
- Non-standard evaluation and standard evaluation
- Numeric classes and storage modes
- Object-Oriented Programming in R
- Parallel processing
- Pattern Matching and Replacement
- Performing a Permutation Test
- Pipe operators (%>% and others)
- Pivot and unpivot with data.table
- Probability Distributions with R
- Publishing
- R code vectorization best practices
- R in LaTeX with knitr
- R Markdown Notebooks (from RStudio)
- R memento by examples
- Random Forest Algorithm
- Random Numbers Generator
- Randomization
- Raster and Image Analysis
- Rcpp
- Reading and writing strings
- Reading and writing tabular data in plain-text files (CSV, TSV, etc.)
- Recycling
- Regular Expression Syntax in R
- Regular Expressions (regex)
- Reproducible R
- Reshape using tidyr
- Reshaping data between long and wide forms
- RESTful R Services
- RMarkdown and knitr presentation
- RODBC
- roxygen2
- Run-length encoding
- Run-length Encoding with `rle`
- Identifying and grouping by runs in base R
- Identifying and grouping by runs in data.table
- Run-length encoding to compress and decompress vectors
- Scope of variables
- Set operations
- Shiny
- Solving ODEs in R
- Spark API (SparkR)
- spatial analysis
- Speeding up tough-to-vectorize code
- Split function
- sqldf
- Standardize analyses by writing standalone R scripts
- String manipulation with stringi package
- strsplit function
- Subsetting
- Survival analysis
- Text mining
- The character class
- The Date class
- The logical class
- tidyverse
- Time Series and Forecasting
- Updating R and the package library
- Updating R version
- Using pipe assignment in your own package %<>%: How to ?
- Using texreg to export models in a paper-ready way
- Variables
- Web Crawling in R
- Web scraping and parsing
- Writing functions in R
- xgboost
R Language Run-length encoding Run-length Encoding with `rle`
Example
Run-length encoding captures the lengths of runs of consecutive elements in a vector. Consider an example vector:
dat <- c(1, 2, 2, 2, 3, 1, 4, 4, 1, 1)
The rle function extracts each run and its length:
r <- rle(dat)
r
# Run Length Encoding
# lengths: int [1:6] 1 3 1 1 2 2
# values : num [1:6] 1 2 3 1 4 1
The values for each run are captured in r$values:
r$values
# [1] 1 2 3 1 4 1
This captures that we first saw a run of 1's, then a run of 2's, then a run of 3's, then a run of 1's, and so on.
The lengths of each run are captured in r$lengths:
r$lengths
# [1] 1 3 1 1 2 2
We see that the initial run of 1's was of length 1, the run of 2's that followed was of length 3, and so on.
