search for: do_subset

Dear List, do you know a way for subsetting an R object from C code? I would need the equivalent of x[s]. I've found that the do_subset internal function does this, but don't really know how to call it properly. I've two SEXP's, one for the object and one for the index. I'm thinking of creating an enviroment, place the two SEXP's in it and then just parse and run the corresponding R code, but there might be si...

...4C29BC3: malloc (vg_replace_malloc.c:299) ==4711== by 0x4FB1B04: Rf_allocVector3 (memory.c:2712) ==4711== by 0x5027574: Rf_allocVector (Rinlinedfuns.h:577) ==4711== by 0x5027574: Rf_ExtractSubset (subset.c:115) ==4711== by 0x502ADCD: VectorSubset (subset.c:198) ==4711== by 0x502ADCD: do_subset_dflt (subset.c:823) ==4711== by 0x502BE90: do_subset (subset.c:661) ==4711== by 0x4F7741C: Rf_eval (eval.c:691) ==4711== by 0x4F7BAC3: Rf_evalListKeepMissing (eval.c:2955) ==4711== by 0x50200CB: R_DispatchOrEvalSP (subassign.c:1535) ==4711== by 0x50200CB: do_subassign (subassign.c:15...

...ce_malloc.c:299) > ==4711== by 0x4FB1B04: Rf_allocVector3 (memory.c:2712) > ==4711== by 0x5027574: Rf_allocVector (Rinlinedfuns.h:577) > ==4711== by 0x5027574: Rf_ExtractSubset (subset.c:115) > ==4711== by 0x502ADCD: VectorSubset (subset.c:198) > ==4711== by 0x502ADCD: do_subset_dflt (subset.c:823) > ==4711== by 0x502BE90: do_subset (subset.c:661) > ==4711== by 0x4F7741C: Rf_eval (eval.c:691) > ==4711== by 0x4F7BAC3: Rf_evalListKeepMissing (eval.c:2955) > ==4711== by 0x50200CB: R_DispatchOrEvalSP (subassign.c:1535) > ==4711== by 0x50200CB: do_...

The following code crashes after about 300 iterations on my?x86_64-w64-mingw32?machine on R 3.5.2 --vanilla.?? Others have duplicated this (see?https://github.com/tidyverse/magrittr/issues/190?if necessary), but I don't know how machine/OS-dependent it may be.?? If it doesn't crash for you, please try increasing the length of the x vector. Substituting the commented-out line for the one

...0b87a5 in do_begin () #17 0x080b70b7 in Rf_eval () #18 0x080b70b7 in Rf_eval () #19 0x080b87a5 in do_begin () #20 0x080b70b7 in Rf_eval () #21 0x080b73c3 in Rf_applyClosure () #22 0x080e03b4 in do_internal () #23 0x080e0b37 in Rf_usemethod () #24 0x080b9f34 in Rf_DispatchOrEval () #25 0x0813b48b in do_subset () #26 0x09fe39f0 in ?? () #27 0x081d620b in _length_code () #28 0x0be7aa5c in ?? () #29 0x0c05a050 in ?? () #30 0xbff046a8 in ?? ()

...#39;t work for sub-classes of data.table [4]. Is it feasible for R to consider allowing methods for `[` to set their own visibility flag at this point? The change is deceptively small: set 'eval' to 200 in names.c and R_Visible = TRUE before returning from the non-method-dispatch branch in do_subset(). This results in one change in the saved output of R's own tests/reg-S4.R [5]. Or is the potential breakage for existing code too prohibitive? -- Best regards, Ivan [1] https://github.com/Rdatatable/data.table/blob/e5b845e5cbc6be826558d11d601243240abe7a72/R/print.data.table.R#L164-L169 [2...

...0xd9f668, args=0xda163c, env=0xd9da48) at dotcode.c:1778 #5 0x56c44 in Rf_eval (e=0x3a9fb8, rho=0xd9da48) at eval.c:340 #6 0x58f18 in Rf_DispatchOrEval (call=0x3a94d0, generic=0x1632e8 "[", args=0x3a94b4, rho=0xd9da48, ans=0xefffc1c4, dropmissing=0) at eval.c:1386 #7 0xbea40 in do_subset (call=0x3a94d0, op=0x1c3754, args=0x3a94b4, rho=0xd9da48) at subset.c:471 #8 0x56aa0 in Rf_eval (e=0x3a94d0, rho=0xd9da48) at eval.c:317 #9 0x582c0 in do_set (call=0x3a95cc, op=0x1c3834, args=0x3a95b0, rho=0xd9da48) at eval.c:1008 #10 0x56aa0 in Rf_eval (e=0x3a95cc, rho=0xd9da48) at eval....

...) at ../../../R/src/main/objects.c:311 #10 0x0000000000576a25 in Rf_DispatchOrEval (call=0x1a81d8d0, op=0x1a3622e8, generic=0x67e8d7 "[", args=0x1a81d908, rho=0x1b690298, ans=0x7fffcaa8d5a8, dropmissing=0, argsevald=0) at ../../../R/src/main/eval.c:1930 #11 0x00000000004afc40 in do_subset (call=0x7716, op=0x7716, args=0xffffffffffffffff, rho=0x1b690298) at ../../../R/src/main/subset.c:577 #12 0x0000000000575a42 in Rf_eval (e=0x1a81d8d0, rho=0x1b690298) at ../../../R/src/main/eval.c:461 #13 0x00000000005780c7 in applydefine (call=0x1a81d748, op=0x1a3617a8, args=0x6,...

...> data.table [4]. > > Is it feasible for R to consider allowing methods for `[` to set their > own visibility flag at this point? The change is deceptively small: set > 'eval' to 200 in names.c and R_Visible = TRUE before returning from the > non-method-dispatch branch in do_subset(). This results in one change > in the saved output of R's own tests/reg-S4.R [5]. Or is the potential > breakage for existing code too prohibitive? > > -- > Best regards, > Ivan > > [1] > https://github.com/Rdatatable/data.table/blob/e5b845e5cbc6be826558d11d601243240...

I have an R script that I run using nohup R CMD BATCH r.in r.out & The code loops through data from the database and takes hours. The problem is, in about an hour and a half after I start the script the program stops and I get /usr/lib/R/bin/BATCH: line 55: 14067 Done ( echo "invisible(options(echo = TRUE))"; cat ${in}; echo "proc.time()" ) 14068

If anyone has a few extra CPU cycles to spare, I'd appreciate it if you could verify a problem that I have encountered. Run the code below and tell me if it crashes your R before completion. library(lme4) data(bdf) dump<-sapply( 1:50000, function(i) { fm <- lme(langPOST ~ IQ.ver.cen + avg.IQ.ver.cen, data = bdf, random = ~ IQ.ver.cen | schoolNR); cat("