similar to: strsignif.c, util.c (PR#10635)

Displaying 20 results from an estimated 2000 matches similar to: "strsignif.c, util.c (PR#10635)"

2008 Feb 17
2
Mac OS X 2.5.1 / reg-plot.R / tr (PR#10781)
In building R 2.6.2 from source for Mac OS X 2.5.1 (with i686-apple-darwin9-gcc-4.0.1), 'make check' fails. The failure is in reg-plot.R, and occurs because Mac OS X's 'tr' command (invoked by Rdiff to strip carriage returns) regards the dagger sign in reg-plot.ps as an illegal byte sequence. I'm surprised that this doesn't seem to have been reported before, but it
2010 Jan 28
2
src/library/grid/src/grid.c (PR#14199)
At around line 2590, in function gridRect() in src/library/grid/src/grid.c (at the latest svn revision, 50745), ought not temp, www and hhh to be PROTECTed within this block? Andrew
2006 Jan 27
1
rbind/cbind unimplemented for raw (RAWSXP) types. (PR#8529)
Full_Name: Hin-Tak Leung Version: R 2.2.1 OS: x86_64-redhat-linux-gnu Submission from: (NULL) (131.111.186.92) rbind/cbind is unimplemented for raw (RAWSXP) types. I have a working patch implementing the functionality, to follow. --please do not edit the information below-- Version: platform = x86_64-redhat-linux-gnu arch = x86_64 os = linux-gnu system = x86_64, linux-gnu status = major
2006 Nov 21
2
packBits (PR#9374)
Full_Name: Prokaj Vilmos Version: R 2-4-0 OS: Windows Submission from: (NULL) (193.224.79.8) PackBits(rbinom(32,1,0.5)==1,"integer") does not work. z<-packBits(rbinom(32,1,.5)==1,"integer") Error in packBits(x, type) : argument 'x' must be raw, integer or logical Taking a closer look at the C code main/character.c do_packBits rutin one can find the following
2017 Mar 29
3
Transferring ownership of R-managed buffer
I have a use case where I would like to create an SEXP around an existing buffer that is managed by R, thus avoiding a copy operation. If I have something like: void *p = (void*) RAW(PROTECT(Rf_allocVector(RAWSXP, n))); ... additional maniupulation ... SEXP x = somefunc(SXPTYPE, n, p); // ???? Is there a "placement" constructor available? (I have arranged for the corresponding
2010 Aug 22
1
Handle RAWSXP in inspect.c:typename()
Hi all I had written a gdb macro to dump the string representation of an SEXPREC type when I realised everything I needed was in inspect.c already in the typename() function. However, the typename function doesnt handle the RAWSXP type, so if possible, could the following patch be applied (I've just put in inline as it is a trivial 1-liner)? Index: src/main/inspect.c
2009 May 10
2
In C, a fast way to slice a vector?
Hello, Suppose in the following code, PROTECT(sr = R_tryEval( .... )) sr is a RAWSXP vector. I wish to return another RAWSXP starting at position 13 onwards (base=0). I could create another RAWSXP of the correct length and then memcpy the required bytes and length to this new one. However is there a more efficient method? Regards Saptarshi Guha
2010 Jun 19
1
more powerful iconv
R community, As you may know, R's iconv doesn't work well converting to and from encodings that allow embedded nulls. For example > iconv("foo", to="UTF-16") Error in iconv("foo", to = "UTF-16") : embedded nul in string: '\xff\xfef\0o\0o\0' However, I don't believe embedded nulls are at issue here, but rather that R's iconv
2005 Aug 20
1
Implementing a single-precision class with raw
A package that I develop (xcms) sometimes needs to read and process vectors several hundreds of megabytes in size. (They only represent parts of a large data sets which can approach nearly 100GB.) Unfortunately, R sometimes hits the 2GB memory limit of Win32. To help cut the memory footprint in half, I'm implementing a "float" class as a subclass of "raw". Because
2009 Jul 09
1
bug in seq_along
Using the IRanges package from Bioconductor and somewhat recent R-2.9.1. ov = IRanges(1:3, 4:6) length(ov) # 3 seq(along = ov) # 1 2 3 as wanted seq_along(ov) # 1! I had expected that the last line would yield 1:3. My guess is that somehow seq_along don't utilize that ov is an S4 class with a length method. The last line of the *Details* section of ?seq has a typeo. Currently it is
2001 Jan 25
1
problems compiling R under digital unix 4.0d (PR#826)
Dear Sirs, I am trying to compile R v1.2.1 under Digital Unix 4.0D. The configure-script runs without any problems but during 'make' I receive the following error-message: [......] g77 -mieee -g -O2 -c dtrco.f -o dtrco.o g77 -mieee -g -O2 -c dtrsl.f -o dtrsl.o g77 -mieee -g -O2 -c eigen.f -o eigen.o g77 -mieee -g -O2 -c lminfl.f -o lminfl.o ar cr libappl.a Rsock.o approx.o bakslv.o
2009 Dec 16
2
What is the fastest way to see what are in an RData file?
Currently, I load the RData file then ls() and str(). But loading the file takes too long if the file is big. Most of the time, I only interested what the variables are in the the file and the attributes of the variables (like if it is a data.frame, matrix, what are the colnames/rownames, etc.) I'm wondering if there is any facility in R to help me avoid loading the whole file.
2005 Mar 29
1
final stages of installing R - please help?
Hello, This morning I downloaded, unzipped, and compiled the latest version of R for unix, in my HOME/APPLICATIONS directory. My current unix machine is a sparc-sun-solaris2.9, running SunOS 5.9. Here are the last few lines of the output following ./configure: R is now configured for sparc-sun-solaris2.9 Source directory: . Installation directory: /usr/local C compiler:
2005 Mar 10
1
R_alloc with more than 2GB (PR#7721)
Full_Name: Wolfgang Huber Version: R-devel_2005-03-10 OS: alphaev68-dec-osf4.0f Submission from: (NULL) (62.253.128.15) This report concerns allocation of large (>2^31 byte) chunks of memory with R_alloc. I suspect it is a bug/typo but please don't hate me if it's actually a feature: In R, I can happily create large matrices: > a= matrix(0, nrow=191481, ncol=3063) > dim(a) [1]
2012 Mar 08
2
On R performance
I've been working on an R performance academic project for the last couple years which has involved writing an interpreter for R from scratch and a JIT for R vector operations. With the recent comments on Julia, I thought I'd share some thoughts from my experience since they differ substantially from the common speculation on R performance. I went into the project thinking that R would
2015 Mar 17
2
Reduce memory peak when serializing to raw vectors
Hi, I've been doing some tests using serialize() to a raw vector: df <- data.frame(runif(50e6,1,10)) ser <- serialize(df,NULL) In this example the data frame and the serialized raw vector occupy ~400MB each, for a total of ~800M. However the memory peak during serialize() is ~1.2GB: $ cat /proc/15155/status |grep Vm ... VmHWM: 1207792 kB VmRSS: 817272 kB We work with very
2004 Jun 03
2
returning strings to R from C functions
I'm using .C() and .External() and have no problems sending integers, reals or strings from R to C. Nor do I have problems sending integers or reals back from C to R. But I'm pulling my hair out trying to set a string value in a C function and then sending it back from C to to R. I've searched the usual sources and tried various casts, macros and allocation schemes, but I'm
2008 Mar 12
3
Different (tree) event behaviors across platforms
Hi all, I''m currently writing a simple outliner application as a tutorial on wxRuby (both will be soon released ;-) ) I tested this application on Windows and Linux and found that the tree event behavior : - is sometime strange on each platform - is also different on each platform Even if I managed to take care of these differences in the application, I''m just wondering if : -
2015 Mar 17
2
Reduce memory peak when serializing to raw vectors
Presumably one could stream over the data twice, the first to get the size, without storing the data. Slower but more memory efficient, unless I'm missing something. Michael On Tue, Mar 17, 2015 at 2:03 PM, Simon Urbanek <simon.urbanek at r-project.org> wrote: > Jorge, > > what you propose is not possible because the size of the output is > unknown, that's why a
2010 Aug 26
2
Speeding up transpose
I've looked at how to speed up the transpose function in R (ie, t(X)). The existing code does the work with loops like the following: for (i = 0; i < len; i++) REAL(r)[i] = REAL(a)[(i / ncol) + (i % ncol) * nrow]; It seems a bit optimistic to expect a compiler to produce good code from this. I've re-written these loops as follows: for (i = 0, j = 0; i<len; i +=