search for: myargs

This is was something like a request for your comments, thoughts on the topic... Many of you will know that the "..." (aka \dots) argument is very useful for passing ``further graphical parameters'', but can be a pain when itself is passed to too many plotting functions inside your own function. An artificial example being myplot <- function(x,y, ...) { plot(0:1, 0:1,

...user-supplied ones. One possible solution would be to augment the return value of commandArgs() with BOOL vector attribute that says whether it is a standard (reserved) R option or not. Here is a usage example that I have in mind: R BATCH --no-save 2001-01-01 3001-01-01 Foo/*.in batch.R batch.R: myArgs <- commandArgs() myArgs <- myArgs[!attr(myArgs, "is.standard")] start <- myArgs[1] end <- myArgs[2] files <- myArgs[-seq(2)] # code ... I am sure there are other (better) solutions, but having anything like this would make it easier to integrate R with shell scripts tha...

...fist a function with scalar parameters sigma_pos_old<-function(t,q,lam1,lam2) { q/(lam1-lam2)^2*( (exp(2*lam1*t)-1)/(2*lam1)-2/(lam1+lam2)*(exp(lam1*t+lam2*t)-1) + (exp(2*lam2*t)-1)/(2*lam2) ) } # now the same function where the only argument t is given as a 1x1 vector sigma_pos<-function(myargs) { q/(lam1-lam2)^2*( (exp(2*lam1*myargs[1])-1)/(2*lam1)-2/(lam1+lam2)*(exp(lam1*myargs[1]+lam2*myargs[1])-1) + (exp(2*lam2*myargs[1])-1)/(2*lam2) ) } # Now I use do.call newtime<-seq(1,5,len=1001) mypar<-c(q,lam1,lam2) sig_xx<-do.call("sigma_pos_old",c(list(t=newtime),mypar))...

Dear R-users, I am translating a S script into R and having some troubles with the match function. This function appears to work with vector and data.frame in S, but not in R, e.g.: a <- rep((1:4), each = 10) b <- rep((1:10), times = 4) mydf <- data.frame(a,b) myarg <- mydf[1,] match(myarg, mydf) # S returns 1 but R returns NA NA I guess one could use match(interaction(myarg),

Hi all, I'm trying to process all files with a certain extension "*.ext" in a directory like this: > R --slave --args /my/dir < dir_plot.r where I then I want to do something like: myarg <- commandArgs() inputdir <- myarg[length(myarg)] print(inputdir) "for file with extension "*.ext in inputdir" do data = process.data(file) outfile =

Dear List, just out of pure curiosity: is it possible to define a function via 'substitute()' such that the function's formal arguments are specified by a "wildcard" that is substituted when the expression is evaluated? Simple example: x.args <- formals("data.frame") x.body <- expression( out <- myArg + 100, return(out) ) expr <-

...6) Why is something like this not suitable: fun1 <- function(a1,a2,a3 = c("hi","by")) { cat(a3,a1+a2,"\n") } > fun1 (1,2) hi by 3 > fun1(1,2, a3 = "whoopee") whoopee 3 ... or, if you want to include the function as an argument of a list: > myArgs <- list(fun=fun1, arglist=list(a1=2, a2 =5, a3 = c("hi","by"))) For which you can do stuff like: > do.call(myArgs[[1]],myArgs[-1][[1]]) hi by 7 > arglist <- myArgs[-1][[1]][-3] > do.call(myArgs[[1]],c(arglist,a3 = "whoopee")) whoopee 7 etc. etc. See...

While preparing a function that contained non-ASCII characters for inclusion into a package, I replaced all non-ASCII characters with UTF-8 escape sequences (using \uxxxx) in order to make the package portable (and adhere to "R CMD check"). What I didn't expect: when one uses UTF-8 escape sequences in function arguments, one needs to use UTF-8 escape sequences when calling the

Using R 2.4, the following fails: setClass("testc", representation(a="ANY")) makeC <- function(myarg) new("testc", a=myarg) makeC() -> Error in initialize(value, ...) : argument "myarg" is missing, with no default On the other hand, this is OK: f <- function(a) g(b=a) g <- function(b) if(missing(b)) "missing" else "valid

Frequently we have a print method, say print.myclass, that has a variety of arguments. If in the .Rd file I say \usage{ \method{print}{myclass}(x, myarg) } I get a warning when running R CMD chk: * checking generic/method consistency ... WARNING print: function(x, ...) print.myclass: function(x, myarg) What is the proper way to handle this? Thanks -- Frank E Harrell Jr

Dear R-Developers, could 'sample' gain a ... argument? As a convenience function, I added a sample Method to my hyperSpec class. This function however has a flag indicating whether the results should be returned directly as a hyperSpec object or rather as indices that give a random sample. For the moment, I use SetGeneric to add the dots argument, but this of course gives a warning

I am writing a program where non-technical R users will read in a config file and the config file will then parse the arguments found within the config and pass them to respective functions. I'm having trouble (efficiently) writing a piece of code to retain quotation marks around the argument which requires it as input, as found in the example function below, myFuncton1. Below is a minimal,

Below is an example of output that changed as a result of r64970. I did not see any NEWS item suggesting this change is expected. Note that the example is contrived and I don't have a use case for it. I stumbled across it when playing with recent changes in R relating to duplication. Does the example use undefined syntax? ----- fn1 <- function(mylist) { fn1a <- function()

I have controller that processes data in one table and puts results in another. Now that its'' working, I would like to be able to run it from the command line ( read: windows batch file). How can this be done? It will be installed on a Windows box with InstantRails1.0, (if that matters). I will be doing more processes like this, so this is a good opportunity to get it right. -- Best

...object. foo <- function(a, b=1) .... foo(x, 3) match.call() looks promising, but it records that a is x, while I want the value of x (in the calling frame). Also, if the invocation is foo(x), then match.call doesn't record that b is 1. So I tried this (inside the function definition): myargs <- lapply(names(formals()), function(x) eval(as.name(x))) That's pretty close. However, my function has an optional argument in this sense: bar <- function(x, testing) ... where code in the body is if (! missing(testing)) do stuff When the eval in the previous l...

...h byte compile set to FALSE. When I set ByteCompile to TRUE, I receive the following error message while doing R CMD INSTALL /usr/lib/R/bin/INSTALL: line 34: 9964 Done echo 'tools:::.install_packages()' 9965 Segmentation fault | R_DEFAULT_PACKAGES= LC_COLLATE=C "${R_HOME}/bin/R" $myArgs --slave --args ${args} I have not been able to understand the problem. Can someone help me understand the problem so that it can be fixed? Thanks, Mayank ________________________________ This email message may contain proprietary, private and confidential information. The information transmitte...

Dear r-list folks, I have a problem which has been bugging me for a while now and I was hoping someone out there might be able to help. If I have a user-defined function with an indeterminate number of arguments, using the well-known "..." construct, how can I get the function to return the names of the items which were the arguments of the function as part of the function's

hi: would it be useful to build into R an optional mechanism that typechecks arguments? for example, sum.across <- function ( inpmatrix : matrixtype( dim[1]>1, dim[2]>3 ) ) : vector { } # this would define a sum.across function that can take matrices or data sets, but not vectors, # and which indicates that it will return a vector. xsum <- sum.across( 1:10

Hello, Here are a few questions that would be useful to get an answer via dedicated functions in utils or tools packages: - When did function foo appeared in R or in a given package? - When did argument myarg appeared in function foo? - When did function bar get deprecated or when did it disappeared? - I wrote a script using functions foo and bar with R 1.9.1. My script does not work any more

...ient value with the confidence limits below it, e.g.: 5.3 (4.2,6.4) My current thinking is to have a function (possibly a summary method) that takes the output from my functions and returns something that could be passed directly to the latex, odfTable, etc. functions: > myobj <- myfunc(myargs) > latex( summary(myobj), file='mytempfile' ) I prefer to use LaTeX, but many of the people I work with are stuck with MS products so the odf or html options are attractive there. Does anyone have any suggestions on how best to format the output so it can be passed to latex and friends...