similar to: [SOLVED] Rscript path problem on R 2.13.1 for Ubuntu 11.04?

Dear all, finally decided to do an Ubuntu upgrade and a new clean R install from http://cran.r-project.org/bin/linux/ubuntu/. However, while trying to install a package from R-forge I encountered problems, involving error messages saying "Rscript execution error: No such file or directory" (see below). The same procedure works on Ubuntu 11.04 running R 2.12.1-1 from the Ubuntu

Hi, I have run into a strange issue with Rscript and plyr. When running the following Rscript: #!/usr/bin/Rscript library(plyr) d = ddply(data.frame(a=1:101,b=1:101), .(a,b), nrow) head(d) the script does not terminate. It prints out the results from head(d), but does not return to the shell. By changing the a and b to 1:100, the script returns. The same code running within the R shell works

Hi, I have some code I run interactively through the R interpreter and it works fine. I then run it as a script with Rscript and I get an error. The error is coming when Rscript builds a model matrix. Here is the Rscript code : #!/usr/lib/R/bin/Rscript --verbose require(MASS) options(contrasts = c("contr.treatment", "contr.poly")) .... form <- as.formula(paste(ef.var,

Hi, I have a script I can run step by step through the R interpreter and it works fine. I then run as a shell script with Rscript and it fails. The error message comes when I am creating a model matrix with model.matrix.default(). Error in `contrasts<-`(`*tmp*`, value = "contr.Treatment") : could not find function "is" Calls: model.matrix.default ->

Good morning R-help, I have an idiot question: I would like to use getSrcDirectory() and friends to allow me to identify where an R file has been called from when invoked using Rscript. If I understand the documentation correctly, the following example should work: In file test.R: options(keep.source=T) fn<-function(x){x<-x+1} srcDir<-getSrcDirectory(fn) print(srcDir) I

Dear R-devel members, recently, I ran into the following error message (R-devel 2018-01-31): 'Rscript' should not be used without a path -- see par. 1.6 of the manual I would like to know more about it, why is it required to run Rscript with a path, and where is that par. 1.6 of the manual. I get this error message during Travis r-devel build of my package for generating makefiles. I

Hello, I'm trying to build a simple cpp file using the R CMD SHLIB command and I always receive the same error message: cygwin warning: MS-DOS style path detected: C:/PROGRA~1/R/R-212~1.1/etc/i386/Makeconf Preferred POSIX equivalent is: /cygdrive/c/PROGRA~1/R/R-212~1.1/etc/i386/Makeconf CYGWIN environment variable option "nodosfilewarning" turns off this warning. Consult

Full_Name: Philip R. Kensche Version: 2.9.1 OS: Linux Submission from: (NULL) (131.174.146.252) Use case: Run R scripts using bin/Rscript or "bin/R --no-restore --file=<script-file> --args <args>" in a heterogeneous computing grid in which it is not possible to predict the actual installation directory of the R binaries. Problem: The script bin/R and the wrapper

Thanks for bringing the question over from StackOverflow [1]. I am not very impressed that you STILL hide behind a pseudonym and I am starting to question my sanity as to why I take time out to help someone like that. Anyway, read on ... [1] http://stackoverflow.com/questions/35313704/rscript-launch-custom-r/ On 10 February 2016 at 15:50, Cron Acronis wrote: | Dear all, | | I am trying to use

Hi, A user of my `optparse` package discovered a bug in Rscript's parsing of [args]. (https://github.com/trevorld/optparse/issues/24) I've reproduced the bug on my machine including compiling and checking the development version of R. I couldn't find a mention of it in the Bug Tracker or New Features. Can be minimally reproduced on the UNIX command line with following commands:

On 16/09/2018 4:53 AM, Voeten, C.C. wrote: > Hello, > > I have found what I believe to be a bug in the Linux version of the Rscript binary. > Under Windows (official 64-bit 3.5.1 R distribution running on an up-to-date Win10), I can do the following (e.g. under powershell): > > PS H:\Users\Cesko> Rscript -e 'ls() >>> ls()' > character(0) > character(0)

Greetings, I am creating a standalone executable script using Rscript and have run into problems when I define a new S4 class. Here is a small script that demonstrates my problem: #!/usr/bin/env Rscript # # toy.Rscript -- testing S4 class creation in an Rscript setClass("toy", representation(name = "character", price = "numeric"),

On 04/26/2018 02:23 PM, Kerry Jackson wrote: > Thanks Tomas. > > I confirm the quick workaround works for me in the DOS prompt, and when having a shortcut to RScript in SendTo, and when used in the Task Scheduler. I have not tested the R-devel version, due to my unfamiliarity with installing from source code. Thanks, Kerry. There are binary builds for daily snapshots of R-devel

Thanks, actually this is because the snapshot build is still one version behind (74642, the fix is in 74643). When I build my own installer and install it seems to be working fine. Sorry for the confusion, Tomas On 04/26/2018 02:49 PM, Kerry Jackson wrote: > Hi Tomas, > > Thanks for the info about the binary builds; I did install it, however the bug still seems to be there in the

Stephen, I hope you don;t mind that I am ccing this to the r-sig-debian list. In the future, please consider asking there, in particular for Ubuntu. On 2 May 2007 at 15:56, Stephen B. Weston wrote: | Dirk, | | I just downloaded and installed the .deb files for R-2.5.0 | for my Ubuntu/Dapper machine from: | | http://lib.stat.cmu.edu/R/CRAN/bin/linux/ubuntu/dapper/ | | I admit that I

Thanks for the report. A quick workaround before this gets fixed is to add an extra first argument that has no space in it, e.g. Rscript --vanilla "foo bar.R" The problem exists on all systems, not just Windows. Best Tomas On 04/25/2018 09:55 PM, Kerry Jackson wrote: > Hi R Developers, > I have found what I think is a bug in the RScript.exe in version 3.5.0 of R for Windows.

Hi all, this is probably some tricky configuration file problem, but I figure someone here might have come across this in the past: In short, I've been using Rscript to run my scripts, usually successfully. But recently I've run into a strange problem, and the only function that causes an error is "print". I can create a file that contains only a print command, and it causes

It seems the fix has not been ported to the patched version of R on Windows yet. I just tested R version 3.5.0 Patched (2018-04-27 r74667). IMHO this bug is so bad that it is worth a new release R 3.5.1 before it starts biting more users like this one https://stackoverflow.com/q/50077412/559676. BTW, although the bug has been fixed (https://github.com/wch/r-source/commit/c29f694), I think it will

Rscript eats up the last argument when reporting the command it runs: $ Rscript --verbose "/tmp/test.R" one two three running '/usr/local/lib/R-devel/lib/R/bin/R --slave --no-restore --file=/tmp/test.R --args one two' With the patch below, I get the following: $ Rscript --verbose "/tmp/test.R" one two three running '/usr/local/lib/R-devel/lib/R/bin/R --slave

See the example below (under Ubuntu): $ Rscript -e '1' -e '2' [1] 1 [1] 2 $ Rscript -e '1' -e '' -e '2' ERROR: option '-e' requires an argument $ uname -a Linux xie 3.5.0-25-generic #39-Ubuntu SMP Mon Feb 25 18:26:58 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Similar problem under Windows: Rscript -e "1" -e "" -e "2" [1]