search for: zedlewski

Hi, I'm a newbie trying to make an R program executable on UNIX, just like one would write an executable perl script by putting "#!/usr/bin/perl" in the first line, and so on. It seems, though, that this would only work if I use the "BATCH" command to tell R to execute the program in its first argument. This would have the unfortunately side-effect of dumping all

Hi, I have an R script that takes its input in the form of command-line parameters. It works fine, but R complains about every unknown arg with the "ARGUMENT %s ignored" message, and this goes to stdout instead of stderr because R_ConsoleFile isn't set yet. Is it really necessary to process all command line args before setting R_ConsoleFile? It seems that only Aqua systems care

Hi, I have an R script that takes its input in the form of command-line parameters. It works fine, but R complains about every unknown arg with the "ARGUMENT %s ignored" message, and this goes to stdout instead of stderr because R_ConsoleFile isn't set yet. Is it really necessary to process all command line args before setting R_ConsoleFile? It seems that only Aqua systems care

I've noticed that the max.col function with the default "random" option often gives unexpected results. For instance, in this test, it seems clear what the answer should be: > # second col should always be max > x1 = cbind(1:10, 2:11, -Inf) > > # this works fine > max.col(x1, "first") [1] 2 2 2 2 2 2 2 2 2 2 > > # this gives random answers >

I've noticed that the max.col function with the default "random" option often gives unexpected results. For instance, in this test, it seems clear what the answer should be: > # second col should always be max > x1 = cbind(1:10, 2:11, -Inf) > > # this works fine > max.col(x1, "first") [1] 2 2 2 2 2 2 2 2 2 2 > > # this gives random answers >