similar to: reference counting bug related to break and next in loops

Hi, again i am stuck in my presentation, and i have never learn R before in my life but need this to be done, so please help me out for a favour: http://www.nabble.com/file/p20333155/kew.dat kew.dat run this in R and these comes up: Month Year Rain 1 Jan 1900 74.400000 2 Feb 1900 80.500000 3 Mar 1900 23.600000 4 Apr 1900 23.600000 5 May 1900 25.100000 6

Dear I would like to know how to use the Croston method in R, consaltarte if I download a package? personally work the series as a SARIMA In the present instalment have many values zeros proposed the following model, but I have many doubts with his predictions. M3 = arima (d1, order = c (2,1,4), n. ahead = 4, seasonal = list (order = c (2,1,4), period = 4)) where D1 = diff (series) Many

It looks like the 'seq' variable to 'for' can be altered from within the loop, leading to incorrect answers. E.g., in the following I'd expect 'sum' to be 1+2=3, but R 2.10.0 (svn 48686) gives 44.5. > x = c(1,2); sum = 0; for (i in x) { x[i+1] = i + 42.5; sum = sum + i }; sum [1] 44.5 or, with a debugging cat()s, > x = c(1,2); sum = 0; for (i in x) {

I think the following rather wierd expressions show a problem in how some of the .Primitive functions evaluate their arguments. I haven't yet thought of a way that a nonabusive user might run into this problem. In each case the first argument, x, is modified in the course of evaluating the second argument and then modified x gets used as the first argument: > x<-as.integer(1:5); y

Hello, After creating and destroying a number of domUs, I noticed that /local/domain/0/backend starts to get cluttered when using XL. The vif, vfb, vkbd, and vbd sections look like this: 270 = "" 271 = "" 272 = "" 273 = "" 274 = "" 275 = "" Where the dom ID is set to an empty value, however the console

I find it a little bit irritating when I receive a patch directly addressed to me to review, but I don't see the "00/34" cover letter. I want to see what this series is about, and what the motiviation for this change is. I'm also highly frustrated, in general, with mix-and-match CC: lists for patch series. Just put everyone relevant in the CC: for the entire series. That way

I find it a little bit irritating when I receive a patch directly addressed to me to review, but I don't see the "00/34" cover letter. I want to see what this series is about, and what the motiviation for this change is. I'm also highly frustrated, in general, with mix-and-match CC: lists for patch series. Just put everyone relevant in the CC: for the entire series. That way

The get_buf() API sets the second arg to the number of bytes *written* by the other side; in this case it should be zero as these are output buffers. lguest gets this right (obviously kvm's console doesn't), resulting in continual buildup of console writes. Signed-off-by: Rusty Russell <rusty at rustcorp.com.au> To: Amit Shah <amit.shah at redhat.com> ---

The get_buf() API sets the second arg to the number of bytes *written* by the other side; in this case it should be zero as these are output buffers. lguest gets this right (obviously kvm's console doesn't), resulting in continual buildup of console writes. Signed-off-by: Rusty Russell <rusty at rustcorp.com.au> To: Amit Shah <amit.shah at redhat.com> ---

Dear everyone, I'm doing some simulations which involves bootstrapping (using functions written in c loaded with R's dyn.load() function) and maximising the likelihood function with R's nlm() function. I used to run my code in S-plus but because I frequently ran out of memory (because of S-plus' silly memory management), I decided to try porting my code to R. In R (on a linux

Hi Hal, On Fri, Apr 4, 2014 at 1:22 PM, Hal Finkel <hfinkel at anl.gov> wrote: > [..] > Agreed; but what does your *ISelLowering::getPointerTy() function look > like? Did you override the default implementation? I wonder if returning > MVT::i64 from this function will make things work for you. > > -Hal > > I actually missed implementing this one. But, depending

[Env: Win XP, R 2.14.2, R 2.15.0] I have a replacement function for setwd() in my .Rprofile which displays the current R path in the R window title. It no longer works in R 2.15.x, giving the error below. Worse, the error prevents the rest of my .Rprofile script from completing. Is there some way to rescue this, i.e., preserve this behavior in R 2.15? If not, how can I modify my script so it

R-devel has been switched to use reference counting by default with r77508. Building with -DSWITCH_TO_NAMED goes back to the NAMED mechanism. Best, luke On Sun, 24 Nov 2019, luke-tierney at uiowa.edu wrote: > Baring any unforeseen issues R-devel will switch in about a week from > the NAMED mechanism to reference counting for determining when objects > can be safely mutated in base C

fitz_ra wrote > I know this is posted a lot, I've been through about 40 messages reading > how to do this so let me apologize in advance because I can't get this > operation to work unlike the many examples shown. > > I have a 2 row matrix >> temp > [,1] [,2] [,3] [,4] [,5] [,6] [,7] [,8] > [,9] [,10] > [1,] 17.000

Hi, > On Nov 18, 2020, at 12:08, Ola Fosheim Grøstad via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > My experience with LLVM is limited, but I am trying to figure out how to add optimizations for automatic reference counting. The GC documentation mentions that patch-points could be useful, but it does not state how they would be useful. If this is a FAQ, please let me know...

Fix get/put refcount imbalance with zero copy, which caused qemu to hang forever on guest driver unload. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Dave, I've put this on my tree so no need for you to bother. drivers/vhost/vhost.c | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c index

Fix get/put refcount imbalance with zero copy, which caused qemu to hang forever on guest driver unload. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Dave, I've put this on my tree so no need for you to bother. drivers/vhost/vhost.c | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c index

This release restores wheel emulation on absolute devices and drops the forced direction locking for scroll buildup during wheel emulation since it made it almost impossible to actually scroll in both directions. Since horizontal scrolling is disabled by default anyway, we don't need this lock. Peter Hutterer (5): man: add a warning that wheel emu inertia must be set and it isn't

Hello, We are currently making lots of changes to Rcpp (see the open Rcpp mailing list if interested [1] in the details). We are now using [2] R_PreserveObject and R_ReleaseObject to manage garbage collection instead of the PROTECT/UNPROTECT dance. This seems to work well, but I was wondering if there was documentation about it. In particular, if we preserve the same SEXP twice (or more),

This is very exciting news. Luke, thank you for all your work on this - I know it's been a long journey. All the best, Henrik On Tue, Dec 3, 2019 at 8:04 AM Tierney, Luke <luke-tierney at uiowa.edu> wrote: > > R-devel has been switched to use reference counting by default with > r77508. Building with -DSWITCH_TO_NAMED goes back to the NAMED > mechanism. > > Best,