similar to: write.table with quote=TRUE fails on nested data.frames

Displaying 20 results from an estimated 700 matches similar to: "write.table with quote=TRUE fails on nested data.frames"

2008 Mar 10
2
write.table with row.names=FALSE unnecessarily slow?
write.table with large data frames takes quite a long time > system.time({ + write.table(df, '/tmp/dftest.txt', row.names=FALSE) + }, gcFirst=TRUE) user system elapsed 97.302 1.532 98.837 A reason is because dimnames is always called, causing 'anonymous' row names to be created as character vectors. Avoiding this in src/library/utils, along the lines of Index:
2017 Mar 20
2
IO error when writing to disk
Hello, Here a small improvement for R. When you use the function write.table, if the disk is full for example, the function doesn't return an error and the file is written but truncated. It can be a source of mistakes because you can then copy the output file and think everything is ok. How to reproduce ------------------------- >> write.csv(1:10000000, 'path') You must have
2006 Jun 29
1
write.table does not quote col.names properly (PR#9044)
Full_Name: Michael Toews Version: 2.3.1 OS: Mac OS 10.4.6 and WinXP/SP2 Submission from: (NULL) (24.80.163.133) This bug also affects related functions (write.csv, etc.), and can be demonstrated using either a matrix or data frame: m <- matrix(1:9,nrow=3, dimnames=list(c("A","B","C"), c("I","II","III")))
2020 Nov 19
1
Learning to build applications
I have managed to get through the qtmake stage of compiling the current github version of pgmodeler on CentOS 7 but make && make install fails with: make && make install cd libutils/ && ( test -e Makefile || /bin/qmake-qt5 -o Makefile /home/h/pgmodeler/libutils/libutils.pro CONFIG+=release PREFIX= BINDIR= PRIVATEBINDIR= PRIVATELIBDIR=/lib ) && make -f Makefile
2007 Jul 13
0
KWD crashes when opening OOo
Hello, KWD crashes almost regularly when trying to start OpenOffice.org. I've attached two output files from valgrind to this e-mail (as suggested by David Reveman in another mail 11.7): Use something like: valgrind --tool=memcheck kde-window-decorator .... I'm using Trevino's git version of Compiz in up-to-date Kubuntu Feisty system. Compiz version is
2009 Aug 17
1
image() generates many border lines in pdf, not on screen (quartz) - R 2.9.1 GUI 1.28 Tiger build 32-bit (5444) - OS X 10.5.8
Dear all, I have invested substantial amount of work in a complicated, yet on screen perfect looking graph that uses image(). Unfortunately saving it as pdf (or quartz.save at high resolution) all generate very disturbing border lines around each small rectangle that image() has drawn. While using Preview it helps to turn off antialiasing to make those faint lines disappear on screen
2004 Nov 24
2
an R function to search on Prof. Baron's site
Inspired by the functions that Barry Rawlingson and Dave Forrest posted for searching Rwiki and R-help archive, I've made up a function that does the search on Prof. Baron's site (Thanks to Prof. Baron's help on setting up the query string!): RSiteSearch <- function(string, restrict="Rhelp", format="long", sortby="score",
2005 Jul 07
1
write.csv (PR#7992)
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.names=col.names, sep=sep,
2009 Nov 02
1
two small wishes (with code sugegstions) for R-core
Dear R developers, It would be great if you could implement the two minor code changes suggested below, which would help processing large objects in R. Jens Oehlschl?gel # Wish no. 1: let [.AsIs return the class AFTER subsetting, not the class of the original object # Wish no. 2: adjust write.csv and write.csv2 for multiple calls in chunked writing # Rationale no. 1: a couple of packages
2004 Dec 23
1
searching Jonathan Baron's R Site
First, my site will be down December 27-28 because of a network upgrade at Penn. It will also be down at least one day before that, while I upgrade the operating system. (And another day some time in January because of a planned power outage.) Second, I have replaced the search engine in my R site: http://finzi.psych.upenn.edu/ I am now using Namazu instead of HtDig. The direct link to the
2005 Jun 29
2
write.csv suggestion
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") write.table(..., col.names = NA, sep = ",", qmethod = "double")
2011 Aug 25
2
Using write.table i have a table with two columns i would like to save it as an excel file
Using write.table i would like to save data as an excel file to a folder. I am not too sure how to write the file path or what to name the file. I would appreciate any feedback. > write.table(x, file = "", append = FALSE, quote = TRUE, sep = " ", + eol = "\n", na = "NA", dec = ".", row.names = TRUE, + col.names =
2014 Feb 26
1
[PATCH v5 1/8] qspinlock: Introducing a 4-byte queue spinlock implementation
On Wed, Feb 26, 2014 at 10:14:21AM -0500, Waiman Long wrote: > +static void put_qnode(void) > +{ > + struct qnode_set *qset = this_cpu_ptr(&qnset); > + > + qset->node_idx--; > +} That very much wants to be: this_cpu_dec().
2014 Feb 26
1
[PATCH v5 1/8] qspinlock: Introducing a 4-byte queue spinlock implementation
On Wed, Feb 26, 2014 at 10:14:21AM -0500, Waiman Long wrote: > +static void put_qnode(void) > +{ > + struct qnode_set *qset = this_cpu_ptr(&qnset); > + > + qset->node_idx--; > +} That very much wants to be: this_cpu_dec().
2020 Jul 25
0
Guidelines when to use LF vs CRLF ("\n" vs. "\r\n") on Windows for new lines (line endings)?
On 25/07/2020 4:48 p.m., nospam at altfeld-im.de wrote: > Dear R developers, > > I am developing an R package which returns strings with new line codes. > I am not sure if I should use "\r\n" or "\n" in my returned strings on Windows platforms. > > What is the recommended best practice for package developers (and code in base R) for coding new lines in
2010 Feb 22
1
rownames cannot allocate vector of size
Hi, On R 2.10.1 for Windows, when I do the following to duplicate the structure of a large numeric matrix called matrix1: matrix2 <- matrix(0,nrow=nrow(matrix1),ncol=ncol(matrix1)) and then rownames(matrix2) <- rownames(matrix1) I get a "cannot allocate vector of size xxMb" error but if I instead do: rnames <- list() rnames <- rownames(matrix1) matrix2 <-
2010 Mar 22
1
sets package: converting a set to data frame?
I just started using nice package "sets" and I wonder if there are utilities to convert (some) sets to data frame (as in the example below) > library(sets) > a <- gset(elements = list(e('A', 0.1), e('B', 0.8))) > lst <- as.list(a) > nr <- length(lst) > rnames <- character() > for (i in 1:nr) rnames[i] <- lst[[i]] > df <-
2020 Jul 25
2
Guidelines when to use LF vs CRLF ("\n" vs. "\r\n") on Windows for new lines (line endings)?
Dear R developers, I am developing an R package which returns strings with new line codes. I am not sure if I should use "\r\n" or "\n" in my returned strings on Windows platforms. What is the recommended best practice for package developers (and code in base R) for coding new lines in strings? And just out of curiosity: What is the reason (or history) for preferring
2002 Jun 21
1
naming things in functions
Hello, I'm working with R version 1.5.0 in Windows. I've written a function (SummaryMat, segment below) which uses a loop to repeatedly call another function (PercentsMat, segment below). PercentsMat creates a matrix and adds rows to it each time it is called. I use deparse(substitute(...)) to get the names of the lists sent to PercentsMat to use them as row names in the generated
2008 Oct 24
1
write.csv(..., col.names = FALSE) (PR#13202)
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 <- match.call(expand.dots = TRUE) for (argname in c("col.names", "sep",