Hi, Rui et al.:
On 6/29/24 14:24, Rui Barradas wrote:
Às 17:02 de 28/06/2024, Spencer Graves escreveu:
Hello, All:
I'm getting strange errors with write.csv with some objects of
class c('findFn', 'data.frame'). Consider the following:
df1 <- data.frame(x=1)
class(df1) <- c('findFn
Às 17:02 de 28/06/2024, Spencer Graves escreveu:
Hello, All:
I'm getting strange errors with write.csv with some objects of
class c('findFn', 'data.frame'). Consider the following:
df1 <- data.frame(x=1)
class(df1) <- c('findFn', 'data.frame')
write.csv(df1, 'df1.csv')
# Error in x$P
В Fri, 28 Jun 2024 11:02:12 -0500
Spencer Graves пишет:
> df1 <- data.frame(x=1)
> class(df1) <- c('findFn', 'data.frame')
> write.csv(df1, 'df1.csv')
> # Error in x$Package : $ operator is invalid for atomic vectors
Judging by the traceback, only data frames that have a Package column
should ha
Hello, All:
I'm getting strange errors with write.csv with some objects of class
c('findFn', 'data.frame'). Consider the following:
df1 <- data.frame(x=1)
class(df1) <- c('findFn', 'data.frame')
write.csv(df1, 'df1.csv')
# Error in x$Package : $ operator is invalid for atomic vectors
df2
Hi Toby et al,
On Wed, Mar 29, 2023 at 10:24 PM Toby Hocking wrote:
> Dear R-devel,
> I did a systematic comparison of write.csv with similar functions, and
> observed two asymptotic inefficiencies that could be improved.
>
> 1. write.csv is quadratic time (N^2) in the number of columns N.
> C
Dear R-devel,
I did a systematic comparison of write.csv with similar functions, and
observed two asymptotic inefficiencies that could be improved.
1. write.csv is quadratic time (N^2) in the number of columns N.
Can write.csv be improved to use a linear time algorithm, so it can handle
CSV files
-project.org; Lipatz Jean-Luc
Subject: Re: [Rd] write.csv
This is a bit difficult:
R binaries (both for R base and R packages) are still built with Windows Server
2008 and my desktop machine is Windows 7, hence at least currently such a check
would not get executed on the machines R core / CRAN use
Murdoch
; Jim Hester
Cc: r-devel@r-project.org; Lipatz Jean-Luc
Subject: Re: [Rd] write.csv
This is a bit difficult:
R binaries (both for R base and R packages) are still built with Windows Server
2008 and my desktop machine is Windows 7, hence at least currently such a check
would not get executed
in
the environment where automated builds/tests for windows are run.
-Original Message-
From: Nathan Sosnovske
Sent: Tuesday, July 4, 2017 8:02 AM
To: 'Duncan Murdoch' ; Jim Hester
Cc: r-devel@r-project.org; Lipatz Jean-Luc
Subject: RE: [Rd] write.csv
The best way to test
where automated builds/tests for windows are run.
-Original Message-
From: Nathan Sosnovske
Sent: Tuesday, July 4, 2017 8:02 AM
To: 'Duncan Murdoch' ; Jim Hester
Cc: r-devel@r-project.org; Lipatz Jean-Luc
Subject: RE: [Rd] write.csv
The best way to test on Windows would p
tion on the filesystem (instead of a drive letter) so that drive letter
> conflicts don't come into play.
>
> -Original Message-
> From: R-devel [mailto:r-devel-boun...@r-project.org] On Behalf Of Duncan
> Murdoch
> Sent: Tuesday, July 4, 2017 7:53 AM
> To: Jim Hester
conflicts don't
come into play.
-Original Message-
From: R-devel [mailto:r-devel-boun...@r-project.org] On Behalf Of Duncan Murdoch
Sent: Tuesday, July 4, 2017 7:53 AM
To: Jim Hester
Cc: r-devel@r-project.org; Lipatz Jean-Luc
Subject: Re: [Rd] write.csv
On 04/07/2017 10:01 AM, Jim H
-Message d'origine-
De : Duncan Murdoch [mailto:murdoch.dun...@gmail.com]
Envoyé : mardi 4 juillet 2017 14:24
À : Lipatz Jean-Luc; r-devel@r-project.org
Objet : Re: [Rd] write.csv
On 04/07/2017 5:40 AM, Lipatz Jean-Luc wrote:
Hi all,
I am currently studying how to generalize t
there
> were any reports before yours.
>
> Duncan Murdoch
>
>
>> JLL
>>
>>
>> -Message d'origine-
>> De : Duncan Murdoch [mailto:murdoch.dun...@gmail.com]
>> Envoyé : mardi 4 juillet 2017 14:24
>> À : Lipatz Jean-Luc; r-devel@r-pr
oduced with a
> simple USB key and you cannot state that a disk will eternally be empty
> enough, specially when it has several users.
>
> JLL
>
>
> -Message d'origine-
> De : Duncan Murdoch [mailto:murdoch.dun...@gmail.com]
> Envoyé : mardi 4 juillet 2017 14:2
-project.org
Subject: Re: [Rd] write.csv
On 04/07/2017 8:46 AM, Nathan Sosnovske wrote:
> This doesn't really strike me as a bug. Lots of (most?) programming languages
> expect you to handle this as an error condition. If you tried the same thing
> in C you would get the same error.
T
looks as though the
write succeeded, when it didn't.
Duncan Murdoch
-Original Message-
From: R-devel [mailto:r-devel-boun...@r-project.org] On Behalf Of Lipatz
Jean-Luc
Sent: Tuesday, July 4, 2017 5:40 AM
To: Duncan Murdoch
Cc: r-devel@r-project.org
Subject: Re: [Rd] write.cs
---Message d'origine-
De : Duncan Murdoch [mailto:murdoch.dun...@gmail.com]
Envoyé : mardi 4 juillet 2017 14:24
À : Lipatz Jean-Luc; r-devel@r-project.org
Objet : Re: [Rd] write.csv
On 04/07/2017 5:40 AM, Lipatz Jean-Luc wrote:
Hi all,
I am currently studying how to generalize the usage of
Jean-Luc
Sent: Tuesday, July 4, 2017 5:40 AM
To: Duncan Murdoch
Cc: r-devel@r-project.org
Subject: Re: [Rd] write.csv
I would really like the bug fixed. At least this one, because I know people in
my institute using this function.
I understand your arguments about open source, but I also saw in
JLL
-Message d'origine-
De : Duncan Murdoch [mailto:murdoch.dun...@gmail.com]
Envoyé : mardi 4 juillet 2017 14:24
À : Lipatz Jean-Luc; r-devel@r-project.org
Objet : Re: [Rd] write.csv
On 04/07/2017 5:40 AM, Lipatz Jean-Luc wrote:
> Hi all,
>
> I am currently studying how to genera
On 04/07/2017 5:40 AM, Lipatz Jean-Luc wrote:
Hi all,
I am currently studying how to generalize the usage of R in my statistical
institute and I encountered a problem that I cannot declare on bugzilla (cannot
understand why).
Bugzilla was badly abused by spammers last year, so you need to ha
Hi all,
I am currently studying how to generalize the usage of R in my statistical
institute and I encountered a problem that I cannot declare on bugzilla (cannot
understand why). Sorry for trying this mailing list but I am really worried
about the problem itself and the possible implications i
Hi all,
Can help me understand why write.csv manipulates a call object instead
of simply calling write.table with modified arguments? I would have
written write.csv as:
write.csv <- function (...) {
Call <- match.call(expand.dots = TRUE)
for (argname in c("append", "col.names", "sep", "de
748
Für Umsatzsteuerzwecke: Ust-ID-Nr.: DE 251 168 597
-Ursprüngliche Nachricht-
Von: Paul Roebuck [mailto:[EMAIL PROTECTED]
Gesendet: Monday, October 27, 2008 05:59
An: R Development Mailing List
Cc: Albrecht, Dr. Stefan (AIM SE)
Betreff: Re: [Rd] write.csv(..., col.names = FALSE) (PR#1
On Fri, 24 Oct 2008 [EMAIL PROTECTED] wrote:
> in write.csv() it is not possible to set both
> row.names = FALSE, col.names = FALSE
> since the col.names = FALSE gets overwritten:
>
> > write.csv
> function (...)
> {
> Call <- match.call(expand.dots = TRUE)
> for (argname in c("col.names",
Full_Name: Stefan Albrecht
Version: 2.7.2 (and 2.8.0)
OS: Windows NT
Submission from: (NULL) (194.127.8.17)
Dear R Debug-Team,
in write.csv() it is not possible to set both
row.names = FALSE, col.names = FALSE
since the col.names = FALSE gets overwritten:
> write.csv
function (...)
{
Call
On Thu, 24 Nov 2005, Roger Peng wrote:
> Okay, upon further examination, it appears that it works fine if you set
> 'row.names = FALSE' as opposed to 'row.names = F'.
Yes. Adding eval.parent() (not eval()) would be better, though, as it
would allow a variable (like F) to be used. I rather like
Roger Peng <[EMAIL PROTECTED]> writes:
> Okay, upon further examination, it appears that it works fine if you set
> 'row.names = FALSE' as opposed to 'row.names = F'.
Nope. It's still a bug and you're quite right that eval() is needed.
We can't have that an argument only works when supplied as a
Okay, upon further examination, it appears that it works fine if you set
'row.names = FALSE' as opposed to 'row.names = F'.
-roger
Roger Peng wrote:
> Upon replying to this email, I took a look at 'write.csv()' and noticed
> something interesting. I remember there being a discussion sometime i
Upon replying to this email, I took a look at 'write.csv()' and noticed
something interesting. I remember there being a discussion sometime in
the past about letting 'write.csv()' accept the 'row.names' argument.
However, I get the following error:
> write.csv(airquality, file = "myfile.csv",
On Thu, 24 Nov 2005, Roger Peng wrote:
> If you don't want the row names, as 'write.csv()' writes out by default,
> try
>
> write.table(, file = "myfile.csv", sep = ",", row.names = FALSE)
Or, better (since it sets other args to the appropriate values),
write.csv(, file = "myfile.csv", row.names
I don't understand very well if your problem is rownames or column names,
but what you want must be :
row.names=FALSE and/or col.names=FALSE, which are arguments of the function
'write.table()'
don't think you need to load any particular package for that.
see also :
--
If you don't want the row names, as 'write.csv()' writes out by default,
try
write.table(, file = "myfile.csv", sep = ",", row.names = FALSE)
-roger
Sven Schaltenbrand wrote:
> hallo,
>
> i have a problem by writing a csv file
> the first colum is filled with index numbers from 1 to n.
> i ha
On Thu, 2005-11-24 at 17:00 +0100, Sven Schaltenbrand wrote:
> hallo,
>
> i have a problem by writing a csv file
> the first colum is filled with index numbers from 1 to n.
> i have to unique two csv files once a week while one file is always the
> same.
> can anybody tell me, how to write the da
hallo,
i have a problem by writing a csv file
the first colum is filled with index numbers from 1 to n.
i have to unique two csv files once a week while one file is always the
same.
can anybody tell me, how to write the dataset into a csv file without the
first row of the indexnumbers.
x[,-1] doe
I just checked the svn. I did not realize it had been changed that way
so you are right, its better and possibly marginally acceptable although
I do think it would be preferable to set the defaults rather than the
values though I would no longer argue as strongly.
On 7/7/05, Duncan Murdoch <[EMAI
On 7/7/2005 12:38 PM, Gabor Grothendieck wrote:
> This may not be inconsistent with the documentation but it is
> inconsistent with good practice. Wrappers should, in general,
> set the default values, as the poster rightly indicated, and not the
> values themselves. Its not a coincidence that
This may not be inconsistent with the documentation but it is
inconsistent with good practice. Wrappers should, in general,
set the default values, as the poster rightly indicated, and not the
values themselves. Its not a coincidence that multiple people
have mentioned this.
On 7/7/05, [EMAIL
This topic already came up about a week ago on R-devel
Subject: write.csv suggestion
[ too bad that "R-devel" is not available via RSiteSearch() ...
{I could send you the back archives, Jon, if you are interested} ]
There, Brian Ripley, explained why this is not a bug, since
it works as do
The write.csv() function is currently implemented as
function (..., col.names=NA, sep=",", qmethod="double")
{
write.table(..., col.names=NA, sep=",", qmethod="double")
}
Surely, it should be
function (..., col.names=NA, sep=",", qmethod="double")
{
write.table(..., col.
eemed suboptimal (to me) because one would have to read the
> code to know that the col.names = TRUE option was not being passed along
> to write.table (as I expected).
>
> Best,
> Robert
>
> -Original Message-
> From: Prof Brian Ripley [mailto:[EMAIL PROTECTED]
> Sent:
y [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 29, 2005 4:16 PM
To: McGehee, Robert
Cc: r-devel@stat.math.ethz.ch
Subject: Re: [Rd] write.csv suggestion
The help page says
By default there is no column name for a column of row names. If
'col.names = NA' and 'row.nam
The help page says
By default there is no column name for a column of row names. If
'col.names = NA' and 'row.names = TRUE' a blank column name is
added. This can be used to write CSV files for input to
spreadsheets. 'write.csv' and 'write.csv2' provide convenience
Hello all,
I had some trouble recently with write.csv because I couldn't change one
of the default options. A quick view of the code showed that the
function was not defined in the most optimal way.
Currently,
write.csv <- function (..., col.names = NA, sep = ",", qmethod =
"double")
wri
44 matches
Mail list logo
