On 30 December 2016 at 20:38, Romain Francois wrote:
| It made more sense to track times since an origin, esp when you might use
several timers in case you use multiple threads.
Using an offset to an origin (and hence differences) is also a sensible way
to deal with higher resolutions. We cann
It made more sense to track times since an origin, esp when you might use
several timers in case you use multiple threads.
> Le 30 déc. 2016 à 13:37, Dirk Eddelbuettel a écrit :
>
>
> On 29 December 2016 at 11:25, Jonathan Christensen wrote:
> | Hi Kaspar and Dirk,
> |
> | It is indeed cumu
On 30 December 2016 at 06:37, Dirk Eddelbuettel wrote:
|
| On 29 December 2016 at 11:25, Jonathan Christensen wrote:
| | Hi Kaspar and Dirk,
| |
| | It is indeed cumulative. Previously (presumably when that gallery page was
| | written) it was not cumulative, but Romain Francois changed the beha
On 29 December 2016 at 11:25, Jonathan Christensen wrote:
| Hi Kaspar and Dirk,
|
| It is indeed cumulative. Previously (presumably when that gallery page was
| written) it was not cumulative, but Romain Francois changed the behavior of
the
| step() function several years ago, in this commit:
h
Hi Kaspar and Dirk,
It is indeed cumulative. Previously (presumably when that gallery page was
written) it was not cumulative, but Romain Francois changed the behavior of
the step() function several years ago, in this commit:
https://github.com/RcppCore/Rcpp/commit/e295b2b178de55291e63705966368404
On 29 December 2016 at 14:55, Kaspar Märtens wrote:
| Hi,
|
| Trying out the Rcpp Timer example from http://gallery.rcpp.org/articles/
| using-the-rcpp-timer/ I was unable to reproduce similar results. The example
| output
|
| get/put g/p+rnorm() empty loop
| 1.967e+03 3.288e+03 6.4
Hi,
Trying out the Rcpp Timer example from
http://gallery.rcpp.org/articles/using-the-rcpp-timer/ I was unable to
reproduce similar results. The example output
get/put g/p+rnorm() empty loop
1.967e+03 3.288e+03 6.400e-04
compared to the output I see
get/put g/p+rnorm() empty loo
