From: roger koenker <roger_at_ysidro.econ.uiuc.edu>

Date: Sun, 10 Jun 2007 16:35:54 -0500

R-help_at_stat.math.ethz.ch mailing list

https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code. Received on Sun 10 Jun 2007 - 21:42:29 GMT

Date: Sun, 10 Jun 2007 16:35:54 -0500

An important potential benefit of R solutions shared by awk, sed, ...
is that they provide a reproducible way to document exactly how one
got

from one version of the data to the next. This seems to be the main
problem with handicraft methods like editing excel files, it is too
easy to introduce new errors that can't be tracked down at later
stages of the analysis.

url: www.econ.uiuc.edu/~roger Roger Koenker email rkoenker_at_uiuc.edu Department of Economics vox: 217-333-4558 University of Illinois fax: 217-244-6678 Champaign, IL 61820

On Jun 10, 2007, at 4:14 PM, (Ted Harding) wrote:

> On 10-Jun-07 19:27:50, Stephen Tucker wrote:

*>>
**>> Since R is supposed to be a complete programming language,
**>> I wonder why these tools couldn't be implemented in R
**>> (unless speed is the issue). Of course, it's a naive desire
**>> to have a single language that does everything, but it seems
**>> that R currently has most of the functions necessary to do
**>> the type of data cleaning described.
**>
**> In principle that is certainly true. A couple of comments,
**> though.
**>
**> 1. R's rich data structures are likely to be superfluous.
**> Mostly, at the sanitisation stage, one is working with
**> "flat" files (row & column). This straightforward format
**> is often easier to handle using simple programs for the
**> kind of basic filtering needed, rather then getting into
**> the heavier programming constructs of R.
**>
**> 2. As follow-on and contrast at the same time, very often
**> what should be a nice flat file with no rough edges is not.
**> If there are variable numbers of fields per line, R will
**> not handle it straightforwardly (you can force it in,
**> but it's more elaborate). There are related issues as well.
**>
**> a) If someone entering data into an Excel table lets their
**> cursor wander outside the row/col range of the table,
**> this can cause invisible entities to be planted in the
**> extraneous cells. When saved as a CSV, this file then
**> has variable numbers of fields per line, and possibly
**> also extra lines with arbitrary blank fields.
**>
**> cat datafile.csv | awk 'BEGIN{FS=","}{n=NF;print n}'
**>
**> will give you the numbers of fields in each line.
**>
**> If you further pipe it into | sort -nu you will get
**> the distinct field-numbers. If you know (by now) how many
**> fields there should be (e.g. 10), then
**>
**> cat datafile.csv | awk 'BEGIN{FS=","} (NF != 10){print NR ", " NF}'
**>
**> will tell you which lines have the wrong number of fields,
**> and how many fields they have. You can similarly count how
**> many lines there are (e.g. pipe into wc -l).
**>
**> b) Poeple sometimes randomly use a blank space or a "." in a
**> cell to demote a missing value. Consistent use of either
**> is OK: ",," in a CSV will be treated as "NA" by R. The use
**> of "." can be more problematic. If for instance you try to
**> read the following CSV into R as a dataframe:
**>
**> 1,2,.,4
**> 2,.,4,5
**> 3,4,.,6
**>
**> the "." in cols 2 and 3 is treated as the character ".",
**> with the result that something complicated happens to
**> the typing of the items.
**>
**> typeeof(D[i,j]) is always integer. sum(D[1,1]=1, but
**> sum(D[1,2]) gives a type-error, even though the entry
**> is in fact 2. And so on , in various combinations.
**>
**> And (as.nmatrix(D)) is of course a matrix of characters.
**>
**> In fact, columns 2 and 3 of D are treated as factors!
**>
**> for(i in (1:3)){ for(j in (1:4)){ print( (D[i,j]))}}
**> [1] 1
**> [1] 2
**> Levels: . 2 4
**> [1] .
**> Levels: . 4
**> [1] 4
**> [1] 2
**> [1] .
**> Levels: . 2 4
**> [1] 4
**> Levels: . 4
**> [1] 5
**> [1] 3
**> [1] 4
**> Levels: . 2 4
**> [1] .
**> Levels: . 4
**> [1] 6
**>
**> This is getting altogether too complicated for the job
**> one wants to do!
**>
**> And it gets worse when people mix ",," and ",.,"!
**>
**> On the other hand, a simple brush with awk (or sed in
**> this case) can sort it once and for all, without waking
**> the sleeping dogs in R.
**>
**> I could go on. R undoubtedly has the power, but it can very
**> quickly get over-complicated for simple jobs.
**>
**> Best wishes to all,
**> Ted.
**>
**> --------------------------------------------------------------------
**> E-Mail: (Ted Harding) <Ted.Harding_at_manchester.ac.uk>
**> Fax-to-email: +44 (0)870 094 0861
**> Date: 10-Jun-07 Time: 22:14:35
**> ------------------------------ XFMail ------------------------------
**>
**> ______________________________________________
**> R-help_at_stat.math.ethz.ch mailing list
**> https://stat.ethz.ch/mailman/listinfo/r-help
**> PLEASE do read the posting guide http://www.R-project.org/posting-
**> guide.html
**> and provide commented, minimal, self-contained, reproducible code.
*

R-help_at_stat.math.ethz.ch mailing list

https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code. Received on Sun 10 Jun 2007 - 21:42:29 GMT

Archive maintained by Robert King, hosted by
the discipline of
statistics at the
University of Newcastle,
Australia.

Archive generated by hypermail 2.2.0, at Sun 10 Jun 2007 - 22:31:48 GMT.

*
Mailing list information is available at https://stat.ethz.ch/mailman/listinfo/r-help.
Please read the posting
guide before posting to the list.
*