search for: matrix3

Hi, thank you for taking the time and reading my question. My question is twofold: 1. I have several matrices with variables and one matrix with water levels. I want to predict the water level with the data in the other matrices. Basically, * mod<-lm(matrix1 ~ matrix2+matrix3)* ( What looks like a minus is meant to be the wiggly minus.) Of course I could dissemble the matrices and paste their columns into one long, long vector. But the method above gives reasonable results. Are there any methodological objections against doing this? 2. After having done the regression...

Hi R-users I have a series of matrices and I would like to bind them together by column using a loop (i.e. not writing cbind(matrix1, matrix2,matrix3....)). The reason is because in my real data set I have a very large number of matrices. Example: matrix1 <- matrix (1:12,4,3) matrix2 <- matrix (13:24,4,3) matrix3 <- matrix (25:36,4,3) matrix4 <- matrix (37:48,4,3) matrix5 <- matrix (49:60,4,3) for (i in 1:5) {...

I have a matrix with a lot of values inside.. when I execute the folowing command matrix2=subset(martix, condition.....) it works... but after the previous command I execute another "subset" matrix3=subset(martix2, condition2.....) and appears the following error: (subscript) logical subscript too long How can I solve this??? I think the probles is the size of the matrix... Thanks.. -- View this message in context: http://r.789695.n4.nabble.com/subset-in-a-BIG-matrix-tp3254115p3254115.html...

I'm performing item response theory with eRm packages I am excluding the persons that doesn't fit in the infit/outfit persons. for that I created a condition. then I have to create a new subset or matrix but with the condition. So: ORIGINAL matrix<-cbind(item1, item2, item3, item4) IF I PERFORM A head(matrix) item1 item2 item3 item4 3 2 3 1 3 1

What are the current limitations of using -O4 in llvm-gcc-4.2? As a first test, I compiled the molscript program first as -O3 and it works fine. However if i try to compile the same code as -O4, the build fails with... ar -cru clib.a args.o str_utils.o dynstring.o err.o indent.o vector3.o matrix3.o quaternion.o body3d.o extent3d.o io_utils.o colour.o key_value.o named_data.o double_hash.o hermite_curve.o element_lookup.o aa_lookup.o mol3d.o mol3d_init.o mol3d_io.o mol3d_utils.o mol3d_chain.o mol3d_secstruc.o sgi_image.o vrml.o ogl_utils.o ogl_body.o ogl_bitmap_character.o llvm-gcc -o molscr...

...imitations of using -O4 in > llvm-gcc-4.2? As a first test, I compiled the molscript > program first as -O3 and it works fine. However if i > try to compile the same code as -O4, the build fails with... > > ar -cru clib.a args.o str_utils.o dynstring.o err.o indent.o > vector3.o matrix3.o quaternion.o body3d.o extent3d.o io_utils.o > colour.o key_value.o named_data.o double_hash.o hermite_curve.o > element_lookup.o aa_lookup.o mol3d.o mol3d_init.o mol3d_io.o > mol3d_utils.o mol3d_chain.o mol3d_secstruc.o sgi_image.o vrml.o > ogl_utils.o ogl_body.o ogl_bitmap_ch...

I will test your suggestion, but I designed the test case to load the memory directly into <4 x float> registers. So there is absolutely no permutation and other swizzle or move operations. Maybe the heuristic should not only count the depth but also the surrounding load/store operations. Are the load/store operations vectorized, too? (I designed the test case to completely fit the SSE

...---------- A non-text attachment was scrubbed... Name: matrix2.c Type: text/x-csrc Size: 424 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120213/00c55781/attachment.c> -------------- next part -------------- A non-text attachment was scrubbed... Name: matrix3.c Type: text/x-csrc Size: 480 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120213/00c55781/attachment-0001.c>

Carl-Philip, The reason that this does not vectorize is that it cannot vectorize the stores; this leaves only the mul-add chains (and some chains with loads), and they only have a depth of 2 (the threshold is 6). If you give clang -mllvm -bb-vectorize-req-chain-depth=2 then it will vectorize. The reason the heuristic has such a large default value is to prevent cases where it costs more to