Scribd Logo
Upload

Welcome to Scribd!

  • 13 views

    Reading and Writing Data Part II Reading and Writing Data Part II

    Uploaded by

    intj2001712
    dumping and dputting are useful textual formats for passing R objects between users because the format is editable and potentially recoverable if corrupted. Textual formats also preserve metadata and can be version controlled more easily compared to other formats like CSV. However, textual formats take up more space than other formats. Multiple R objects can also be passed together using dump and source, while individual objects can be passed with dput and dget. Data is typically read into R using connection interfaces to files, URLs, or other sources.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content

    You might also like

    Reading and Writing Data Part II Reading and Writing Data Part II

    Uploaded by

    intj2001712
    13 views9 pages
    dumping and dputting are useful textual formats for passing R objects between users because the format is editable and potentially recoverable if corrupted. Textual formats also preserve metadata and can be version controlled more easily compared to other formats like CSV. However, textual formats take up more space than other formats. Multiple R objects can also be passed together using dump and source, while individual objects can be passed with dput and dget. Data is typically read into R using connection interfaces to files, URLs, or other sources.

    Original Description:

    reading data

    Original Title

    1_6 reading_data_II

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    dumping and dputting are useful textual formats for passing R objects between users because the format is editable and potentially recoverable if corrupted. Textual formats also preserve metadata and can be version controlled more easily compared to other formats like CSV. However, textual formats take up more space than other formats. Multiple R objects can also be passed together using dump and source, while individual objects can be passed with dput and dget. Data is typically read into R using connection interfaces to files, URLs, or other sources.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pdf or txt
    13 views9 pages

    Reading and Writing Data Part II Reading and Writing Data Part II

    Uploaded by

    intj2001712
    dumping and dputting are useful textual formats for passing R objects between users because the format is editable and potentially recoverable if corrupted. Textual formats also preserve metadata and can be version controlled more easily compared to other formats like CSV. However, textual formats take up more space than other formats. Multiple R objects can also be passed together using dump and source, while individual objects can be passed with dput and dget. Data is typically read into R using connection interfaces to files, URLs, or other sources.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pdf or txt
    of 9

    Reading and Writing Data Part II Reading and Writing Data Part II

    Roger D. Peng, Associate Professor of Biostatistics


    Johns Hopkins Bloomberg School of Public Health
    Textual Formats Textual Formats
    dumping and dputing are useful because the resulting textual format is edit-able, and in the case
    of corruption, potentially recoverable.
    Unlike writing out a table or csv le, dump and dput preserve the metadata (sacricing some
    readability), so that another user doesnt have to specify it all over again.
    Textual formats can work much better with version control programs like subversion or git which
    can only track changes meaningfully in text les
    Textual formats can be longer-lived; if there is corruption somewhere in the le, it can be easier to
    x the problem
    Textual formats adhere to the Unix philosophy
    Downside: The format is not very space-efcient

    2/9
    dput-ting R Objects dput-ting R Objects
    Another way to pass data around is by deparsing the R object with dput and reading it back in using
    dget.
    > y <- data.frame(a = 1, b = "a")
    > dput(y)
    structure(list(a = 1,
    b = structure(1L, .Label = "a",
    class = "factor")),
    .Names = c("a", "b"), row.names = c(NA, -1L),
    class = "data.frame")
    > dput(y, file = "y.R")
    > new.y <- dget("y.R")
    > new.y
    a b
    1 1 a
    3/9
    Dumping R Objects Dumping R Objects
    Multiple objects can be deparsed using the dump function and read back in using source.
    > x <- "foo"
    > y <- data.frame(a = 1, b = "a")
    > dump(c("x", "y"), file = "data.R")
    > rm(x, y)
    > source("data.R")
    > y
    a b
    1 1 a
    > x
    [1] "foo"
    4/9
    Interfaces to the Outside World Interfaces to the Outside World
    Data are read in using connection interfaces. Connections can be made to les (most common) or to
    other more exotic things.
    file, opens a connection to a le
    gzfile, opens a connection to a le compressed with gzip
    bzfile, opens a connection to a le compressed with bzip2
    url, opens a connection to a webpage

    5/9
    File Connections File Connections
    > str(file)
    function (description = "", open = "", blocking = TRUE,
    encoding = getOption("encoding"))
    description is the name of the le
    open is a code indicating

    r read only
    w writing (and initializing a new le)
    a appending
    rb, wb, ab reading, writing, or appending in binary mode (Windows)
    -
    -
    -
    -
    6/9
    Connections Connections
    In general, connections are powerful tools that let you navigate les or other external objects. In
    practice, we often dont need to deal with the connection interface directly.
    is the same as
    con <- file("foo.txt", "r")
    data <- read.csv(con)
    close(con)
    data <- read.csv("foo.txt")
    7/9
    Reading Lines of a Text File Reading Lines of a Text File
    writeLines takes a character vector and writes each element one line at a time to a text le.
    > con <- gzfile("words.gz")
    > x <- readLines(con, 10)
    > x
    [1] "1080" "10-point" "10th" "11-point"
    [5] "12-point" "16-point" "18-point" "1st"
    [9] "2" "20-point"
    8/9
    Reading Lines of a Text File Reading Lines of a Text File
    readLines can be useful for reading in lines of webpages
    ## This might take time
    con <- url("http://www.jhsph.edu", "r")
    x <- readLines(con)
    > head(x)
    [1] "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.0 Transitional//EN\">"
    [2] ""
    [3] "<html>"
    [4] "<head>"
    [5] "\t<meta http-equiv=\"Content-Type\" content=\"text/html;charset=utf-8
    9/9

    You might also like