search for: g0c4

> .Internal(inspect(1:10)) @300e4e8 13 INTSXP g0c0 [NAM(3)] 1 : 10 (compact) > .Internal(inspect(seq(1,10))) @3b6e1f8 13 INTSXP g0c4 [] (len=10, tl=0) 1,2,3,4,5,... > system.time(1:1e7) user system elapsed 0 0 0 > system.time(seq(1,1e7)) user system elapsed 0.05 0.00 0.04 It seems that result of function 'seq' doesn't use compact internal representation. However, looking at t...

...uke On 04/29/2018 06:22 AM, Duncan Murdoch wrote: > On 28/04/2018 11:11 PM, Suharto Anggono Suharto Anggono via R-devel wrote: >>> .Internal(inspect(1:10)) >> @300e4e8 13 INTSXP g0c0 [NAM(3)]? 1 : 10 (compact) >>> .Internal(inspect(seq(1,10))) >> @3b6e1f8 13 INTSXP g0c4 [] (len=10, tl=0) 1,2,3,4,5,... >>> system.time(1:1e7) >> ??? user? system elapsed >> ?????? 0?????? 0?????? 0 >>> system.time(seq(1,1e7)) >> ??? user? system elapsed >> ??? 0.05??? 0.00??? 0.04 >> >> It seems that result of function 'seq...

On 28/04/2018 11:11 PM, Suharto Anggono Suharto Anggono via R-devel wrote: >> .Internal(inspect(1:10)) > @300e4e8 13 INTSXP g0c0 [NAM(3)] 1 : 10 (compact) >> .Internal(inspect(seq(1,10))) > @3b6e1f8 13 INTSXP g0c4 [] (len=10, tl=0) 1,2,3,4,5,... >> system.time(1:1e7) > user system elapsed > 0 0 0 >> system.time(seq(1,1e7)) > user system elapsed > 0.05 0.00 0.04 > > It seems that result of function 'seq' doesn't use compact inte...

...in the handling of the compact form of the row.names attributes. When n is the number of rows of a data.frame, the compact form is c(NA_integer_,-n), as in: > d <- data.frame(x=1:10) > .Internal(inspect(d)) @104f174a8 19 VECSXP g0c1 [OBJ,NAM(2),ATT] (len=1, tl=0) @103a7dc60 13 INTSXP g0c4 [] (len=10, tl=0) 1,2,3,4,5,... ATTRIB: @104959380 02 LISTSXP g0c0 [] TAG: @100823078 01 SYMSXP g1c0 [MARK,LCK,gp=0x4000] "names" (has value) @104f17748 16 STRSXP g0c1 [NAM(2)] (len=1, tl=0) @10085c678 09 CHARSXP g1c1 [MARK,gp=0x61] [ASCII] [cached] "x" TAG:...

...R version 2.14.0 (2011-10-31) Platform: i386-pc-mingw32/i386 (32-bit) > x = 1L > .Internal(inspect(x)) # why NAM(2)? expected NAM(1) @2514aa0 13 INTSXP g0c1 [NAM(2)] (len=1, tl=0) 1 > y = 1:10 > .Internal(inspect(y)) # NAM(1) as expected but why different to x? @272f788 13 INTSXP g0c4 [NAM(1)] (len=10, tl=0) 1,2,3,4,5,... > z = data.frame() > .Internal(inspect(z)) # why NAM(2)? expected NAM(1) @24fc28c 19 VECSXP g0c0 [OBJ,NAM(2),ATT] (len=0, tl=0) ATTRIB: @24fc270 02 LISTSXP g0c0 [] TAG: @3f2120 01 SYMSXP g0c0 [MARK,gp=0x4000] "names" @24fc334 16 STR...

...se .Internal(inspect(x)) in order to detect vector copying. Take for example the following silly code: f <- function() { x = seq(10) print(.Internal(inspect(x))) for(i in seq(10)) { x[i] <- x[i] + 1 print(.Internal(inspect(x))) } } The output of f() was: @bd7acf0 13 INTSXP g0c4 [NAM(1)] (len=10, tl=0) 1,2,3,4,5,... [1] 1 2 3 4 5 6 7 8 9 10 @bdd6f80 14 REALSXP g0c6 [NAM(1)] (len=10, tl=0) 2,2,3,4,5,... [1] 2 2 3 4 5 6 7 8 9 10 @ba66278 14 REALSXP g0c6 [NAM(1)] (len=10, tl=0) 2,3,3,4,5,... [1] 2 3 3 4 5 6 7 8 9 10 @ba661e0 14 REALSXP g0c6 [NAM(...

Hi, I haven't found a way to display the memory location of an object in R. Is there one? (I want to see whether some code 'grows' an object, and an ever-changing memory location for the object would presumably confirm this) Thanks m -- View this message in context: http://r.789695.n4.nabble.com/memory-location-of-object-tp3207798p3207798.html Sent from the R help mailing list

...blem with the way the names have been constructed, that would explain the error in str(), and would lead to lots of other weird problems. Another way to look at R objects from within R is to use .Internal(inspect( x )). For example, > .Internal(inspect(names(iris))) @7f898ff9e2e8 16 STRSXP g0c4 [NAM(2)] (len=5, tl=0) @7f8992c41878 09 CHARSXP g0c2 [gp=0x61,ATT] [ASCII] [cached] "Sepal.Length" @7f8992c41840 09 CHARSXP g0c2 [gp=0x61] [ASCII] [cached] "Sepal.Width" @7f8992c41808 09 CHARSXP g0c2 [gp=0x61,ATT] [ASCII] [cached] "Petal.Length" @7f898ba9...

...hat would >> explain the error in str(), and would lead to lots of other weird problems. >> >> Another way to look at R objects from within R is to use >> .Internal(inspect( x )). For example, >> >> .Internal(inspect(names(iris))) >> @7f898ff9e2e8 16 STRSXP g0c4 [NAM(2)] (len=5, tl=0) >> @7f8992c41878 09 CHARSXP g0c2 [gp=0x61,ATT] [ASCII] [cached] >> "Sepal.Length" >> @7f8992c41840 09 CHARSXP g0c2 [gp=0x61] [ASCII] [cached] "Sepal.Width" >> @7f8992c41808 09 CHARSXP g0c2 [gp=0x61,ATT] [ASCII] [cached] >> &qu...

...e error in str(), and would lead to lots of other weird >> problems. >> >> Another way to look at R objects from within R is to use >> .Internal(inspect( x )). For example, >> >> .Internal(inspect(names(iris))) >> @7f898ff9e2e8 16 STRSXP g0c4 [NAM(2)] (len=5, tl=0) >> @7f8992c41878 09 CHARSXP g0c2 [gp=0x61,ATT] [ASCII] [cached] >> "Sepal.Length" >> @7f8992c41840 09 CHARSXP g0c2 [gp=0x61] [ASCII] [cached] "Sepal.Width" >> @7f8992c41808 09 CHARSXP g0c2 [gp=0x61,ATT] [ASCII] [cach...

Hey Duncan, Hard to debug? That's an understatement. Eyes bleeding.... In any case, I tried all your suggestions. To get "integer" for the final column, I had to change the code to get integers instead of strings. double[] d1 = ((REXPVector) ((RList) tableRead).get(0)).asDoubles(); double[] d2 = ((REXPVector) ((RList) tableRead).get(1)).asDoubles(); double[] d3 = ((REXPVector)