similar to: keep adding elements to the matrix

Dear all I would like to ask you if an assignment can be done inside a lapply statement. For example I would like to covert a double nested for loop for (i in c(1:dimx)){ for (j in c(1:dimy)){ Powermap[i,j] <- Pr(c(i,j),c(PRX,PRY),f) } } to something like that: ij<-expand.grid(i=seq(1:dimx),j=(1:dimy)) unlist(lapply(1:nrow(ij),function(rowId) { return

This problem is likely to be specific to Windows, and particularly Win7. After a successful build of a package (R CMD build addendum), I immediately run an R CMD check for the same package. Not always, but _very_ often, I get the following error: C:\Users\nisabbe\Documents\@Doctoraat\R>R CMD check addendum Loading required package: tcltk Loading Tcl/Tk interface ... done Loading

Hello list. This is from an R session (admittedly, I''m still using R 2.11.1): > print function (x, ...) UseMethod("print") <environment: namespace:base> > showMethods("print") Function "print": <not a generic function> Don''t the two results contradict each other? Or do I have a terrible misunderstanding of what

Dear all, I am trying to learn lapply. I would like, as a test case, to try the lapply alternative for the Shadowlist<-array(data=NA,dim=c(dimx,dimy,dimmaps)) for (i in c(1:dimx)){ Shadowlist[,,i]<-i } ---so I wrote the following--- returni <-function(i,ShadowMatrix) {ShadowMatrix<-i} lapply(seq(1:dimx),Shadowlist[,,seq(1:dimx)],returni) So far I do not get same results

Good day all, I'm trying to plot a continuous line plot, which is followed by two forecast points eg. one forecast point is 12 months out, and another 24 months out from the last date of the line plot. In my attempts so far, the second plot (the forecast points) is scaled against a new axis scale, thus the two plots are not directly comparable (I need the forecast points to be scaled

Hello list. Another 'puzzle' for which I don't have a clean solution. Say I have a multidimensional object, e.g.: Mm<-matrix(1:6, nrow=2, dimnames=list(c("a","b"), c("g","h","i"))) And on the other hand I have a list Ind<-list("b","g") This holds, for each dimension, an indexer for that dimension. Now I would

Hi all, I am having a bit of trouble with the array structure of R. What I want to do is dynamically add/remove elements to an array. For example: Let's say I have created an array: > myArray <- array(c(3,8), dim=c(1,2)) > myArray [,1] [,2] [1,] 3 8 And I now want to, for example, push an element (5,6) on to this array so it will read: [,1] [,2] [1,] 3 8

Hi all. I am currently attempting to build a list of sparse matrixes. That I have already achieved, by > vmat <- list() > for (i in 1:n) { > vmat <- c(vmat, sparseMatrix(i,j,x=data) > } How I am trying to select those elements from the list where the column e.g. 999 is not null. I can do this for one of the sparse matrices with > which(vmat[[1]][,999] != 0) which

On 04/24/2013 01:29 PM, Caldarale, Charles R wrote: > Is this a potential aliasing effect? Since myarray is defined as a pointer, not an array, it's theoretically possible that the address therein refers to the same memory location as the pointer itself. I was thinking along those lines, but I haven't been able to come up with a specific instance of what could possibly be aliased.

I was suprised to find that some bitcode I'm generating isn't getting optimized. Here, I'm doing the equivalent of "myarray[5]++" (on an "extern int *myarray"), repeated three times: @myarray = external global i32* define void @update_array() #0 { %1 = load i32** @myarray, align 8 %2 = getelementptr inbounds i32* %1, i64 5 %3 = load

Hello, I am trying to alter the way in which lattice functions (specifically xyplot) print the axis labels when one uses the 'scales' parameter. I can obtain the effect I want by using scales=list(y=list(log=10, labels=expression(yvalues))) where yvalues are the values that would have been printed as the y-axis labels if the "labels" argument had not been present. To help

I am new to R. I try to search the web but could not find the answer so I post it here asking for help. I have a csv file looks like this: (between two ==== lines) =========================== Machine Name,"Resource, Type","Resource, Sub-type","Resource, Instance",Date,,Data ->,,,,,, ,0.041666667,,,,,,,,,,, Time (HH:MM)

Hello all. I'm developing a package for R holding a Gibbs sampler, which tends to have better performance when written in C than in R. During each iteration in the Gibbs sampler, I need the inverse of a symmetric matrix. For this, I wish to use lapack, as is concisely suggested in "Writing R extensions", since this will have better performance than I could ever write myself. After

Hello When a call comes in, I'd like to fork a Python script that broadcasts a message so that users see the CID name + number pop up on their computer screen, and simultaneously ring their phones. The following script doesn't work as planned: It waits until the script ends before moving on to the next step, which is Dial(): =========== exten =>

Hey Guys n Gals; I have some arrays that I can't seem to expand correctly (if that's the correct word?), imagine the following example: #!/bin/bash myArray=("First" "Second" "Third") First=("Monday" "Tuesdays" "Wednesday") Second=("One" "Two" "Three") Third=("A" "B"

Hi Scott, On 24/04/13 19:40, Scott Pakin wrote: > I was suprised to find that some bitcode I'm generating isn't getting > optimized. Here, I'm doing the equivalent of "myarray[5]++" (on an > "extern int *myarray"), repeated three times: does your bitcode contain data layout information? Ciao, Duncan. > > @myarray = external global i32* >

> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Scott Pakin > Subject: [LLVMdev] Another missed optimization opportunity? > I'm doing the equivalent of "myarray[5]++" (on an > "extern int *myarray"), repeated three times: > I had expected the three increments by 1 to > be collapsed into a single increment

The semantic reason is that the optimizer is required to assume that the i32 stores could be storing to the storage of myarray. LLVM IR does not permit optimizers to optimize based on the nominal types of memory objects or memory accesses. This gets optimized in C, because the C compiler adds special TBAA metadata annotations to the loads and stores which say that the stores of "int" do

Dear list, I''ve had this a few times now, and wonder if this is possible: I''m using a package, often for plotting something, but I want to tune the way the plotting goes, in a way that was not foreseen by the maker of the package. Now, most of the time, these kinds of R functions (say pkg::plot.something) call into other R functions (say pkg::plot.something.internal), and

> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Scott Pakin > Subject: Re: [LLVMdev] Another missed optimization opportunity? > > Is this a potential aliasing effect? Since myarray is defined as a > > pointer, not an array, it's theoretically possible that the address > > therein refers to the same memory location as