I posted this in openbabel-devel but didn't get much help, so hopefully
someone here can help. I don't think its too openbabel specific.
I would like to make use of open babel from within the R language.
Initially I just need to do some format conversions, but may expand the
usage to other parts
On 25 March 2013 at 12:50, Kevin Horan wrote:
| I posted this in openbabel-devel but didn't get much help, so hopefully
| someone here can help. I don't think its too openbabel specific.
|
| I would like to make use of open babel from within the R language.
| Initially I just need to do some for
> "MM" == Martin Maechler
> on Tue, 19 Mar 2013 17:16:42 +0100 writes:
> "RG" == Renaud Gaujoux
> on Sun, 17 Mar 2013 10:38:44 +0200 writes:
RG> Late report is better than never isn't it? :)
>>> > Well,... you forgot to show the error (and the
>>> traceback)
Hi,
I used to use currentTime() (from /src/main/datetime.c) to time various
sections of data.table C code in wall clock time in sub-second accuracy
(type double), consistently across platforms. The consistency across
platforms is a really nice feature of currentTime(). But currentTime()
isn'
Would it make sense for as.Date.POSIXct to not assume tz="UTC" if the
POSIXct object has a valid tzone attribute? Current behavior may be
confusing in certain cases, for example:
> (d <- structure(1090450800, tzone="Europe/Berlin",
+ class=c("POSIXct","POSIXt")))
[1] "2004-07-22 01:00:00 CEST"
>
It turns out the reason for this is pretty simple:
sys.source does:
for (i in exprs) eval(i, envir)
where source basically does
n <- length(exprs)
for (i in seq_len(n)) eval(expr[i], envir)
so the problem is presumably related to the way that for strips attributes.
Hadley
On Tue, Mar 19, 2013
On 13-03-26 6:45 PM, Hadley Wickham wrote:
It turns out the reason for this is pretty simple:
sys.source does:
for (i in exprs) eval(i, envir)
where source basically does
n <- length(exprs)
for (i in seq_len(n)) eval(expr[i], envir)
so the problem is presumably related to the way that for stri
The help page for mean still says there is a method for data.frame although
this has been deprecated for several versions and in R 3.0.0 beta I get:
mean(data.frame(x=rnorm(10), y=rnorm(10)) )
[1] NA
Warning message:
In mean.default(data.frame(x = rnorm(10), y = rnorm(10))) :
argument is not
Sounds good for me.
Thanks.
2013/3/27 Duncan Murdoch
> On 13-03-26 6:45 PM, Hadley Wickham wrote:
>
>> It turns out the reason for this is pretty simple:
>>
>> sys.source does:
>> for (i in exprs) eval(i, envir)
>>
>> where source basically does
>> n <- length(exprs)
>> for (i in seq_len(n)) ev
