Displaying 20 results from an estimated 2000 matches similar to: "R-2.7.0 make check failure"
2008 Aug 27
1
S4 coercion
I am extending a DBI connection by
setClass("TSPostgreSQLConnection",
contains=c("PostgreSQLConnection","TSdbOptions"))
but the first time I use this I am getting a warning when it tries to
coerce the TSPostgreSQLConnection to a PostgreSQLConnection. After the
first use the warning stops, but the first warning is causing me
problems when I do automatic checks
2017 Jan 02
1
utils::ls.str(): Partial argument name 'digits' to seq() (should be digits.d?)
Should utils::ls.str() be updated as:
svn diff src/library/utils/R/str.R
Index: src/library/utils/R/str.R
===================================================================
--- src/library/utils/R/str.R (revision 71879)
+++ src/library/utils/R/str.R (working copy)
@@ -622,7 +622,7 @@
args$digits.d <- NULL
}
strargs <- c(list(max.level = max.level, give.attr = give.attr,
2017 Jan 04
0
cat(s, file): infinite loop of "invalid char string in output conversion" warnings with UTF-8 encoding
The below code snippet gives a single warning:
Warning message:
In cat(s, file = tempfile()) : invalid char string in output conversion
when n <= 10001, whereas with n >= 10002 it appears to be generating
the same warning in an infinite loop in the call to cat().
n <- 10002L
r <- raw(length = n)
r[] <- charToRaw(" ")
r[length(r)] <- as.raw(0xa9)
s <-
2023 Apr 30
0
Forcing a PROTECT Bug to Occur
On 4/30/23 06:05, Michael Milton wrote:
> Hi Tomas, thanks for the reply.
>
> I played with some of the factors you mentioned like allocating more
> INTSXP of the same size as vec_1, to little success. The thing that
> actually "worked" and caused a segfault, was simply allocating a
> larger vector the first time. 100 elements seemed to do it, but 10 or
> less
2012 Jul 25
2
reshape -> reshape 2: function cast changed?
Hi,
I used to use reshape and moved to reshape2 (R 2.15.1). Now I tried some of my older scripts and was surprised that my cast function wasn't working like before.
What I did/want to do:
1) Melt a dataframe based on a vector specifying column names as measure.vars. Thats working so far:
dfm <- melt(df, measure.vars=n, variable_name = "species", na.rm = FALSE)
2) Recast the
2006 Jan 02
0
boostrap astronomy problem
Hi,
I am an astronomer and somewhat new to boostrap statistics. I understand
the basic idea of bootstrap resampling, but am uncertain if it would be
useful in my case or not. My problem consists of maximizing a likelihood
function based on the velocities of a number of stars. My assumed
distribution of velocities of these stars is:
2004 Mar 11
2
No traceback available when using try(...)
Hello,
1. The Situation :
------------------------
The stack traceback is not available when error ouccured in a try(....)
-- test.R --------------------------------
f<-function(a){
return ( log(a) )
}
try(f("A"))
traceback()
-------------------------------------------
I get the following message :
> try(f("A"))
Error in log(x) : Non-numeric argument to mathematical
2007 Feb 19
2
"try"ing to understand condition handling
I'm confused by the page documenting tryCatch and friends.
I think it describes 3 separate mechanisms: tryCatch (in which control
returns to the invoking tryCatch), withCallHandlers (in which control
goes up to the calling handler/s but then continues from the point at
which signalCondition() was invoked), and withRestarts (I can't tell
where control ends up).
For tryCatch the docs say
2010 Dec 05
1
How to catch both warnings and errors?
Dear expeRts,
I am struggling with warning/error handling.
I would like to call a function which can produce either
a) normal output
b) a warning
c) an error
Since the function is called several (thousand) times in a loop, I would like
to proceed "quietly" and collect the warnings and errors [to deal with them at a
later point].
I have seen constructs with tryCatch (which can
2012 Oct 21
1
suppress *specific* warnings?
Not desperately important, but nice to have and possibly of use to
others, is the ability to suppress specific warnings rather than
suppressing warnings indiscriminately. I often know of a specific
warning that I want to ignore (because I know that's it's a false
positive/ignorable), but the current design of suppressWarnings() forces
me to ignore *any* warnings coming from the
2008 May 19
2
2.7.0 graphics changes and png devices
Hi,
I have a question about the graphics changes in 2.7.0. The example is
this bit of code:
par(mfcol = c(2, 3))
for(i in 1:6) plot(1:10, 1:10, xlab = "xlab", ylab = "ylab", main = "main")
In 2.7.0, if I do this interactively (using windows()), I get bold
titles. If I do this through a png device, I get regular weight
titles. If I do this in 2.6.2, both
2009 Apr 14
0
top level condition handlers
Hello,
I would like to establish top level condition handlers and restarts, so
that I don't explicit calls to withCallingHandlers and withRestarts in
many places:
For example :
> customError
function( message ){
err <- simpleError( message )
class( err ) <- c( "customError", class( err) )
err
}
> withCallingHandlers( { signalCondition(customError(
2023 Feb 19
2
R: determine if `suppressMessages()` has been invoked
Awesome, this gets the job done.
To answer your question:
When using C or C++ via Rinside or within a package, those functions do not listen to suppressMessages, e.g. `Rprintf` keeps printing to the console. Since it's common to use wrapper functions in R anyway, they can run `are_messages_suppressed` and pass the information on to an explicit `verbose` argument of the C / C++ function.
2008 Jul 17
2
AIX 5.3 --enable-R-shlib --with-x ---with-iconv make error with R-2.7.0 and R-2.7.1
Hi guys,
I am trying to compile a 64bit version of R 2.7.0 on AIX 5.3. And I am
running into some troubles. I also try the latest version 2.7.1 and
get the very similar errors.
The machine info:
-----------------------
$uname -srvp
AIX 3 5 powerpc
----------------------
My configuration is this:
----------------------------------------------------------
./configure \
2008 May 26
2
R 2.7.0: pdf() > pdf.options versus formals
Hi,
I have a tiny question about the graphics change in R 2.7.0.
If I write a script ? la:
options(device="pdf")
formals(pdf)[c("file","onefile","width","height")] <- list("~/Rplot
%03d.pdf", FALSE, 8, 8)
plot(3)
plot(4)
both plots will be written into ONE pdf file. (not two as expected)
This worked fine under 2.6.x
In R 2.7.0 I
2008 May 01
1
Locale problem with umlauts in factor levels in 2.7.0 (patched) from grid or lattice
With 2.7.0 patched (not tested with 2.0.0), I get an error message in a
program that ran correctly in R 2.6.2 when the grouping factor of a
stripplot contains an Umlaut:
I am aware that there are a few locale-changes in R 2.7.0, but I could not
easily
locate who's at fault
Dieter
library(lattice)
dt = data.frame(x=rnorm(100),y=1:100,levs= as.factor(c("Gru","Gr?")))
2008 Jun 19
1
error related to approxfun in R 2.7.0
I'm testing R version 2.7.0 on windows and there seems to be a
compatibility issue with objects that were created by "approxfun" in
older versions. As long as the objects were created in version 2.7.0
things work ok, but calling the interpolated functions from R version
2.0.1 causes this error:
Error in .C("R_approx", as.double(x), as.double(y), as.integer(n),
xout =
2008 Jun 30
1
2.7.0 breaks read.table
Hi,
yes a bold statement, but I get different behaviour
from 2.6.2 and 2.7.0 in read.table, and I don't find
any documentation in http://cran.r-project.org/src/base/NEWS.
A file like (space delimited):
foo + .
bar - .
2.7.0:
> tab <- read.table("test.txt",as.is=TRUE)
> tab
V1 V2 V3
1 foom 0 0
2 bar 0 0
while until now and on 2.6.2
> tab <-
2009 Mar 27
1
deleting/removing previous warning message in loop
Hello R Users,
I am having difficulty deleting the last warning message in a loop so that the only warning that is produced is that from the most recent line of code. I have tried options(warn=1), rm(last.warning), and resetting the last.warning using something like:
> warning("Resetting warning message")
This problem has been addressed in a previous listserve string,
2008 Apr 28
4
R 2.7.0, match() and strings containing \0 - bug?
Hi,
A piece of my code that uses readBin() to read a certain file type is
behaving strangely with R 2.7.0. This seems to be because of a failure
to match() strings after using rawToChar() when the original was
terminated with a "\0" character. Direct equality testing with ==
still works as expected. I can reproduce this as follows:
> x <- "foo"
> y <-