Peter Ehlers wrote:
> It is hardly R's fault that Excel users routinely commit
> crimes against data.
A ‘fortune’ candidate?
--
Karl Ove Hufthammer
__
R-help@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the p
David Scott wrote:
> As a further note, this is a reminder that whenever you get data via a
> spreadsheet the first thing to do is examine it and clean up any
> problems. A basic requirement is to tabulate any categorical variable.
I like using the ‘describe’ function in the ‘Hmisc’ package for t
David,
Thanks. When I am back at work I will try to find out some specifics
regarding the original data base and how the reports are generated. The
differencs are not apparent via manual inspection.
I will look at the csv file in an editor as well and look into xlsReadWrite.
I agree EXCEL format
I am a bit confused by this. You are doing a transfer from Excel (.xls
or .xlsx) to .csv, then a subset in R and ending up with a couple of
entries which are " Open" rather than "Open". So where are they coming
from? You say they are not in the original Excel, so that suggests the
transfer to .
At 14.01.2011 07:09 -0800, Peter Ehlers wrote:
On 2011-01-14 02:09, bgr...@dyson.brisnet.org.au wrote:
Brian,
Thanks. My response to David follows. I should add that this problem has
never occurred previously as far as I know (I have now checked the
previous report I was sent):
This problem o
On 2011-01-14 02:09, bgr...@dyson.brisnet.org.au wrote:
Brian,
Thanks. My response to David follows. I should add that this problem has
never occurred previously as far as I know (I have now checked the
previous report I was sent):
This problem occurs to me frequently. Like Philipp and David,
On Fri, Jan 14, 2011 at 07:58:07PM +1000, bgr...@dyson.brisnet.org.au wrote:
>
> Thanks for your e-mail. The data was a report derived from a statewide
> database, saved in EXCEL format, so the usual issue of the vagaries of
> human data entry variation wasn't the issue as the data was an automate
Brian,
Thanks. My response to David follows. I should add that this problem has
never occurred previously as far as I know (I have now checked the
previous report I was sent):
Hello David,
Thanks for your e-mail. The data was a report derived from a statewide
database, saved in EXCEL format, so
Hello David,
Thanks for your e-mail. The data was a report derived from a statewide
database, saved in EXCEL format, so the usual issue of the vagaries of
human data entry variation wasn't the issue as the data was an automated
report, which is run every three months. I would not have even noticed
On Fri, 14 Jan 2011, David Scott wrote:
As a further note, this is a reminder that whenever you get data via
a spreadsheet the first thing to do is examine it and clean up any
problems. A basic requirement is to tabulate any categorical
variable. Spreadsheets allow any sort of data to be enter
As a further note, this is a reminder that whenever you get data via a
spreadsheet the first thing to do is examine it and clean up any
problems. A basic requirement is to tabulate any categorical variable.
Spreadsheets allow any sort of data to be entered, with no controls. My
experience is th
try strip.white=TRUE to strip out white space
Sent from my iPad
On Jan 13, 2011, at 21:44, bgr...@dyson.brisnet.org.au wrote:
>
> I have a frustrating issue which I am hoping someone may have a suggestion
> about.
>
> I am running XP and R 2.12.0 and saved an EXCEL file that I was sent as a
>
I have a frustrating issue which I am hoping someone may have a suggestion
about.
I am running XP and R 2.12.0 and saved an EXCEL file that I was sent as a
csv file.
The initial code I ran follows.
dec <- read.csv("g://FMH/FO30122010.csv",header=T)
dec.open <- subset (dec, Status == "Open")
tab
13 matches
Mail list logo
