Displaying 10 results from an estimated 10 matches for "setdatapart".
Did you mean:
getdatapart
2016 Jan 05
2
For integer vectors, `as(x, "numeric")` has no effect.
...e most obvious fixes are always back-incompatible these days.
>>> The example intrigued me, so I looked into it a bit (should have been doing something else, but ....)
>
>>> You're right that this is the proverbial thin-edge-of-the-wedge.
>
>>> The problem is in setDataPart(), which will be called whenever a class extends one of the vector types.
>
>>> It does
>>> as(value, dataClass)
>>> The key point is that the third argument to as(), strict=TRUE by default. So, yes, the change will cause all integer vectors to become double when the...
2015 Dec 12
2
For integer vectors, `as(x, "numeric")` has no effect.
...> Somehow, the most obvious fixes are always back-incompatible these days.
> The example intrigued me, so I looked into it a bit (should have been doing something else, but ....)
> You're right that this is the proverbial thin-edge-of-the-wedge.
> The problem is in setDataPart(), which will be called whenever a class extends one of the vector types.
> It does
> as(value, dataClass)
> The key point is that the third argument to as(), strict=TRUE by default. So, yes, the change will cause all integer vectors to become double when the class extends &q...
2015 Dec 11
0
For integer vectors, `as(x, "numeric")` has no effect.
Somehow, the most obvious fixes are always back-incompatible these days.
The example intrigued me, so I looked into it a bit (should have been doing something else, but ....)
You're right that this is the proverbial thin-edge-of-the-wedge.
The problem is in setDataPart(), which will be called whenever a class extends one of the vector types.
It does
as(value, dataClass)
The key point is that the third argument to as(), strict=TRUE by default. So, yes, the change will cause all integer vectors to become double when the class extends "numeric". Genera...
2016 Jan 05
0
For integer vectors, `as(x, "numeric")` has no effect.
...>>>> me, so I looked into it a bit (should have been doing
>>>> something else, but ....)
>>
>>>> You're right that this is the proverbial
>>>> thin-edge-of-the-wedge.
>>
>>>> The problem is in setDataPart(), which will be called
>>>> whenever a class extends one of the vector types.
>>
>>>> It does as(value, dataClass) The key point is that the
>>>> third argument to as(), strict=TRUE by default. So,
>>>> yes, the change wil...
2015 Dec 19
2
For integer vectors, `as(x, "numeric")` has no effect.
...most obvious fixes are always back-incompatible these days.
>>> The example intrigued me, so I looked into it a bit (should have been doing something else, but ....)
>
>>> You're right that this is the proverbial thin-edge-of-the-wedge.
>
>>> The problem is in setDataPart(), which will be called whenever a class extends one of the vector types.
>
>>> It does
>>> as(value, dataClass)
>>> The key point is that the third argument to as(), strict=TRUE by default. So, yes, the change will cause all integer vectors to become double when the...
2015 Dec 11
3
For integer vectors, `as(x, "numeric")` has no effect.
>>>>> Martin Maechler <maechler at stat.math.ethz.ch>
>>>>> on Tue, 8 Dec 2015 15:25:21 +0100 writes:
>>>>> John Chambers <jmc at r-project.org>
>>>>> on Mon, 7 Dec 2015 16:05:59 -0800 writes:
>> We do need an explicit method here, I think.
>> The issue is that as() uses methods for the generic
2015 Dec 19
0
For integer vectors, `as(x, "numeric")` has no effect.
...ehow, the most obvious fixes are always back-incompatible these days.
>> The example intrigued me, so I looked into it a bit (should have been doing something else, but ....)
>> You're right that this is the proverbial thin-edge-of-the-wedge.
>> The problem is in setDataPart(), which will be called whenever a class extends one of the vector types.
>> It does
>> as(value, dataClass)
>> The key point is that the third argument to as(), strict=TRUE by default. So, yes, the change will cause all integer vectors to become double when the clas...
2015 Dec 26
0
[Bioc-devel] For integer vectors, `as(x, "numeric")` has no effect.
...are always back-incompatible these days.
>>>> The example intrigued me, so I looked into it a bit (should have been doing something else, but ....)
>>
>>>> You're right that this is the proverbial thin-edge-of-the-wedge.
>>
>>>> The problem is in setDataPart(), which will be called whenever a class extends one of the vector types.
>>
>>>> It does
>>>> as(value, dataClass)
>>>> The key point is that the third argument to as(), strict=TRUE by default. So, yes, the change will cause all integer vectors to become...
2012 Jun 14
0
Reference class inheritance using matrix/array class
...setRefClass("Vol", fields=list(x="numeric"), contains="matrix")
... no error is produced, *but* on displaying Vol, I see no mention of
the "matrix" class. Carrying on, if I then try to instantiate an
object:
>Vol$methods( initialize = function() {
> setDataPart(.self,matrix(1:100,nrow=10))
>})
vol0 <- Vol$new(22)
Error in tryCatchOne(expr, names, parentenv, handlers[[1L]]) :
node stack overflow
I've tried a number of permutations with no luck. Any ideas? Is this
possible with Ref classes?
-jim
> sessionInfo()
R version 2.14.1 (2011-12-2...
2012 Jul 07
1
creating a '[' method for an S4 class
Hi,
I'm working on an S4 class that is expected to behave like an array.
I have some difficulties when defining '[' and I wonder if someone
could point me to the right direction:
1) Call the S4 object "obj"
2) Assume dim(obj) = c(10, 4, 2)
3) Suppose someone calls: obj[1:3,] , which is a mistake, given
dim(obj); how do I detect such situations?
Thank you very much for