search for: dosomethingwith

I'm having trouble setting up the function call to handle two lists of matrices. Each list has 6 matrices - Each matrix is 20x10. I need to do some basic math on corresponding matrices in each list. Here are some outputs of these lists, etc... # first list > length(qc.pm) [1] 6 > dim(qc.pm[[1]]) [1] 20 10 > qc.pm[[1]][1:4,1:4] 441-JP071707.CEL 442-JP071707.CEL

Dear all, I know this topic has already been covered in other posts (at least the for loop Vs apply family of function), but I am looking for fresh / up-to-date opinion and feedback on those 3 methods to run unavoidable loops in R. I realise that it may be too general question for many, so any feedback appreciated. 1. apply Vs for loop >> Seems apply is (was?) supposed to be faster than

...quot;); items2 <- read.csv(testfile2, dec=","); The way I intend to use it is to define a string list containing names of date.frames, and interate this list to perform some function: createTable <- function(latentVariableNames) { for (currentName in names(latentVariableNames)) { doSomethingWith(currentName) } } Would be grateful for any help! Chaehan [[alternative HTML version deleted]]

...e rest of "..." to another function. Here's a short example: I'm adding more functionality to a generic method by defining how it works on a new class "MyClass": setMethod('existingFunction', 'MyClass', function (object, ...) { vars <- list(...) doSomethingWith(vars$myCustomVar) # now I want to pass the rest of the vars down to another function, # let's say some plotting function, so I'd like to remove # `myCustomVar` from "...", keep the rest of the vars and just # pass the valid "..." elements down through the call...

Hi all, the language reference for the alloca instruction states: The ‘alloca‘ instruction allocates memory on the stack frame of the currently executing function, to be automatically released when this function returns to its caller. when using come c code like void myfunc(void){ int i=4; double d[i]; } the ir shows enclosing llvm.stackSave & restore constructs, enclosing the alloca

> In C, the ‘minimal’ part is called the ‘scope’. Variables are always destroyed in the inverse order to the order in which they are created and so it’s always trivial to translate each into a stack save followed by an alloca when the variable comes into scope and a stack restore when the variable goes out of scope. > >> what would happen if stack safe/remove would be neglected?

Hey guys, I recently published an article documenting some of the more useful and interesting parts of Prototype''s Enumerable, Hash and Array objects. You can find it here: http://encytemedia.com/blog/articles/ 2005/12/07/prototype-meets-ruby-a-look-at-enumerable-array-and-hash If you have any feedback or suggestions, fire away. Cheers, -Justin Palmer

...he alloca changes whenever the declaration goes into scope. By emitting a stack save and restore for d, clang doesn’t need to have different IR generating code for your example and for this one: > > void myfunc(void > { > for (int i=0 ; i<4; i++) > { > double d[i]; > doSomethingWith(d); > } > } > > In this case, each time that the loop is entered you will get a new d with a different size. Clang emits code that handles this case, and an early optimisation pass will remove the stack save and stack restore intrinsics if they’re not actually needed. > > Davi...

How does one create a vector whose contents is the list of variables in a dataframe pertaining to a particular pattern? This is so simple but I cannot find a straightforward answer. I want to be able to pass the contents of that list to a "for" loop. So let us assume that one has a dataframe whose name is Data. And let us assume one had the height of a group of people measured at