Hi Tomas,
On Mon, May 13, 2019 at 11:42 AM Tomas Kalibera
wrote:
[...]
> This is because (from NEWS:)
>
> The default ‘user agent’ has been changed when accessing http://
>and https:// sites using libcurl. (A site was found which caused
>libcurl to infinite-loop with the previous
On 5/6/19 2:27 PM, Stephen Berman wrote:
On Mon, 6 May 2019 11:12:25 +0200 Ralf Stubner wrote:
On 04.05.19 19:04, Stephen Berman wrote:
In versions of R prior to 3.6.0 the following invocation succeeds,
returning the data frame shown:
read.table("https://www.dwds.de/r/stat?corpus=kern&cnt=t
On Mon, 6 May 2019 11:12:25 +0200 Ralf Stubner wrote:
> On 04.05.19 19:04, Stephen Berman wrote:
>> In versions of R prior to 3.6.0 the following invocation succeeds,
>> returning the data frame shown:
>>
>>> read.table("https://www.dwds.de/r/stat?corpus=kern&cnt=tokens&date=decade&format=text";,
On 04.05.19 19:04, Stephen Berman wrote:
> In versions of R prior to 3.6.0 the following invocation succeeds,
> returning the data frame shown:
>
>> read.table("https://www.dwds.de/r/stat?corpus=kern&cnt=tokens&date=decade&format=text";,
>> header=TRUE)
>Dekade Anzahl
> 11900 11467254
>
On 04.06.2017 11:50, jing hua zhao wrote:
Hi All,
I wonder if there should be one character for quote= in read.table, i.e.,
args(read.table)
function (file, header = FALSE, sep = "", quote = "\"'", dec = ".",
...
I have a file containing the following lines,
08248-GOTERM3'-phosphoa
Thank you both!
Bill Dunlap
TIBCO Software
wdunlap tibco.com
On Wed, Oct 7, 2015 at 1:44 PM, peter dalgaard wrote:
> This is fixed/changed in r-devel:
>
> > str(type.convert("i"))
> Factor w/ 1 level "i": 1
>
> It was reported on July 18 as PR#16473, if you care.
>
> (Funny how an obscure issu
This is fixed/changed in r-devel:
> str(type.convert("i"))
Factor w/ 1 level "i": 1
It was reported on July 18 as PR#16473, if you care.
(Funny how an obscure issue goes unnoticed for a decade, then pops up twice
independently within a few months. A property of the Poisson process, I
suppose.
On 07/10/2015 21:22, William Dunlap wrote:
I just noticed that read.table() and type.convert() interpret the string "i"
as a missing value of type complex.
> str(read.table(text=c("i\ni\ni\ni\n")))
'data.frame': 4 obs. of 1 variable:
$ V1: cplx NA NA NA ...
> str(type.convert
Milan Bouchet-Valat wrote
> It seems that read.table() in R 3.0.1 (Linux 64-bit) does not consider
> quoted integers as an acceptable value for columns for which
> colClasses="integer". But when colClasses is omitted, these columns are
> read as integer anyway.
>
> For example, let's consider a fi
On Mon, Apr 21, 2014 at 06:44:05PM +0100, Prof Brian Ripley wrote:
> On 21/04/2014 18:08, Andrew Piskorski wrote:
> >> .External(utils:::C_readtablehead, ...)
> >
> > Ah, that works fine, and is nice and simple. So problem solved, thank
> > you!
> >
> > I do still wonder though, with the C symbol
On 21/04/2014 18:08, Andrew Piskorski wrote:
On Mon, Apr 21, 2014 at 12:43:55PM -0400, Simon Urbanek wrote:
And that's how it should be - there is not reason why any other code should
link to it. Why don't you just use
.External(utils:::C_readtablehead, ...)
Ah, that works fine, and is nice
Andrew,
I haven't checked, but probably because it wasn't registered as a native
routine for that package.
~G
On Mon, Apr 21, 2014 at 10:08 AM, Andrew Piskorski wrote:
> On Mon, Apr 21, 2014 at 12:43:55PM -0400, Simon Urbanek wrote:
>
> > And that's how it should be - there is not reason why a
On Mon, Apr 21, 2014 at 12:43:55PM -0400, Simon Urbanek wrote:
> And that's how it should be - there is not reason why any other code should
> link to it. Why don't you just use
>
> .External(utils:::C_readtablehead, ...)
Ah, that works fine, and is nice and simple. So problem solved, thank
yo
Andrew,
On Apr 21, 2014, at 11:53 AM, Andrew Piskorski wrote:
> One of the great things about R is how readable and re-usable much of
> its own implementation is. If an R function doesn't do quite what you
> want but is close, it is usually very easy to read its code and start
> adapting that a
On Fri, Oct 4, 2013 at 9:20 AM, Peter Meilstrup
wrote:
> I think this is not the right approach -- quoting is a transport-layer
> feature of the CSV format, not part of the application layer. Quotes
> should always be interpreted away from column data before any data is
> handed to the application
On Fri, Oct 4, 2013 at 9:15 AM, peter dalgaard wrote:
>
> On Oct 4, 2013, at 17:10 , Henrik Bengtsson wrote:
>
>> On Fri, Oct 4, 2013 at 4:55 AM, Duncan Murdoch
>> wrote:
>>> On 13-10-04 7:31 AM, Joshua Ulrich wrote:
On Tue, Oct 1, 2013 at 11:29 AM, David Winsemius
wrote:
>
>
I think this is not the right approach -- quoting is a transport-layer
feature of the CSV format, not part of the application layer. Quotes
should always be interpreted away from column data before any data is
handed to the application layer. (CSV does not _have_ any application
layer; type informa
On Oct 4, 2013, at 17:10 , Henrik Bengtsson wrote:
> On Fri, Oct 4, 2013 at 4:55 AM, Duncan Murdoch
> wrote:
>> On 13-10-04 7:31 AM, Joshua Ulrich wrote:
>>>
>>> On Tue, Oct 1, 2013 at 11:29 AM, David Winsemius
>>> wrote:
On Sep 30, 2013, at 6:38 AM, Joshua Ulrich wrote:
On Fri, Oct 4, 2013 at 4:55 AM, Duncan Murdoch wrote:
> On 13-10-04 7:31 AM, Joshua Ulrich wrote:
>>
>> On Tue, Oct 1, 2013 at 11:29 AM, David Winsemius
>> wrote:
>>>
>>>
>>> On Sep 30, 2013, at 6:38 AM, Joshua Ulrich wrote:
>>>
On Mon, Sep 30, 2013 at 7:33 AM, Milan Bouchet-Valat
wrot
Le vendredi 04 octobre 2013 à 07:55 -0400, Duncan Murdoch a écrit :
> On 13-10-04 7:31 AM, Joshua Ulrich wrote:
> > On Tue, Oct 1, 2013 at 11:29 AM, David Winsemius
> > wrote:
> >>
> >> On Sep 30, 2013, at 6:38 AM, Joshua Ulrich wrote:
> >>
> >>> On Mon, Sep 30, 2013 at 7:33 AM, Milan Bouchet-Val
Le vendredi 04 octobre 2013 à 07:34 -0500, Joshua Ulrich a écrit :
> On Thu, Oct 3, 2013 at 9:44 AM, Jens Oehlschlägel
> wrote:
> > I agree that quoted integer columns are not the most efficient way of
> > delivering csv-files. However, the sad reality is that one receives such
> > formats and sti
On Thu, Oct 3, 2013 at 9:44 AM, Jens Oehlschlägel
wrote:
> I agree that quoted integer columns are not the most efficient way of
> delivering csv-files. However, the sad reality is that one receives such
> formats and still needs to read the data. Therefore it is not helpful to
> state that one sh
On 13-10-04 7:31 AM, Joshua Ulrich wrote:
On Tue, Oct 1, 2013 at 11:29 AM, David Winsemius wrote:
On Sep 30, 2013, at 6:38 AM, Joshua Ulrich wrote:
On Mon, Sep 30, 2013 at 7:33 AM, Milan Bouchet-Valat wrote:
Hi!
It seems that read.table() in R 3.0.1 (Linux 64-bit) does not consider
quote
On Tue, Oct 1, 2013 at 11:29 AM, David Winsemius wrote:
>
> On Sep 30, 2013, at 6:38 AM, Joshua Ulrich wrote:
>
>> On Mon, Sep 30, 2013 at 7:33 AM, Milan Bouchet-Valat
>> wrote:
>>> Hi!
>>>
>>>
>>> It seems that read.table() in R 3.0.1 (Linux 64-bit) does not consider
>>> quoted integers as an a
On Sep 30, 2013, at 6:38 AM, Joshua Ulrich wrote:
> On Mon, Sep 30, 2013 at 7:33 AM, Milan Bouchet-Valat
> wrote:
>> Hi!
>>
>>
>> It seems that read.table() in R 3.0.1 (Linux 64-bit) does not consider
>> quoted integers as an acceptable value for columns for which
>> colClasses="integer". But
On Tue, Oct 1, 2013 at 5:50 AM, Peter Meilstrup
wrote:
>
> On Mon, Sep 30, 2013 at 8:10 AM, Joris Meys wrote:
>>
>> Regardless of whether "stored as character" is interpreted the R way or the
>> ASCII way, the point Joshua makes is rather valid. Mainly because
>> read.table has an argument quote
On Mon, Sep 30, 2013 at 8:10 AM, Joris Meys wrote:
> Regardless of whether "stored as character" is interpreted the R way or the
> ASCII way, the point Joshua makes is rather valid. Mainly because
> read.table has an argument quote with default value \"'. This means that at
> least according to R
On Mon, Sep 30, 2013 at 5:33 AM, Milan Bouchet-Valat wrote:
> Hi!
>
>
> It seems that read.table() in R 3.0.1 (Linux 64-bit) does not consider
> quoted integers as an acceptable value for columns for which
> colClasses="integer". But when colClasses is omitted, these columns are
> read as integer
On Mon, Sep 30, 2013 at 5:27 PM, Milan Bouchet-Valat wrote:
> Le lundi 30 septembre 2013 à 17:10 +0200, Joris Meys a écrit :
> > Regardless of whether "stored as character" is interpreted the R way
> > or the ASCII way, the point Joshua makes is rather valid. Mainly
> > because read.table has an a
Le lundi 30 septembre 2013 à 17:10 +0200, Joris Meys a écrit :
> Regardless of whether "stored as character" is interpreted the R way
> or the ASCII way, the point Joshua makes is rather valid. Mainly
> because read.table has an argument quote with default value \"'. This
> means that at least acco
It is after all an R-related mailing list, and professor Ripley has set a
certain standard ages ago ;)
On Mon, Sep 30, 2013 at 5:19 PM, Milan Bouchet-Valat wrote:
> Le lundi 30 septembre 2013 à 10:07 -0500, Joshua Ulrich a écrit :
> > On Mon, Sep 30, 2013 at 9:45 AM, Milan Bouchet-Valat
> wrote
Le lundi 30 septembre 2013 à 10:07 -0500, Joshua Ulrich a écrit :
> On Mon, Sep 30, 2013 at 9:45 AM, Milan Bouchet-Valat
> wrote:
> > Le lundi 30 septembre 2013 à 08:38 -0500, Joshua Ulrich a écrit :
> >> On Mon, Sep 30, 2013 at 7:33 AM, Milan Bouchet-Valat
> >> wrote:
> >> > Hi!
> >> >
> >> >
Regardless of whether "stored as character" is interpreted the R way or the
ASCII way, the point Joshua makes is rather valid. Mainly because
read.table has an argument quote with default value \"'. This means that at
least according to R, everything between either " or ' should be seen as of
type
On Mon, Sep 30, 2013 at 9:45 AM, Milan Bouchet-Valat wrote:
> Le lundi 30 septembre 2013 à 08:38 -0500, Joshua Ulrich a écrit :
>> On Mon, Sep 30, 2013 at 7:33 AM, Milan Bouchet-Valat
>> wrote:
>> > Hi!
>> >
>> >
>> > It seems that read.table() in R 3.0.1 (Linux 64-bit) does not consider
>> > qu
Le lundi 30 septembre 2013 à 08:38 -0500, Joshua Ulrich a écrit :
> On Mon, Sep 30, 2013 at 7:33 AM, Milan Bouchet-Valat
> wrote:
> > Hi!
> >
> >
> > It seems that read.table() in R 3.0.1 (Linux 64-bit) does not consider
> > quoted integers as an acceptable value for columns for which
> > colClas
On Mon, Sep 30, 2013 at 7:33 AM, Milan Bouchet-Valat wrote:
> Hi!
>
>
> It seems that read.table() in R 3.0.1 (Linux 64-bit) does not consider
> quoted integers as an acceptable value for columns for which
> colClasses="integer". But when colClasses is omitted, these columns are
> read as integer
On Fri, Aug 26, 2011 at 9:41 PM, Scott wrote:
> It does look like you've got a memory issue. perhaps using
> as.is=TRUE, and/or stringsAsFactors=FALSE will help as optional arguments
> to read.table
>
> if you don't specify these sorts of things, R can have to look through the
> file and figure o
On Fri, Aug 26, 2011 at 11:55 PM, Ben Bolker wrote:
> Scott googlemail.com> writes:
>
>>
>> It does look like you've got a memory issue. perhaps using
>> as.is=TRUE, and/or stringsAsFactors=FALSE will help as optional arguments
>> to read.table
>>
>> if you don't specify these sorts of things,
Scott googlemail.com> writes:
>
> It does look like you've got a memory issue. perhaps using
> as.is=TRUE, and/or stringsAsFactors=FALSE will help as optional arguments
> to read.table
>
> if you don't specify these sorts of things, R can have to look through the
> file and figure out which
It does look like you've got a memory issue. perhaps using
as.is=TRUE, and/or stringsAsFactors=FALSE will help as optional arguments
to read.table
if you don't specify these sorts of things, R can have to look through the
file and figure out which columns are characters/factors etc and so the
l
One further note:
No problem with R version 2.13.0 (2011-04-13)
Göran
2011/8/26 Göran Broström :
> Another one:
>
> The 'death.RData' was created about a year ago, but ...? Same info as below.
>
> Göran
>
>> load("../Data/death.RData")
>> summary(death)
>
> *** caught segfault ***
> address 0x
Another one:
The 'death.RData' was created about a year ago, but ...? Same info as below.
Göran
> load("../Data/death.RData")
> summary(death)
*** caught segfault ***
address 0x4e04959, cause 'memory not mapped'
Traceback:
1: match(x, levels)
2: factor(a, levels = ll[!(ll %in% exclude)]
Is there a compelling reason to have strip.white default
to FALSE? It seems to me that it would be more common to
want the TRUE case.
Having said that, I must confess that I've never had the
problem Erik describes.
-Peter Ehlers
On 2010-06-29 17:14, Matt Shotwell wrote:
The document RFC 4180
The document RFC 4180 (which appears to be the CSV standard used by R,
see ?read.table) considers spaces to be part of the fielded value. Some
have taken this to mean that all white space characters should be
considered part of the fielded value, though the RFC is not explicit
here. Hence, this beh
Hi,=20
Sorry, didn't notice a quote in the longer line that was causing the
problem. Everything works fine with read.table(quote=3D"",...). Please
remove PR#13626 report - I tried to do so from the bug tracking web
interface, but did not have the permissions. Thanks!
Notice: This e-mail messa
On Wed, 11 Jun 2008 [EMAIL PROTECTED] wrote:
> Full_Name: Juho Vuori
> Version: 2.7.0 (2008-04-22)
> OS: Linux poseidon.fimr.fi 2.6.23.17-88.fc7PAE #1 SMP Thu May 15 00:22:53 EDT
> 2008 i686 i686 i386 GNU/Linux
> Submission from: (NULL) (193.166.188.194)
>
>
> Calling read.table() twice the follo
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
--27464147-621931503-1212766709=:10799
Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 8BIT
Not a bug, sinc
On Mon, 21 Jan 2008, David Reitter wrote:
On 21 Jan 2008, at 11:38, Prof Brian Ripley wrote:
The first column of your file repeats 0 and 1, and your specification asked
for the first column to be taken as the row names: from the help file
If 'row.names' is not specified and the header li
--Apple-Mail-1--729254567
Content-Type: text/plain;
charset=US-ASCII;
format=flowed;
delsp=yes
Content-Transfer-Encoding: 7bit
On 21 Jan 2008, at 11:38, Prof Brian Ripley wrote:
>
> The first column of your file repeats 0 and 1, and your
> specification asked for the fir
On Sun, 20 Jan 2008, [EMAIL PROTECTED] wrote:
>
> --Apple-Mail-44--797532055
> Content-Type: text/plain;
> charset=US-ASCII;
> format=flowed;
> delsp=yes
> Content-Transfer-Encoding: 7bit
>
> I believe read.table may report misleading errors. In this example,
> where a header lin
[EMAIL PROTECTED] wrote:
> --Apple-Mail-44--797532055
> Content-Type: text/plain;
> charset=US-ASCII;
> format=flowed;
> delsp=yes
> Content-Transfer-Encoding: 7bit
>
> I believe read.table may report misleading errors. In this example,
> where a header line in a file has an inc
On Wed, Jan 09, 2008 at 03:27:31PM -0500, Gabor Grothendieck wrote:
> Use file.file()$size to find out how large the file is
> and skip files larger than some cutoff.
You presumably meant file.info()$size
Dirk
>
> On Jan 9, 2008 2:01 PM, Derek Stephen Elmerick <[EMAIL PROTECTED]> wrote:
> > He
On Wed, 9 Jan 2008, Derek Stephen Elmerick wrote:
> Hello ?
>
> I am trying to write code that will read in multiple datasets;
> however, I would like to skip any dataset where the read-in process
> takes longer than some fixed cutoff. A generic version of the function
> is the following:
>
> for(
That was supposed to be file.info()$size
On Jan 9, 2008 3:27 PM, Gabor Grothendieck <[EMAIL PROTECTED]> wrote:
> Use file.file()$size to find out how large the file is
> and skip files larger than some cutoff.
>
> On Jan 9, 2008 2:01 PM, Derek Stephen Elmerick <[EMAIL PROTECTED]> wrote:
>
> > Hell
Use file.file()$size to find out how large the file is
and skip files larger than some cutoff.
On Jan 9, 2008 2:01 PM, Derek Stephen Elmerick <[EMAIL PROTECTED]> wrote:
> Hello –
>
> I am trying to write code that will read in multiple datasets;
> however, I would like to skip any dataset where th
On Jan 9, 2008 2:01 PM, Derek Stephen Elmerick <[EMAIL PROTECTED]> wrote:
> Hello â
>
> I am trying to write code that will read in multiple datasets;
> however, I would like to skip any dataset where the read-in process
> takes longer than some fixed cutoff. A generic version of the function
>
It's the quoting character(s). This following seems to read the file in
correctly:
R> DF <- read.table("http://llmpp.nih.gov/DLBCL/NEJM_Web_Fig1data";,
+ header = TRUE, sep = "\t", quote="")
R> str(DF)
'data.frame': 7399 obs. of 295 variables:
[...]
If I have to guess, it's
On Mon, 2007-05-14 at 23:41 +0200, [EMAIL PROTECTED] wrote:
> Full_Name: vax, 9000
> Version: 2.4.0, 2.2.1
> OS: 2.4.0: Mac OS X; 2.2.1: Linux
> Submission from: (NULL) (192.35.79.70)
>
>
> To reproduce this bug, first go to the website "http://llmpp.nih.gov/DLBCL/";
> and
> download the 14.8M d
Arnost.Komarek med.kuleuven.be> writes:
>
> Dear R Core Team,
>
> Help to 'read.table' claims that
> 'read.csv' is identical to 'read.table' except for the defaults.
Pedantically speaking, the claim is true: the difference is
in the default for the quote= argument.
>
> However, 'read.tabl
Prof Brian Ripley <[EMAIL PROTECTED]> writes:
> > Sorry, unclear. We already change quote= for read.delim and read.csv,
> > and I was suggesting also to modify the default for comment.char for
> > those functions, but definitely not for read.table.
> >
> > Arguably, those functions are there to ha
On Wed, 5 Jul 2006, Peter Dalgaard wrote:
> Prof Brian Ripley <[EMAIL PROTECTED]> writes:
>
>> On Wed, 5 Jul 2006, Peter Dalgaard wrote:
>>
>>> [EMAIL PROTECTED] writes:
>>>
(1) read.table(), with sep="\t", identifies 13 our of 1400 records,
in a file with 1400 records of 3 fields each,
Prof Brian Ripley <[EMAIL PROTECTED]> writes:
> On Wed, 5 Jul 2006, Peter Dalgaard wrote:
>
> > [EMAIL PROTECTED] writes:
> >
> >> (1) read.table(), with sep="\t", identifies 13 our of 1400 records,
> >> in a file with 1400 records of 3 fields each, as having only 2 fields.
> >> This happens unde
On Wed, 5 Jul 2006, Peter Dalgaard wrote:
> [EMAIL PROTECTED] writes:
>
>> (1) read.table(), with sep="\t", identifies 13 our of 1400 records,
>> in a file with 1400 records of 3 fields each, as having only 2 fields.
>> This happens under version 2.3.1 for Windows as well as with
>> R 2.3.1 for Ma
[EMAIL PROTECTED] writes:
> (1) read.table(), with sep="\t", identifies 13 our of 1400 records,
> in a file with 1400 records of 3 fields each, as having only 2 fields.
> This happens under version 2.3.1 for Windows as well as with
> R 2.3.1 for Mac OS X, and with R-devel under Mac OS X.
> [R vers
[EMAIL PROTECTED] writes:
> On Fri, 20 Jan 2006 [EMAIL PROTECTED] wrote:
>
> > Full_Name: emiel ver loren
> > Version: 2.2.0
>
> We do ask you not to send reports on obselete versions of R.
Well, we might forgive that (please at least check against the current
NEWS file), but
USING FAKE EMAIL
On Fri, 20 Jan 2006 [EMAIL PROTECTED] wrote:
> Full_Name: emiel ver loren
> Version: 2.2.0
> OS: Windows XP
> Submission from: (NULL) (145.117.31.248)
>
>
> Dear R-community and developers,
>
> I have been trying to read in a tab delimeted file where the column names and
> the row names are of
[EMAIL PROTECTED] writes:
> Full_Name: emiel ver loren
> Version: 2.2.0
> OS: Windows XP
> Submission from: (NULL) (145.117.31.248)
>
>
> Dear R-community and developers,
>
> I have been trying to read in a tab delimeted file where the column names and
> the row names are of the form "GO:05
Please do not report documented behaviour as a bug!
See the 'check.names' argument to read.table.
In your second example you are applying as.character to a data frame, and
you seem not to realize that. We specifically ask you NOT to use R-bugs
to ask questions. (What is happening is that you g
, everyone who needs to edit this file can just do
so in emacs, and putting quotes around the fields is an easy fix. Thanks
Robert
-Original Message-
From: Prof Brian Ripley [mailto:[EMAIL PROTECTED]
Sent: Friday, October 21, 2005 9:59 AM
To: McGehee, Robert
Cc: r-devel@stat.math.ethz.
data(), but any feedback on this is welcomed.
Using quotes, e.g. "A B C" may work?
>
> Thanks,
> Robert
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 21, 2005 1:58 AM
> To: r-devel@stat.math.e
CTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, October 21, 2005 1:58 AM
To: r-devel@stat.math.ethz.ch
Cc: [EMAIL PROTECTED]
Subject: Re: [Rd] read.table error upon package installation (PR#8230)
What is the R error here?
The default delimiter in read.table is not \t but whitespace, so the
first
exam
What is the R error here?
The default delimiter in read.table is not \t but whitespace, so the first
example has 2 and 3 rows (fine for header=T) and the second has 2 and 4
rows.
On Fri, 21 Oct 2005 [EMAIL PROTECTED] wrote:
> Upon upgrading to R 2.2.0 on my Windows box, I found that one of my
72 matches
Mail list logo
