Git Product home page Git Product logo

foofactors's Introduction

NOTE: This is a toy package created for expository purposes, for the second edition of R Packages. It is not meant to actually be useful. If you want a package for factor handling, please see forcats.

foofactors

Factors are a very useful type of variable in R, but they can also be very aggravating. This package provides some helper functions for the care and feeding of factors.

Installation

You can install foofactors like so:

devtools::install_github("jennybc/foofactors")

Quick demo

Binding two factors via fbind():

library(foofactors)
a <- factor(c("character", "hits", "your", "eyeballs"))
b <- factor(c("but", "integer", "where it", "counts"))

Simply catenating two factors leads to a result that most don’t expect.

c(a, b)
#> [1] 1 3 4 2 1 3 4 2

The fbind() function glues two factors together and returns factor.

fbind(a, b)
#> [1] character hits      your      eyeballs  but       integer   where it 
#> [8] counts   
#> Levels: but character counts eyeballs hits integer where it your

Often we want a table of frequencies for the levels of a factor. The base table() function returns an object of class table, which can be inconvenient for downstream work.

set.seed(1234)
x <- factor(sample(letters[1:5], size = 100, replace = TRUE))
table(x)
#> x
#>  a  b  c  d  e 
#> 19 19 21 22 19

The fcount() function returns a frequency table as a tibble with a column of factor levels and another of frequencies:

fcount(x)
#> # A tibble: 5 x 2
#>   f         n
#>   <fct> <int>
#> 1 d        22
#> 2 c        21
#> 3 a        19
#> 4 b        19
#> 5 e        19

foofactors's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

foofactors's Issues

Workflow for converting an existing R project into a package project

Hi,

First of all: Thank you very much for this repo and the book. They are both extremely useful for a novice like myself!

Hopefully you are willing to answer a few questions. I created a new project in RStudio and hooked it up to a GitHub repo. The intent was to build a shiny app, but along the way I decided that it made more sense to make a package instead. That's when I discovered your book.

Is there a preferred workflow to convert my existing shiny app project into a package project (with the devtools package or otherwise)?

The main reason for asking is that my current file structure (which I don't mind changing) is not the same as that which was created when following along with chapter 2 of the book.

Please forgive me if I have overlooked this in the book.

Best regards,
Rishi

what is the presumed folder when we execute load_all()

this in section 2.8. it is not clear what is getwd() and how to avoid loading unwanted stuff. I am working from ESS and have a file play-package.R and execute the
library(devtools)
library(tidyverse)
library(fs)
load_all("./foofactors/")

and it does not load the foofactors at all. foofactors is a folder just under my workdir and the fbind.R is there. according the load_all help it should load the path provided, but it does not.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.