> John Lawson
> on Thu, 5 Mar 2020 20:34:00 -0700 writes:
> I see this error on windows CRAN Check
> --- failure: the condition has length > 1 ---
> --- srcref ---
> :
> --- package (from environment) ---
> daewr
> --- call from context ---
> ihstep(y,
Recently I complained about the fact that it was taking forever for
packages to come back to me from the winbuilder facility that Uwe Ligges
so kindly provides.
Ben Bolker suggested that I use "rhub" instead. I responded that I'd
*heard* of rhub but had no real idea what it was nor how to
I see this error on windows CRAN Check
--- failure: the condition has length > 1 ---
--- srcref ---
:
--- package (from environment) ---
daewr
--- call from context ---
ihstep(y, x, m, c)
--- call from argument ---
if (t1 == "I" & t2 == "(") {
iquad = TRUE
}
t1 and t2 are both characters
Download the 'rhub' package. Then submission to 'rhub' is one easy command.
HTH,
-Roy
> On Mar 5, 2020, at 3:33 PM, Rolf Turner wrote:
>
>
> On 6/03/20 11:14 am, Ben Bolker wrote:
>
>
>
>> It's probably been suggested already in this thread, but perhaps
>> rhub would work for you as an al
On 6/03/20 11:14 am, Ben Bolker wrote:
It's probably been suggested already in this thread, but perhaps
rhub would work for you as an alternative?
Quite possibly, but I have no real idea what "rhub" is. I've seen it
referred to many times but the references always assume that you know
You can also just paste the ftp link into your browser.
On Thursday, March 5, 2020, 6:31:03 PM EST, Rolf Turner
wrote:
On 6/03/20 11:41 am, Henrik Bengtsson wrote:
> 1. I'd guess it helps Uwe a bit you clarify exactly which queue you
> think is stuck - otherwise he has to check the
On 6/03/20 11:41 am, Henrik Bengtsson wrote:
1. I'd guess it helps Uwe a bit you clarify exactly which queue you
think is stuck - otherwise he has to check them all. They're independent.
Yeah. Sorry. It's the R-release queue.
2. You can look at the different win-builder queues yourself vi
1. I'd guess it helps Uwe a bit you clarify exactly which queue you think
is stuck - otherwise he has to check them all. They're independent.
2. You can look at the different win-builder queues yourself via ftp, see
https://stat.ethz.ch/pipermail/r-package-devel/2020q1/005098.html
/Henrik
On Thu
Maybe there's something queriable similar to the CRAN queue? (In an
ideal world this could even be incorporated into F Michonneau's
foghorn package ...)
It's probably been suggested already in this thread, but perhaps
rhub would work for you as an alternative?
On Thu, Mar 5, 2020 at 4:35 PM R
Sorry to be a pest, but I submitted a package to winbuilder more than 24
hours ago, and nothing has come back to me. For a while (a few days
ago) I was getting about a 20 minute turnaround.
One gets dependant on facilities such as winbuilder and gets frustrated
when they don't perform quit
Well, it originates in C, where & and | are bitwise operators.
-pd
> On 5 Mar 2020, at 15:44 , Jeff Jetton wrote:
>
> This is something that, by the way, I've always thought R got backwards. If
> you want an operation to handle "one thing" against "one other thing"
> (scalars), a single & or |
This is something that, by the way, I've always thought R got backwards. If
you want an operation to handle "one thing" against "one other thing"
(scalars), a single & or | seems like the obvious symbol for it. Whereas an
operation on "multiple things" (vectors) would be well-represented by a
multi
On 05.03.2020 09:45, Rolf Turner wrote:
On 5/03/20 9:04 pm, Tomas Kalibera wrote:
On 3/5/20 4:26 AM, John Lawson wrote:
I see this error on the CRAN Check report
Fatal error: the condition has length > 1
The problem is that the condition t1 == "I" & t2 == "(" of the if
statement in
On 3/5/20 9:45 AM, Rolf Turner wrote:
On 5/03/20 9:04 pm, Tomas Kalibera wrote:
On 3/5/20 4:26 AM, John Lawson wrote:
I see this error on the CRAN Check report
Fatal error: the condition has length > 1
The problem is that the condition t1 == "I" & t2 == "(" of the if
statement in the c
It's not about god imposing style:). Consider this variant of your example:
>flag <- !is.null(x) && x > 0
With the strict checking this will throw error when you run it (good). If you
replace && with & and x is a vector, flag will silently become a vector and the
error be masked or delayed
On 5/03/20 9:04 pm, Tomas Kalibera wrote:
On 3/5/20 4:26 AM, John Lawson wrote:
I see this error on the CRAN Check report
Fatal error: the condition has length > 1
The problem is that the condition t1 == "I" & t2 == "(" of the if
statement in the code is not a scalar. Even though this
On 3/5/20 4:26 AM, John Lawson wrote:
> I see this error on the CRAN Check report
>
>> ### ** Examples
>>
>> #Definitive Screening Design
>> library(daewr)
>> set.seed(1234)
>> x <- DefScreen(m=5,c=0)
>> colnames(x) <- paste("x",1:5,sep="")
>> x$y <- 3*x$x1 + 2*x$x2 + 2*x$x4*x$x5 + x$x3^2 + 2*x$x1^
17 matches
Mail list logo
